Since i've upgraded to latest version, Server 1.3.770, on my win7 x64, Cubase 7.5.30 x64 doesn't seen the Reverb instance anymore, while it is absolutely there in the folder with the exact same name... I already re-scanned the vst folder twice.
First thing i would recommend you is to try some other host ... Reaper for example (unrestricted demo available for download). This will help you find out the origin of the problem - host or Nebula itself.
@ fr3udes Hi! I'm on Cubase 6.5. and have experienced some of that problem.
Franci is right, there is something weired about how Cubase reacts.
Here is a suggestion: If you have two folders, one called 'acustica' where your old Nebula Reverb.dlls reside and one new folder called 'acustica64', I would tried to deactivate the 'acustica' folder, so that Cubase only see the 'acustica64' folder. That's where your new Nebula 3 Reverb.dll should be AFAIK.
Then you do a rescan and check if Cubase finds Nebula 3 Reverb.dll
If you need the Nebula-stuff in the 'acustica' folder, you have to rename those Nebula dlls. that have the same name as Nebula 3 Reverb.dll - meaning: If you have one instance that's called Nebula 3 XXX, then you have to rename it, because of the 9-character bug in Cubase.
Important: a space counts as one character AFAIK, therefore Nebula_3_ has 9 characters (space marked with underscore). Tricky/irriating/time consuming stuff, yes I know, but rename to something that differs on the 9th character, and you're safe!
Version upgrade in Windows & OSX Nebula version upgrade is build in an installer setup that will upgrade your product to the last available version. Windows version will ask again for the both folder locations, instead MAC version that will use the default ones.
IMPORTANT: If the supplied path(s) in Windows version upgrade are incorrect, Nebula will not boot anymore. Avoid inconvenience and check both path before apply. If you have any questions, contact our technical support.
Solution: Paste new plug-in support installation folder over the old one, then go MAST page .XML file(s) and check/edit manually datapath tag path.
If you can solve it manually, send me a support ticket.