Hello guys, this is my first post but I have questions and hope someone will care to help.
In FL Studio, the versions designed for Windows 8 / 10 / 11 implements "vectorial" scaling for the GUI settings. A lot of newer VST's won't capture text input, they also create visual trails when I drag some of them around and some of these same problematic VST's won't even show changes in knob tweaks or pretty much anything else unless I move the plugin around after the change or after I minimize it, or even drag to resize it, then I will see the refresh. Something is telling me there is a correlation there.
I've read the manual and I assume it has something to do with "Windows system scaling". I've adjusted the scaling and other mentioned settings in FL Studio as suggested but still nothing, so I'm assuming it's either my old hardware or it needs something that a running Windows OS system provides in a way to allow proper functionality with the GUI?
I'll spare most personal details about my old computer, but if it helps any I don't even think vulkan works for it. I'm not convinced that it's not my old hardware but I'm asking here to be sure. I've also spent a very long time before making this thread trying to change settings through winetricks, also in Lutris which is what I use for Windows apps but still haven't found any solution.
I'm building a new computer very soon so I guess one way or another I'll find out if it's just an issue with Linux. Ultimately I'm wondering if anyone with newer hardware uses FL Studio 20+ through Wine with similar issues? I tried virtual desktop as well, that didn't work. Am I missing something that I could do to fix this, it or is my computer just too old?
Windows scaling issue in FL Studio
Re: Windows scaling issue in FL Studio
Just an update.
I guess either people already are aware of this issue, or have no clue what I'm talking about maybe because I just haven't figured out a workaround solution? Either way, not having compatible hardware made it even less desirable to look into it.
Anyways I set up my new computer, I have an AMD 9 7900X CPU, GeForce RTX 4070 and the rest is decent but just giving an idea of what I'm working with to further help (maybe).
May I just add, simply switching a few things in the config for this exact same linux hdd to work without breaking too much of a sweat is why I love Linux so much, maybe it's just me but working with FL 21 in Linux for some reason reminds me of how I felt using FL Studio 11 when my computer with Windows 7 was at it's peak performance.
Well, the graphics for SOME VST's are... less buggy, but there are still some problems that persist. I used a virtual desktop while trying this as well, using the "explorer" in an attempt to completely work in the wine session. Some VST's require you to create an "activation" file out of the systems ID and then drag it into the VST if you do offline activation and... well I can't seem to do that without an error. Maybe it's because I just tried to activate the VST on a different computer and it doesn't recognize the ID of this one. I may try that again later but this particular one requires other files to reside in the system as well which I believe the batch cmd installation failed to complete and I don't know where to place them manually or if that would even fix it.
The main problem however, the reason I made this thread still exists, I use Nexus 4 and the display still doesn't update. The VST starts blank and I have to mess around with the VST to get the preset display to show, also clicking a preset doesn't "update" or "refresh" the screen of the VST either.
Other than that I actually feel inspired to create again, I'm on an hdd on a distro that's very low on system requirements and this thing is feels just as fast as an sdd when I'm moving around in the program and such.
I just wish someone would make FL Studio and VST's completely compatible with Linux. Windows is just not for me anymore and I love FL Studio, I just want to Linux + FL Studio in peace lol. I have a Windows drive literally just so I can use FL Studio and I still haven't, because when I first installed it I find out in that moment that I have to pay for a freaking license key just to remove a watermark (without installing any 3rd party software) from the corner of my screen, that is insane and now they're discontinuing support for Windows 10 next year lol Microsoft just keeps moving further away from what made me stick with it for so long.
I guess either people already are aware of this issue, or have no clue what I'm talking about maybe because I just haven't figured out a workaround solution? Either way, not having compatible hardware made it even less desirable to look into it.
Anyways I set up my new computer, I have an AMD 9 7900X CPU, GeForce RTX 4070 and the rest is decent but just giving an idea of what I'm working with to further help (maybe).
May I just add, simply switching a few things in the config for this exact same linux hdd to work without breaking too much of a sweat is why I love Linux so much, maybe it's just me but working with FL 21 in Linux for some reason reminds me of how I felt using FL Studio 11 when my computer with Windows 7 was at it's peak performance.
Well, the graphics for SOME VST's are... less buggy, but there are still some problems that persist. I used a virtual desktop while trying this as well, using the "explorer" in an attempt to completely work in the wine session. Some VST's require you to create an "activation" file out of the systems ID and then drag it into the VST if you do offline activation and... well I can't seem to do that without an error. Maybe it's because I just tried to activate the VST on a different computer and it doesn't recognize the ID of this one. I may try that again later but this particular one requires other files to reside in the system as well which I believe the batch cmd installation failed to complete and I don't know where to place them manually or if that would even fix it.
The main problem however, the reason I made this thread still exists, I use Nexus 4 and the display still doesn't update. The VST starts blank and I have to mess around with the VST to get the preset display to show, also clicking a preset doesn't "update" or "refresh" the screen of the VST either.
Other than that I actually feel inspired to create again, I'm on an hdd on a distro that's very low on system requirements and this thing is feels just as fast as an sdd when I'm moving around in the program and such.
I just wish someone would make FL Studio and VST's completely compatible with Linux. Windows is just not for me anymore and I love FL Studio, I just want to Linux + FL Studio in peace lol. I have a Windows drive literally just so I can use FL Studio and I still haven't, because when I first installed it I find out in that moment that I have to pay for a freaking license key just to remove a watermark (without installing any 3rd party software) from the corner of my screen, that is insane and now they're discontinuing support for Windows 10 next year lol Microsoft just keeps moving further away from what made me stick with it for so long.
Re: Windows scaling issue in FL Studio
I'm with you in this. While I haven't had the most issues (at least now, but the GUI used to be glitchy just as you described, until it "magically" resolved itself, after a tweak that I'm not sure what it was) I still have a few problems - 64-bit plugins in general seem to work fine (to the extent that I tried, that is), but loading 32-bit ones (which there are a few that I use sometimes) cause the whole program to hang. Here's hoping more compatibility in the future in general, or a "miracle" that would be Image-Line making a native Linux version.
Re: Windows scaling issue in FL Studio
Your FL Studio GUI issues might be due to how Wine handles scaling on older hardware. Problems like text input issues and visual glitches could be related to outdated graphics drivers or hardware. Try updating Wine, adjusting its settings, and ensuring your graphics drivers are current. If possible, test on newer hardware to see if it resolves the issue. If the problem persists, it’s likely linked to your old system's limitations.
