Issues with installation of Reaktor 6 (Hosts can't see VST2 version)

Resonant Serpent

(Originally asked this in the Native Access forum, but didn't get a response.)

I'm using the latest version of Studio One 6 as my host. When looking in the browser at my instrument plugins, I can only see the VST3 version of Reaktor 6. Unfortunately, the VST3 version of Reaktor 6 is buggy, and I can't expand the extra outputs. The VST2 version of Reaktor 6 does work in Studio One, but it's not showing up as recognized by Studio One.

I've attempted uninstalling/reinstalling several times, but no change. Still can't see VST2.

I own legitimate versions of these hosts:

Cubase 13, Sonar(latest), Studio One 6, FL Studio 24, Reaper 7, Reason 12, Ableton 12

In all of these hosts, the VST3 of Reaktor 6 is available and works without issue except for Studio One. In all of these hosts EXCEPT Reaper, VST2 of Reaktor 6 is hidden.

I can load the VST2 version of Reaktor 6 in Reaper, and it works as it should.

So, the VST2 plug is on my computer, but why can't my other hosts see it? According to information on the Studio One forum, others have the VST2 version up and running with zero issues.

How do I solve this?

Vocalpoint

https://community.native-instruments.com/discussion/33119/issues-with-installation-of-reaktor-6-hosts-cant-see-vst2-version

First thing I would do would be to 100% locate the actual VST2 Reaktor plugin file - confirm it's location, size etc to this:

If the file exists - check Studio One→Options→Locations→VST Plugins and see exactly where S1 is scanning for plugins.

Then check Native Access and see where it is placing VST2 (64 Bit) plugins. The stock NI path is brutal and is totally non-standard. If that path is not being added to S1 - there is one solution.

If the paths are good - then check View→Plugin Manager and see if the VST2 of Reaktor is hidden. Each plugins that is visible in S1 will have it's little indicator turned on - while hidden plugs are turned off.

If that is good - then in Plugin Manager - use the Remove Plug-ins button and let S1 completely destroy and rebuild the plugin db.

If you are still stuck after all this - there is some unknown issue that might require a support ticket.

VP

Resonant Serpent

Thank you for the detailed instructions.