Problem with Windows desktop scaling about classic-rbdoom-3-bfg

[MadDeCoDeR]

It quite known issue. It might be due to the new fullscreen code I have put in (more safe than before). I will investigate further and hopefully a fix for that issue will come in future releases (probably not the next one)

[MadDeCoDeR]

Well as it turn out the only thing I had to do was to make it DPI aware.
The new version is now available and the fix is included.

[TheVoodoo]

Weird... above 720p it works now as intended (thx for that) but it introduced a new bug...
When switching to 1280x720 it won't fill the screen at all ;)
I also noticed that the "revert" button doesn't work anymore when changing resolution in fullscreen.

[MadDeCoDeR]

For the resolution, quick question do you happen to have something like integer scaling active in your GPU ? I just test on mine (AMD RX 570) and once I disabled that the game was properly scaling to 720p.
As for the second welp that is something I forgot to change with the new fullscreen algorithm thanks for mentioning it.

[MadDeCoDeR]

And just reupload it with the fix for the revert button

[TheVoodoo]

I'm using a nvidia GTX1070. I'm not familiar with the integer scaling feature, but i checked the GPU settings and it seems that any setting that include scaling is disabled. I made a short video, it might help...

https://youtu.be/DAGEKMIUAuo

Btw, at video timestamp 0:53 i noticed another bug... If you click once in options on the arrow left/right selection, it infinitely circles through that option. You have to move the cursor away to make it stop.

[MadDeCoDeR]

I checked it with another PC that had nVidia and it seems that most likley to occur if you have toyed around with the adjust desktop size and position settings, try to set it on fullscreen and check how it behaves with both the GPU and the display scaling, and al;so see what the checkbox behaviour is.

Edit: as for the other issue, I will check it up.

[MadDeCoDeR]

New nightly releases come with a newer Windows 10 DPI awareness API. You can check if it resolves the issue

[MadDeCoDeR]

It has been an year without a response. Closing issue