I can’t reproduce this, and I can’t see where in the code this would be happening. We only set the DPI awareness in standalone apps, plug-ins should just use the host’s DPI awareness setting (see this method).
Is this only happening in VST3 versions of the plug-in?
I’ve just compiled a VST and yes, it happens there as well
Does the device you’re using have a HiDPI screen? I was able to recreate it on both a Macbook and a Windows Surface running Windows 7 in VMWare
I’ll try and dig around a little more, the process of debugging has been a terror. Any time I try and use Visual Studio in the VM, Windows pops up and tells me its running slow, so it turns Aero off, which in turn means Cubase won’t load…
Let me know if there is any more information you need from me
Yes the device has a hiDPI screen, but AFAIK DPI-aware apps aren’t supported fully on Windows 7. If I open the preferences panel in Cubase 10 the “Enable HiDPI” checkbox isn’t there like it is on 8.1 and 10 so the plug-in should be opened in non DPI-aware mode and therefore shouldn’t interact with the host’s settings at all…
Interesting, is your Windows Text size set to 100% ?
That seems to be where the problem lies, I have it set at 150%, but setting it to 100% means everything works correctly
From the images it looks as though opening the plugin is somehow forcing the host to change its text size to maybe 200%. I remember reading that Cubase doesn’t support non-integer scale factors, but maybe I’m just mentally combining two unrelated things…