screeenager

Yep, I agree 100%, that's what's weird to me as well. I've always managed to do my own software troubleshooting (having a bachelor's degree in computer science, I'd feel lollipop if I didn't), but this time it seems to be beyond my grasp. The first crash occured mid-project, while I was working on a bass cover I had started last month. The Cubase project opened fine as usual, Native worked, everything worked; then after a take, I tried to pull up Native's interface to fiddle with the tone a bit, and that's when it first crashed. It didn't happen after a restart/update (unless something was happening in the background while I was working), and now it doesn't work *at all*.

After using it with zero issues for about two years (currently as a 64 bit VST 3 in Cubase 10.5), I have a very nasty problem with Helix Native, all of the sudden. It started while I was working on a project and I tried opening the window; it froze Cubase, but sound was still playing. Upon restarting Cubase, it showed me the "safe mode" recovery screen, which stated that a fatal exception was found in the Native VST. So far I tried: restarting Cubase (no dice, same result) restarting my PC restarting Cubase in safe mode (that means no external VST's; when I open it like this, the project opens, everything works) reinstalling Helix Native (same thing happened) disabling WiFi and trying to load up Native like this loading Native into another VST host (Adobe Premiere, which it promptly crashed) Anybody got any ideas on what else I could try? I'm getting a little bit desperate, have to admit I haven't had such a big technical issue with my setup in years...