I own and use these plugins quite often so this is an inconvenience.
I assume this is fixable by removing these plugins from the project but I would really like to find a way around this since that means not being able to use the plugins I work with in most of my projects, especially Acustica plugins.
Hard to guess… If you can play the project back, you could try (as a workaround) to Export Audio Mixdown in Realtime. Or you can Freeze (or Render In Place) the tracks first and then Export Audio Mixdown.
I’ll try with rendering in place because freezing the tracks nor the realtime export doesn’t work either but I’ll do it in a separate copy of the project just in case anything goes wrong.
After many tries, the realtime export is the only thing that worked after I enabled the ‘‘Suspend VST3 plug-in processing when no audio signals are received’’ option, I didn’t touch anything plugin-wise so the same plugins that apparently crashed the export before stayed active in the project.
Searching through other related threads and reading the conversations inside, it seems that this has to do with CPU spikes in this version of Cubase and not with the plugins themselves which seems logical because when I was trying to do a realtime export without the suspend VST3 option mentioned above, the export would get to about 3-4% and then crash with the message that the CPU overloaded.
I hope we get a stable version soon, at least without bugs like these.