We recompiled one of our games, and when you run the winsetup.exe program, the "Desktop resolution" option is missing from the list of possible resolutions. Any ideas why this might be?
When we run it from the original folder, the "Desktop resolution" option is there, but when we move the game to another folder, it vanishes!
We are using v3.4.1.14
Ooh, I just noticed someone having the very same issue.
https://www.adventuregamestudio.co.uk/forums/index.php?topic=56699.0
The game we are compiling is Unavowed
The solution was:
Quote from: Chicky on Mon 17/12/2018 20:02:36
I tested eriOo's hypothesis as suggested by tzachs and it has resolved the issue. In windows 10 I right clicked the game's exe, clicked Properties, clicked the compatibility tab then 'Change high DPI settings', ticked the box for 'Override high DPI scaling behaviour' and set the drop down 'Scaling performed by:' to Application.
Sorry about the duplicate thread!
I recall similar thing happened only once before, when person had problems with DirectDraw5 initialization on his system and it gave different results every time when querying supported modes.
For that reason I made it so since 3.4.3 winsetup will be forced to display at least two "common" options there (desktop resolution and native resolution).
Thanks Crimson Wizard! Good to know this won't be a problem in the future.
Quote from: JanetC on Tue 02/07/2019 22:44:49
Ooh, I just noticed someone having the very same issue.
https://www.adventuregamestudio.co.uk/forums/index.php?topic=56699.0
But that's completely different problem? Maybe there's some kind of misunderstanding here.
Quote from: Crimson Wizard on Tue 02/07/2019 22:47:23
Quote from: JanetC on Tue 02/07/2019 22:44:49
Ooh, I just noticed someone having the very same issue.
https://www.adventuregamestudio.co.uk/forums/index.php?topic=56699.0
But that's completely different problem? Maybe there's some kind of misunderstanding here.
I think it was the same problem. The solution mentioned by Chicky in post 7 worked (we think)
I did some tests with the latest AGS engine on both Windows 10 1803 and 1903 and for me the problem is gone.