Vegastrike changes screen resolution to 1024x768, leaves desktop unusable

Running Vegastrike (from games repository) with default settings changes the desktop resolution to 1024x768, which in my case resulted in timings outside of my display’s (Eizo Flexscan EV2450) accepted range, causing it to display only “SIGNAL ERROR”. Unfortunately that new resolution was saved in the $HOME/.local/share/kscreen/ state files, so it was set again on a new login, thus leaving the desktop permanently inaccessible. It was a devil of a time to find those state files… deleting them fixed the problem, as KDE now chose a valid default resolution.

The resolution of Vegastrike can be changed with the vegasettings program. Changing it to 1920x1080 made it playable.

Now my questions are: why is Vegastrike able to set the display to a resolution which is not supported by the graphics card/display pair? And why does this invalid resolution get saved so it is restored on the next desktop login? Should the Xorg server not refuse setting such a resolution? It gets the valid timings from the display via DDC, after all.

unfortunately, this can happen with changing display settings. In my opinion, bieng able to change your screen resolution away from the default or ‘supported’ by your monitor is beneficial because it ultimately gives you more controll and helps significantly when trying to configure monitors that arnt quite displaying images correctly.

there is a fix for this problem however which involves removing spesific resolutions from your system using xrandr.
Preface to solution: run at your own risk. you will also need to be in a different resolution to remove it.

NB: switch to your root user with su [root username] or sudo su

Step 1: use xrandr to list al of your current display resolutions

command: xrandr

you should get a result containing resolutions and refreshrates similar to this:

1360x768       59.8     60.0
1152x864       60.0
1024x768       60.0

step 2: remove resolutons that are unsuported by your monitor

NB: to find resolutions that are unsuported, compare your monitors officially suported resolutions with the ones xranr listed, or open your settings app in kde and switch to each one to see which ones cause an error (it should reset to previous resolution in a timelimit if you do not click ok…)

once you have determined the resolutions which do not work, you can put it into the xrandr command with the --rmmode flag. an example is: [DO NOT RUN UNLESS YOU WISH TO REMOVE THIS SPESIFIC RESOLUTION]

xrandr --rmmode 1368x768_60.00

to remove the resolutions you have determined to be problematic, consult the previous xrandr command to find your resolution I.E 1368x768 and the refreshrate directly to its right, I.E 60.0.

next, format the command with your resolution, an underscore and the refreshrate. see above for the example again

NB: you may need to remove the resolution again with the alternate refreshrate if it is not removed the first time. simply repeat the steps after a reboot to try again.

Why game devs change the resolution:
Game developers often set the resolution of your monitor so their game can run full screen without a window box. this means that if the resolution is unsuported, it will effect your monitor. this can be fixed by ether changing the default resolution the game will run at or removing the resolution entirely. this will ether cause the game to launch windowboxed, into a different resolution or not at all if it cannot run in such a manner.

I would reccomend telling the game developers about this issue however because it might effect other users.

by shutting down your system when the monitor blanked, you set the resolution as the last used before powerdown. this means whn you boot up, you will be forced beck into the resolution. to stop this from happening, quit the game before you shut down. this will allow you to return to normal resolution and then be able to boot up into it.

if ytou have any problems with above, please reply and I will do my best to help…

1 Like