The game now ever since today just started crashing for me. I can do the initial start up, but after that anything from loading a previous character, to starting a new one, to trying to change even any one setting in options will straight up crash the game with no error. I would attach the te4_log file but it's like 16 MB big.
Also I notice a file also in the ToME folder called stderr that says this:
PANIC: unprotected error in call to Lua API (Unable to initialize: attempt to call a string value)
Game just straight up crashes
Moderator: Moderator
Re: Game just straight up crashes
Already reported. See http://forums.te4.org/viewtopic.php?f=42&t=28061
Re: Game just straight up crashes
We really need to fix that "bug" because it is a known red herring that constantly gets people. You don't need to post the entire log, just the bit at the end where the Lua error is. It sounds like you already looked for it, and it isn't too surprising you don't see it since the output is buffered and probably never written. Try this and see if you can see more in the logfile this time:
- Make a shortcut to the T-Engine.exe process
- Right-click on the shortcut and bring up Properties
- Find the field that has the executable in it
- Add "--flush-stdout" to the end, so it reads: "bla/bla/bla/t-engine.exe --flush-stdout" (no quotes)
- Use the shortcut to run the program
<DarkGod> lets say it's intended
Re: Game just straight up crashes
I have tried everything in the link and everything you guys suggested and nothing works.
Interestingly when I delete the error files and run the game hoping for it to make new ones it instead of just doesn't create any at all anymore, even with the shortcut mentioned above. I can completely clueless as to what's going on.
Interestingly when I delete the error files and run the game hoping for it to make new ones it instead of just doesn't create any at all anymore, even with the shortcut mentioned above. I can completely clueless as to what's going on.
Re: Game just straight up crashes
I just downloaded b38. A stderr.log file already exists in the package with the "PANIC..." error message, so the only thing to do is actually delete the file. Lol...