FMod’s default UI scale is very big on my screen, I tried changing Edit > Preferences > Interface > Force Device pixel factor to … but %100 is too small and %125 is too big.
How do I fix this?
FMod’s default UI scale is very big on my screen, I tried changing Edit > Preferences > Interface > Force Device pixel factor to … but %100 is too small and %125 is too big.
How do I fix this?
Hi,
Unfortunately, there’s no way to modify the pixel device factor in the Preferences menu outside of the values provided - as someone who uses a 1440p screen, I can definitely empathize with wanting a middle ground between the two values you listed, so I’ve added it to our internal feature/improvement tracker.
That said, as a workaround, if you navigate to your 2.02.00 config file, you can add or change the “forcedDevicePixelRatio” property to set a specific value:
<property name="forcedDevicePixelRatio">
<value>1.14999998</value>
</property>
I find 1.15 to be a good middle ground, but feel free to mess around with it and find a value that suits you. If you do find one you like, could you please let me know what it is, and also your screen size and resolution?
If you’re on Windows, you should be able to find Studio.02.02.00.config
at “C:\Users\YourUsername\AppData\Local\FMOD Studio\Settings”. If you’re on Linux, you should be able to find it at “~home\FMOD Studio\Settings”. The only downside to this is that reopening the preferences menu will reset the property in the config file, so you’ll need to set it again.
Thanks for the answer but when I tried it any thing under 1 would make it the same size as %100, and anything over 1.1 would make it the same size as %125
So that I can confirm the behavior you’re describing, what version of FMOD Studio are you using, and what platform are you on?
I’m using FMod 2.02.15 and I’m on windows 10.
Unfortunately, I cannot replicate the value-snapping behavior you’re describing.for values over 1. If I perform the following steps, I have no issue setting a custom scale with 2.02.15:
Studio.02.02.00.config
fileStudio.02.02.00.config
Please give those a shot and see whether you can set the value without any issue.
Sorry it took so long, I tried it but nothing changes it also automatically unchecks the "Force device pixel scale factor” checkbox for some reason?
No problem. Unfortunately, I’m unable to reproduce that behavior on my end either. That said, a fix for this issue is in the works, and should be included in a future release.
I fixed it by getting a 1080p display
Not sure if this works in Windows 10, but in 11, changing the DPI settings on the shortcut did the trick for me.
Happy to hear you’ve found a workaround - a 115% pixel scaling option was added in 2.02.17 to provide an option between 100% and 125%, so give that a shot too if you’re able to.
In 2.02.18 the 115% pixel scaling option does nothing. It is identical to 125%. FMOD is unusable on 1440p screens except if we force the DPI through windows (which makes the FMOD UI really blurry). Could you look into this? @Leah_FMOD or let us know if it’s fixed in newer versions?
Hi,
I’m unable to reproduce the issue you’re describing. When testing on Win 10, with 2.02.18 and a 1440p screen, after setting the “Force device pixel scale factor” setting to the desired value and restarting Studio, the scale factor is updated as expected. There’s a small but noticeable difference between 115% and 125%:
What version of Windows are you using? Can I get you to upload a screenshot of 115% vs 125% demonstrating the issue?
I ended up here because I also thought the 115% option didn’t work. I took screenshots and there is indeed minimal changes but the 115% is still too big for my screen (2560x1600 16" Lenovo Legion Win11 latest)
So I’m left with two choices : use Windows’ high dpi scaling to get the right size but the text is blurred, or loose a lot of real estate on an already small screen.
I guess more granularity in the pixel scaling options would eventually fix the problem, but will it make everyone happy?
Best,
jedd
I’ve added this to our internal feature/improvement tracker. As a workaround for now, you can try doing what I suggested above in this thread and modify your Studio.02.02.00.config
file to force the desired scale factor. If you could give that a shot and let me know what value works best for you, that’d be great.
This is an old thread already. For me, forcing “device pixel scale factor” to 150% did the trick
I’ve recorded a little video showcasing how confusing the scaling can be. Even with direct access to more values via the config XML.
(With a terrible mic quality sorry, laptop integrated mic)
My main gripe is that jump from 1.000 to 1.002. It seems any value of 1 or less seems to consider the base unit to be a real pixel, whereas other values seem to add to my OS’s base 1.5x zoom.
(Specs in the message above and in the video)
EDIT: In fact it would be nice to see negative zoom options like 90%, 75% etc. If that makes sense : it would allow me to “counteract” the OS zoom level a little bit.
Thanks for the detailed video! It really makes the issue clear. I’ve passed it along to the development for further investigation.
Just to follow up on this, can I get you to confirm what version of FMOD Studio you’re using? There was a known issue with scaling on some screens, typically higher resolution, that has been fixed as of 2.02.23. If you’re using a version below that, I’d recommend updating to that version or above and seeing whether it resolves the issue.
I downloaded 2.02.25 and it seems to behave better indeed. I’m happy to see that the behaviour I recorded wasn’t intentional!
Thanks Leah for your time and your energy in the matter