BigBox DPI Scaling not working correctly

[Makotosan]

Hello,

I just started using launchbox & bigbox on my PC and i noticed that the DPI scaling isn't right with the latest version.
I'm using a 4k TV with 300% (default) windows scaling.

I tried disabling windows (10 22H2) DPI scaling in the .exe property (using Application) but there's no change at all and the application is still following windows's DPI scaling settings.
Every theme is more or less affected with either not correctly scaled images or text (too big), that renders BigBox quite unuseable for me.

Is there another setting allowing to correct that? Is that a bug?

Edited June 11 by Makotosan

[faeran]

Custom themes are designed in the way that the author of the theme intended, so depending on how the theme was coded, it would determine how the default Windows DPI settings affect it. Most themes tend to get built to ignore DPI settings so that the theme can display the same way regardless of resolution or DPI settings.

The second screenshot you posted is actually not text being cut off, but it's an image used in the wheel that gets auto-generated and then cached for when you do not have a clear logo image for a specific game. My guess is that after you changed your DPI back, you may simply need to clear your cached images so it can regenerate one at the correct DPI setting. The setting is found under Options > Image Cache

[Makotosan]

Thanks for your reply, this is what i suspected indeed.

I guess most themes were designed with 1080p/1440p in mind and with 100% or 200% at most scaling, i noticed 300% breaks a lot of things and this is 4k scaling default (and much needed on TVs).
The image generated was generated with the default DPI setting for 4K (300%) so i suppose i should've generated them with 100% using LaunchBox.
Well, for the moment i can't use BigBox like this, some themes could be used with fewer glitches due to the scaling but still not my favourite ones.

May i suggest at least one or two things (just assumptions, i have no access to the code at all, don't take it the wrong way please)

This problem could be solved by reworking BigBox resolution handling and i mean by that: making it resolution aware, not letting themes setting explicit pixel sizes or windows DPI tied ones and managing DPI settings globally, this is what a true fullscreen app does. I also understand this would be tremendous work i'm sure of it and also would introduce many breaking changes in the existing code.
But according to your post, this capability may be already in place actually, and old themes compatibility aside, i think this should be enforced for every themes, ultimately they should be rendered regardless of resolution and windows DPI settings by the application.
As for themes that were made with windows DPI scaling awareness the second solution could solve that problem.

A "soft" solution would be to allow "resizing" the whole interface or scaling it regardless of the windows settings because i still don't understand why letting the application specify its DPI settings does strictly nothing (it should scale to something else than 300%), does the theme itself default to the windows settings regardless? (can't we just force it with a parameter for instance?)
This could solve this kind of issue and allow using any themes no matter what resolution/DPI scaling they were made for.

I love LaunchBox features, but it's a shame this issue comes with BigBox.

 

Edited June 13 by Makotosan