I use the windows settings to reset this every time the client is updated and set it back to ‘system’ override DPI. I do this because I want the full screen client to use a reduced resolution for better framerate on my pc and slightly larger text/gui.
This works because I have my windows display scaled to 125%. Last year(I think) the client used to assume the 125% DPI scaling automatically, since last year a change has removed this functionality so I have to do it manually with each release.
So to review the behavior I’m seeing is opposite between Studio and the Client
Studio:
respects my Windows DPI scaling to enlarge the Studio resolution (causes a small bit of blurring that a lot of users dont’ like, hence the creation of this thread. I don’t mind this scaling, I actually prefer it).
Client:
does not respect my Windows DPI scaling and runs at full resolution (causing me to have to set override each time the client is released to get my client to scale the full screen resolution to my 125% preference, which effectively lowers the game resolution, increasing frame rate)
I don’t have much insight into the Client side of these issues. I will follow up with a the driver of these features on Client, and try to get a response for you guys.
What screen resolution and what DPI scale factor do you have set in your OS? These heavily downscaled screenshots say very little.
The intended behavior is that the Roblox client will scale based on the DPI setting in your OS, just like the OS itself as well as other apps on your PC. The default DPI scale is generally set to match what it would look like on a low-DPI screen (e.g. a 4k screen will be set to 200%, so that UI will be the same physical size as it would be at 1080p at 100%), but you can change this easily.
It’s not clear to me whether you’re experiencing something other than the intended behavior, or if you’re unhappy with the intended behavior. If you want the UI to be smaller than normal, then I’d suggest changing the scale setting in Windows.
Here’s what it looks like on my 4K 28" display, with 200% scaling set in Windows:
I’m not sure what other user’s issues are with the client dpi scaling but from what you describe, you and I are talking about two different things. (I don’t want it to enlarge the text at max resolution)
This is what my client does every time a new client is rolled out:
my client runs at my display max resolution (I do not want this)
I quickly verify the resolution by taking a screenshot and examine the resolution of said screenshot (1920x1080, again, I do not want this)
After I go into the shortcut and compatibility tab, and select dpi setting override, set to ‘system’ then:
my client runs fullscreen at the 125% scaled resolution(or whatever scale you choose). my client runs higher fps due to lower total resolution required
I quickly verify this by screenshot showing the resolution is 1536x864
Try your screenshot again with the shortcut modified as I have described and see the difference in your display. If your client is truly respecting the DPI settings defined by the system, then override with ‘system’ setting should match(spoiler alert: it does not)
edit:
from what I can tell from the behaviour of Studio compared to this, it is the opposite, it does respect the system scaling and enlarges the gui as needed (which I prefer, but the author/OP of this thread does not, and would like it to not resize the Studio GUI and he is forced to update his shortcut with every release opposite to what I’m doing with the client)
Having the client use the native resolution of your display is intentional. When I take screenshots in-game, the output is 3840x2160.
It shouldn’t be harming your performance this significantly though. The client is supposed to render the 3D content at a different, lower resolution, and only 2D content (mostly UI) is rendered at native resolution. On my display, the 3D content renders at 1080p, and only 2D content renders in 2160p.
Okay, but why does telling the compatibility dpi override to use ‘system’ get me a different game resolution? (if the client is using the system scaling, which is only seems to do if i select override)
Last year(I think) something was changed in the client to make the new/current behavior, before that I didn’t have to change my shortcut to get the reduced fullscreen resolution(still fullscreen size).
I don’t know if there is a way to please everyone with this, unless you come up with a way to make the new shortcut inspect and replicate the old shortcut’s settings. The ‘we want Studio tiny/native res’ people will have to keep changing their shortcuts. The ‘we want fullscreen client low res’ people will have to do the same. (maybe this is just me, idk)
The point is that we can keep the set 200% and have Roblox not adapt by the setting set by Windows.
I don’t want to change it to 100% so that Roblox fixes on this device. If I would set the setting to 100% it would be fine. However, before I was able to use ClientSettings, so that I can keep something like 125% and run Roblox with 100% without having to change the setting, aka. it will ignore and not DPI scale.
I don’t want it to DPI scale. How can I achieve that without ClientSettings now? I mean ClientSettings allowed to set other fast flags as well. What happend to the FFLags?
After testing at full res I was impressed that the performance is really comparable as you say. But it still seems I could get the framerate to drop into the 55 fps range at times, vs when at the 1536x864 res I can’t really get it to drop below 59fps and is mostly pegged at 60.
I think the another thing that throws me off about it is that it modifies my field of view a bit compare:
low res(dpi override:system 125%):
again this behavior seems to me as if the app is ignoring the dpi scaling since when i set it to override with system pref it lowers the res, it changes it. If the dpi scaling was working i would expect system override and application(default) to be the same. (as it is with Studio)
Or maybe this is due to override treating it like a dpi unaware app? At any rate, I like the low res and wish there was a way to have the new shortcut that comes out every week or so be a copy of the existing shortcut somehow so I wouldn’t have to keep modifying it.
Your problem is the opposite of mine. Studio applies the scaling and adjusts the gui accordingly and you want it to ignore that. Which you can do by modifying the shortcut but you’d have to do this every release.
To achieve this now, you can set your Studio shortcut as follows:
