Ankmairdor
Member
- May 1, 2019
- 275
- 156
The first log is little bit weird but contains no particularly useful information. The first oddity is that it is missing a standard warning that appears whenever the game dynamically generates a list of buttons, which the mod menu does and based on the text you were applying mods. The second oddity is that the warning and error are only the second half of the standard messages issued when the game closes. I have no idea what type of problem could cause these oddities, but likely some kind of conflict between your computer and Godot.Hi, this game used to work great for me but then I got a new computer and it keeps crashing. I completely deleted it, reinstalled it, tried it with zero mods, with the debug fix mod and it still keeps crashing. This is the error I keep getting from the log:
You don't have permission to view the spoiler content. Log in or register now.
Anyone know how I can fix this or can it be fixed? I actually really enjoy this game and it'd be a shame if I can't get it to work. I was running it a full screen, but then after one of the attempts I kept it default size but still crashes regardless.
Additional: I tried again with the 32.dll recommended on the open post, as well as deleted the inbuilt mod completely. It crashed again on start and I got this error this time:
You don't have permission to view the spoiler content. Log in or register now.
For the second log, I have no idea what opengl32.dll does, but the new error appears non-nonsensical as the line number it mentions does not have any "for" loops for vanilla or for the Bugfix mod. So unless there are other code alterations that you have made, that does not appear to be helping.
You mention the "debug fix mod" but there is no such mod; there are the Debug mod and the Bugfix mod, which are separate mods with different intended effects. The Bugfix mod fixes many mechanical problems with the game, but will not help against a crashing game. The Debug mod can be used to display errors to a terminal while the game runs; however, that terminal usually closes when the game crashes and the log files are not updated if the game suddenly crashes rather than closing normally.
The way around that is to run the executable provided by the Debug mod using the Command Prompt to keep the list of errors visible after the game crashes. The 2 basic commands to do so are "cd <YOUR_PATH_TO_STRIVE_FOLDER>"(replace <> and contents), and the next is the name of the debug executable.
In order to locate the cause of your problem it may help to have more specific information. Seeing as you were able to run the mod system and possibly the options menu it appears that the game is not crashing on start up, so after what specific action is it crashing?