I’ve been using MG3 standalone for a day now and I’m completely blown away - it really is great! I’ve been raving about it to my friends on Discord.
I’ve tried using it as a VST in FL Studio 24, but I’ve come up against a strange issue where the VST interface flickers. It does this on both VST2 and VST3 versions.
When I enter the settings menu, the flickering stops. I ran Afterburner to check what was happening with framerates and found that in the main interface, the framerate varies from 10fps to over 130. When the settings menu is open, the framerate locks at the refresh rate of the panel and everything displays normally. Leaving the settings screen starts the flickering again.
I’ve checked in Waveform 13 and the VST displays just fine. I appreciate that this might be an FL Studio bug rather than a MG3 issue, but it’s the only plugin I’ve ever had behave this way.
Is there an option in FL Studio to select OpenGL Renderer or Software Renderer and if so, have you tried both?
I have seen in other programmes that in some cases Software Renderer works better than OpenGL.
There are no options in FL Studio to switch rendering pipelines (it renders in software by default - the conversations on the ImageLine website about this ‘feature’ were quite entertaining!), but I was able to force Nvidia GPU rendering for the app in Windows options. This seems to have fixed the issue - I no longer see constant flickering. On first boot of FL Studio after the change, it flickered momentarily, but after several relaunches of the app I haven’t seen it since.
After a reboot, the flickering is back. It disappears when I press play on the host DAW.
When the DAW isn’t playing, the MG3 VST crackles in time with the flashing, just like a buffer underrun. This disappers and the flashing stops on pressing play.