Environment:
- OS: Windows 10 Pro 64-bit (Version 10.0.19045 Build 19045)
- CPU: Intel(R) Core(TM) i3 CPU 530 @ 2.93GHz
- CPU Instruction sets: MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, EM64T, VT-x
- Cubase: Steinberg Cubase 14 Pro (14.0.31 Build 337 x64)
- Vaporizer2: version 3.5, installed with both VST2 and VST3, SSE2 option checked
Description:
After installing Vaporizer2 with the SSE2 variant and enabling both VST2 & VST3 in the installer, Cubase automatically adds both plugin files to the blacklist on startup. In the Plugin Manager, VST2 shows “Invalid plugin”, VST3 shows “Unknown”. Interestingly, the Path seems to contain Slashes like in Linux instead of the Windows-Backslash. Not sure if this is intended.
Usually I don't have VST2 turned on but I activated if for debugging purposes to see if only the VST3 plugin is affected.
The standalone version also fails to start without showing any error messages.
Expected Behavior:
At least the SSE2 variant should load successfully in Cubase. The plugin should not be automatically blacklisted unless it crashes.
As my CPU does not have AVX, but SSE2 is supported (verified via CPU-Z and instruction set list), the plugin or at least the standalone version should run normally.
Actual Behavior:
Cubase blocks both VST2 and VST3 versions immediately, listing them as “Invalid plugin” or “Unknown”, despite the CPU meeting SSE2 requirements.
Environment:
Description:
After installing Vaporizer2 with the SSE2 variant and enabling both VST2 & VST3 in the installer, Cubase automatically adds both plugin files to the blacklist on startup. In the Plugin Manager, VST2 shows “Invalid plugin”, VST3 shows “Unknown”. Interestingly, the Path seems to contain Slashes like in Linux instead of the Windows-Backslash. Not sure if this is intended.
Usually I don't have VST2 turned on but I activated if for debugging purposes to see if only the VST3 plugin is affected.
The standalone version also fails to start without showing any error messages.
Expected Behavior:
At least the SSE2 variant should load successfully in Cubase. The plugin should not be automatically blacklisted unless it crashes.
As my CPU does not have AVX, but SSE2 is supported (verified via CPU-Z and instruction set list), the plugin or at least the standalone version should run normally.
Actual Behavior:
Cubase blocks both VST2 and VST3 versions immediately, listing them as “Invalid plugin” or “Unknown”, despite the CPU meeting SSE2 requirements.