4.35 Output Resolution problem
-
Hello, I am using BMS version 4.35.3. In the settings, the Resolution is 1920x1080, but the Output part is Display 1/// 0 0 1024 768 and the resolution looks very bad. Can you help me?
I’m sorry for my bad english.
-
Hello the resolution in menus is always 1024x768, the resolution you see below(1920 x 1080p) is applied in 3d, so if you have the right resolution in 3d you can’t do anything else.
-
It seems a bit strange that you do not get more options in the Output dropdown. Assuming that you are not on a 1024x768 monitor, that is. What kind of computer or laptop are you running on ?
In the screen you show, try and change Window to Borderless. Then press Apply and restart BMS.
For reference, these are my settings:
Even though my settings say 1440p, running borderless my UI displays in the legacy 1024x768 format. Which is what it is for the time being.
-
I think the “Output” dropdown is about selecting which monitor to run on (if you have multiple monitors)
And “Resolution” dropdown is about selecting what resolution to run BMS 3d world, on that monitor.
(Although if you select ‘Borderless’ mode, which is highly recommended, then I think it just uses the native Windows desktop resolution and refresh rate?)
-
@airtex2019 I agree with you on Output and Resolution controls. When I select Output I see my monitors in a drop-down. Which is why I find it strange that OP only sees a 1024x768 option in that case. That would be an unusual setup
-
@jayb
It’s complicated … in Borderless mode it’s showing us our monitor’s current (native) resolution.If in Fullscreen-exclusive mode, it tells the monitor to switch to 1024x768 mode while in 2D. (Note sometimes depending on Nvidia console settings, the GPU will “fake” it and perform scaling on the GPU instead of asking monitor to change modes … so the monitor may stay in its happy native resolution … but in such case I think it still enumerates to the OS/DirectX as a 1024x768 monitor.
And it’s all further complicated by the values on the BMS screen don’t update unless you exit and re-open the Setup screen…
-
Interesting, so that is why he sees that legacy resolution.
They should really do away with Fullscreen mode altogether, or at the very least make Borderless or Windowed the default setting. One can always Alt+Enter to scale up 2D temporarily. On some monitors the scaling can be bearable
-
@33ismet99 said in 4.35 Output Resolution problem:
Hello, I am using BMS version 4.35.3. In the settings, the Resolution is 1920x1080, but the Output part is Display 1/// 0 0 1024 768 and the resolution looks very bad. Can you help me?
I’m sorry for my bad english.
Which native resolution has your monitor?
-
They should really do away with Fullscreen mode altogether,
In another thread (about bugginess of [alt+enter]) I think some of the devs reached basically the same conclusion.
But for those of us with 4k monitors… the 1024x768 2D window is almost impossibly tiny. (Can’t imagine 8k.) And it doesn’t do Windows dpi-scaling.
If they could make the 2D window do DPI-scaling properly (or internally, uniform-scale it to fill the screen, like the 3D borderless window), I think it would eliminate the need to support FSE mode (and the complexities of [alt+enter] mode switching).
-
@airtex2019
I am not on a 4K, but I am on 1440p and the UI is very small indeed. At some point I used 150% scaling through this Windows feature. That worked out to be a nice compromise between hideous full-screen and the UI being way too small. Only thing is you need to scale back to 100% before committing to 3D -
@jayb Why the scale back to 100%? I honestly set it and leave it at 150%. I thought the issue was 3d menu/subtitles sizing but it hasn’t given me issues.
-
You can leave it at 150% if you like. Once I go and fly, I prefer to fly in 3D in my monitors native resolution (ie. 100% scaling).
I found that the upscaling to 150% was most useful for me for the 2D work, to basically have a larger map in the map room. When it was time to commit, I scaled back again to 100% (native)
-
-
does this mean the UI will be at lower resolution until further update?
i have the same issue, output will be 1024x768 as a max setting on display if fullscreen is selected. otherwise if set to borderless my output max is my native monitor resolution of 1920x1080 -
Thank you all.
-
@airtex2019 That is what I was experiencing. The 2-D screen was so small, even on my 65", I couldn’t read it. What i did find out is when I used NVIDIA CP to set windows monitor resolution, it didn’t affect the BMS 2-D window size. I had to use windows display properties, and set my monitor to a lower res. The 2-D window now takes up over a quarter of the monitor.
-
@mailman Not sure if mentioned already in this thread or a different one – but it’s also possible to use [Win+NumpadPlus] to enable the Magnifier tool, to navigate the 2D screens.
Then [Win+Escape] to cancel it, as you transition from 2D to 3D…
-
Hi everyone.
Try this:
In the shortcut to bms, right click and properties, compatibility tab and click the “disable full screen optimizations” box, accept and that’s it.
-
@sniper29 said in 4.35 Output Resolution problem:
Hi everyone.
Try this:
In the shortcut to bms, right click and properties, compatibility tab and click the “disable full screen optimizations” box, accept and that’s it.
Can you clarify – what effect does that have, for your setup – more reliable [alt+enter] and [alt+tab] behavior in fullscreen mode? Or better scaling for the 2D window?
I don’t think that setting can help with DPI scaling issues (the small 2D screen on 4k and higher resolutions).
https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/
Sounds like it just helps reduce DWM input-lag for games running in a borderless-fullscreen window. I haven’t measured to see if it provides any benefit for BMS, but it doesn’t seem to be causing any problem on my system.
-
Great heads-up, thank you. This setting really improves the Alt-ENTER behaviour in BMS to toggle the 2d GUI to fullscreen mode and back to native desktop resolution (more) reliably.
All the best,
Uwe
-
This post is deleted!