GZDoom just updated to 3.3.1 in the interim, so these logs were taken with that version.
Seems like it, I was wondering why it was listing resolutions my computer had no possible way of supporting while not listing resolutions I could see with xrandr.
_mental_ wrote:Same for Cocoa backend.
I'll merge both lists into one to make sure all resolutions are available. List of video modes was updated in
fdd93d7.
Thanks! Got the update a while ago.
_mental_ wrote:
Have no idea why it crashes though. Could you please provide a crash log?
Actually, I've suddenly got it crashing whenever I use +vid_setmode now... I renamed gzdoom.ini to gzdoom-bak.ini and started with this command line:
Code: Select all
gzdoom -iwad DOOM2.WAD -glversion 3 +vid_setmode "1680 1050"
and it crashed
with this error log.
Thinking this was just because the video mode was listed as unsupported, I tried it with 1280x720.
Code: Select all
gzdoom -iwad DOOM2.WAD -glversion 3 +vid_setmode "1280 720"
That crashed
with this error log.
Not including vid_setmode whatsoever successfully started GZDoom with a 640x480 window. Further attempts to use vid_setmode on the command line crashed. Using vid_setmode inside the engine worked successfully.
Then it gets weirder.
After starting the engine, I used vid_setmode 1680 1050, and went to the video options menu to switch to fullscreen. Due to the update, sure enough, the video mode was listed and highlighted in the video options menu. then I shut the engine down and started it up again and it booted... in 640x480 fullscreen. I went to the video options menu and set the resolution correctly and restarted and for some reason it stuck this time. I guess setting the video with vid_setmode isn't getting saved to the config?
I don't know what's going on anymore I'm so sorry.
GZDoom just updated to 3.3.1 in the interim, so these logs were taken with that version.
[quote="dpJudas"]The Linux port only has a [url=https://github.com/coelckers/gzdoom/blob/master/src/posix/sdl/sdlglvideo.cpp#L118]hardcoded list[/url].[/quote]
Seems like it, I was wondering why it was listing resolutions my computer had no possible way of supporting while not listing resolutions I could see with xrandr.
[quote="_mental_"]Same for Cocoa backend. [s]I'll merge both lists into one to make sure all resolutions are available.[/s] List of video modes was updated in [url=https://github.com/coelckers/gzdoom/commit/fdd93d704d3293ea9c28b81f5a365f5773fd22e2]fdd93d7[/url].[/quote]
Thanks! Got the update a while ago.
[quote="_mental_"]
Have no idea why it crashes though. Could you please provide a crash log?[/quote]
Actually, I've suddenly got it crashing whenever I use +vid_setmode now... I renamed gzdoom.ini to gzdoom-bak.ini and started with this command line:
[code]gzdoom -iwad DOOM2.WAD -glversion 3 +vid_setmode "1680 1050"[/code]
and it crashed [url=https://gist.github.com/Orangestar12/aa76e433dad8015fad24b3b613d84ce5]with this error log.[/url]
Thinking this was just because the video mode was listed as unsupported, I tried it with 1280x720.
[code]gzdoom -iwad DOOM2.WAD -glversion 3 +vid_setmode "1280 720"[/code]
That crashed [url=https://gist.github.com/Orangestar12/9c827f071e01a21a4f8ebcd773cdc40a]with this error log.[/url]
Not including vid_setmode whatsoever successfully started GZDoom with a 640x480 window. Further attempts to use vid_setmode on the command line crashed. Using vid_setmode inside the engine worked successfully.
Then it gets weirder.
After starting the engine, I used vid_setmode 1680 1050, and went to the video options menu to switch to fullscreen. Due to the update, sure enough, the video mode was listed and highlighted in the video options menu. then I shut the engine down and started it up again and it booted... in 640x480 fullscreen. I went to the video options menu and set the resolution correctly and restarted and for some reason it stuck this time. I guess setting the video with vid_setmode isn't getting saved to the config?
I don't know what's going on anymore I'm so sorry.