Hello, if some of your third party plugins GUI are locked up in cubase i think i found some solutions for this problem so i hope it can help some of you.
I recopy here what i sent to Steinberg :
I have problems with some hardware midi remote scripts that causes to lock up GUI interface of some third party plugins like omnisphere 3 sonic extensions interface for exemple (cannot interact with the mouse. The sound change but visually nothing move in the plugin).
I tried i think almost all solutions possibles for graphicals glitches in cubase because at first I thought it was something to do with nvidia graphics drivers :
hidpi on and off in cubase, resizable windows ,windows 11 scaling, second monitor, switch graphic cards internal external, nahimic process, power management, Cubase midi ports etc.
Please note that all my system and plugins are up to date:
Processor Intel(R) Core™ Ultra 9 285K (3.70 GHz)
Installed RAM 64.0 GB (63.4 GB usable)
Graphics card NVIDIA GeForce RTX 4070 (12 GB) (STUDIO DRIVER)
Intel(R) Graphics (128 MB)
Storage 5.85 TB of 7.28 TB used
System type 64-bit operating system, x64-based processor
Pen and touch Touch support with 10 touch points
Cubase 15.0.30 Build 287 (x64)
Edition Windows 11 Pro
Version 25H2
Installed on 11/20/2025
OS build 26200.8655
Experience Windows Feature Experience Pack 1000.26100.315.0
Midi Remote Scripts Hardwares:
Komplete Kontrol S61 MK3 Keyboard
Softube Console 1 MK3 and Console Fader MK3
Nektar Panorama CS12
I use midi remote scripts that come with the hardwares ( I did not make them by myself)
I discovered what to do to everything works again but it’s kind of a ‘’patch’’ process.
When i let the midi remote scripts hardwares power OFF before opening the cubase session, everything is back to normal with plugins UI (I can move the mouse on a parameter and it move visually).
It seem that some midi remote script cause conflicts with some plugins GUI like omnisphere (sonic extensions UI).
Also, the problem start to appear when sessions in cubase become a little bit bigger. When i start from scratch, i do not have this problem. When I say bigger, it’s like 40 tracks.
So what i have to do in order to everything works goes like this:
1-Power ON all midi hardwares except those that use midi remote scripts (In my case : The exception I let the power ON before opening cubase is the Softube Console 1 MK3 and Fader MK3).
2-Open Cubase
3-Power ON the kontrol mk3 keyboard and let it load properly
4-Power ON the Nektar Panorama CS12 controller and let it load properly
5-Reload All remote scripts in Cubase ( so they reconnect ).
And everything back to normal.
So I guess it’s definitely something to do with some remote midi scripts process in cubase interfering with some sort of graphical coding in certain plugins.