When I start DoomLegacy 1.48.8 (rev 1567) under Win10 with doom2.wad and try to start a new game or load a saved game it crushes with no message. There was no such bug on 1.48.4
Need more information. I do not have Windows10 to debug upon.
Please start the game with a command line with "-v2", and attach to your posting the stderr and stdout files that are created in the doomlegacy directory.
doomlegacy -game doom2 -v2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looking at the stderr and stdout, there is not enough information to diagnose this.
In 1.48.9 there is a patch to video startup, to make it recover from video startup more gracefully, but stderr indicates that it got well past this point before crashing.
I will not be able to solve this by guessing at it. There are too many changes in 1.48.8 to guess at which is the problem for your setup. I am not reproducing the problem here.
I suggest trying some alternatives,like 800x600, and not using opengl, to start.
Cut it down to the most simple start that still produces the crash.
Try to discover what feature you choose gives the crash and which ones do not cause it to crash.
Did any OpenGL video at all display before it crashed ?
The attributes (Extensions) displayed in stdout short for any modern video card. I usually get near a full page of video attributes from the card. You got 1 line of extensions. I checked mine, and I too get only 1 line with my new motherboard with on-board video chip, so I suppose that has something to do with on-board video. Strange that it is an Intel video chip, but it has "AMD" video extensions.
The stdout says that an ogllog.txt file was produced. If you got that then please attach that too, as that is specific to OpenGL hardware.
Many of the fixes in 1.48.8 are related to supporting complex wads that violate the normal wad structures. But, I see that it was doom2 wad you were using, and the OpenGL code was not involved much in the patches, so we need to identify what it could be.
But, as I was not patching OpenGL code, it did not get tested much for the 1.48.8 release.
You will need to test with OpenGL and without OpenGL (such as "-native").
If you can get it to start using in a window, then you can use the video menu to test other display modes. The error reporting and testing using the video menu is much better than what happens in reading a mode from the config and trying to restore it on startup.
I expect that you are using a Launcher, because one of the output lines indicates that you were using autostart, such as warping to a level map. Try it without the autostart, just to see if that crashes too.
Please try to capture the exact command line that was used so that I can test that command line here on different hardware.
It may be dependent on something in your config file.
Try a direct command line start with a line that uses a different config.
The following will create a new config, "georg", that is initialized from default settings.
doomlegacy -v2 -game doom2 -config georg
Last edit: Wesley Johnson 2021-02-16
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I use new config with default settings I can start a new game and it works well. Then I go to Drawing options and select OpenGL. Screen resolution changes and I still can start new game. But it crushes in about 30 seconds in OpenGL mode.
If I make OpenGL the default option and then restart doomlegacy I can not run a new game, the program crushes. So the reason is in OpenGL mode, I did not touch any other options.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Need more information. I do not have Windows10 to debug upon.
Please start the game with a command line with "-v2", and attach to your posting the stderr and stdout files that are created in the doomlegacy directory.
Sorry for delay, please find requested files attached.
Looking at the stderr and stdout, there is not enough information to diagnose this.
In 1.48.9 there is a patch to video startup, to make it recover from video startup more gracefully, but stderr indicates that it got well past this point before crashing.
I will not be able to solve this by guessing at it. There are too many changes in 1.48.8 to guess at which is the problem for your setup. I am not reproducing the problem here.
I suggest trying some alternatives,like 800x600, and not using opengl, to start.
Cut it down to the most simple start that still produces the crash.
Try to discover what feature you choose gives the crash and which ones do not cause it to crash.
Did any OpenGL video at all display before it crashed ?
The attributes (Extensions) displayed in stdout short for any modern video card. I usually get near a full page of video attributes from the card. You got 1 line of extensions. I checked mine, and I too get only 1 line with my new motherboard with on-board video chip, so I suppose that has something to do with on-board video. Strange that it is an Intel video chip, but it has "AMD" video extensions.
The stdout says that an ogllog.txt file was produced. If you got that then please attach that too, as that is specific to OpenGL hardware.
Many of the fixes in 1.48.8 are related to supporting complex wads that violate the normal wad structures. But, I see that it was doom2 wad you were using, and the OpenGL code was not involved much in the patches, so we need to identify what it could be.
But, as I was not patching OpenGL code, it did not get tested much for the 1.48.8 release.
You will need to test with OpenGL and without OpenGL (such as "-native").
You wil see many more options to test if you do
Test
If you can get it to start using in a window, then you can use the video menu to test other display modes. The error reporting and testing using the video menu is much better than what happens in reading a mode from the config and trying to restore it on startup.
I expect that you are using a Launcher, because one of the output lines indicates that you were using autostart, such as warping to a level map. Try it without the autostart, just to see if that crashes too.
Please try to capture the exact command line that was used so that I can test that command line here on different hardware.
It may be dependent on something in your config file.
Try a direct command line start with a line that uses a different config.
The following will create a new config, "georg", that is initialized from default settings.
Last edit: Wesley Johnson 2021-02-16
When I use new config with default settings I can start a new game and it works well. Then I go to Drawing options and select OpenGL. Screen resolution changes and I still can start new game. But it crushes in about 30 seconds in OpenGL mode.
If I make OpenGL the default option and then restart doomlegacy I can not run a new game, the program crushes. So the reason is in OpenGL mode, I did not touch any other options.
Retest for 1.48.12.
Try using a smaller screen than 1920x1280. There may not be enough graphic memory to support such a high resolution OpenGL.