ToME: the Tales of Maj'Eyal

Hi,
I checked on the forum/internet to see if that was a common problem or not. Looks like it's not.
So I tried the game today. The game worked well. I was able to play, save and all.
I failed my skill choices with my first character so I made a new character. When I save with that new character : the game crashes (with black screen) and the computer restarts.

I reinstalled the game in a different directory, I even created a new game account, the problem is still there. The game still works but if I click on save, it crashes 100% of times.
I don't think it's a problem from my computer since the game worked well with the first character.

I created a forum account just to see if there is an easy way to resolve this or not.

Thank you

You might want to post the te4log.txt file (or the latter few pages from saving, anyway) here, making sure to post it after tome crashes, but before you open tome again. That'll let the devs have more information relevant to the issue.

Your problem might be related to this one.

I have black screen + computer restarts. Not a blue screen.
ty still
I put a te4_log.txt attached

It's very strange that these blue screens are happening for a small set of users. TE4 and its required libraries do not need any special elevated privileges, and really shouldn't be able to take down a system.

From the thread that stinkstink linked, it looks like there is an issue with taking screenshots for some users. Here's a modified executable with a slightly different sdl_get_png_screenshot function. Can you please unzip this executable to your t-engine-windows-1.0.1 folder, run it, and hit printscreen while in the main menu? If you don't bluescreen, you're golden and I'll send a patch off to Darkgod. Either way, please let me know how it works out. Thanks.

johnnyzero wrote:It's very strange that these blue screens are happening for a small set of users. TE4 and its required libraries do not need any special elevated privileges, and really shouldn't be able to take down a system.

From the thread that stinkstink linked, it looks like there is an issue with taking screenshots for some users. Here's a modified executable with a slightly different sdl_get_png_screenshot function. Can you please unzip this executable to your t-engine-windows-1.0.1 folder, run it, and hit printscreen while in the main menu? If you don't bluescreen, you're golden and I'll send a patch off to Darkgod. Either way, please let me know how it works out. Thanks.

Tried this exe but unfortunately it still crashes.
Could you please compile a version like this without the sdl_get_png_screenshot call?

I have black screen + computer restarts. Not a blue screen.

That is a blue screen with Windows set to restart immediately.

I tried the exe.
The game still crashes if I save
The games crashes if I make a screenshoot too.

Blacks/blue/screen + computer restarts

Two things to try:

First is trying the original 1.0.1 t-engine.exe with a libpng15-15.dll compiled by someone else. You can grab a copy from the pgreloaded project and try their DLL out.

Second is a t-engine.exe with the guts of sdl_get_png_screenshot ripped out, as requested by AIAndy. This should let you play the game, but you lose all screenshot functionality.

In any case, attempting to write a PNG to a file should not be able to bring down a stable modern windows system. The OS should be able to see "hey this user code is doing something really wrong", terminate the process, throw up an error dialog, but otherwise continue running normally. My guess is that there are underlying hardware or driver issues on your systems which are being triggered by the way libpng 1.5 writes files.

After you get to play TOME for a bit, can you guys please let me know which motherboards + storage you have?

johnnyzero wrote:Two things to try:

First is trying the original 1.0.1 t-engine.exe with a libpng15-15.dll compiled by someone else. You can grab a copy from the pgreloaded project and try their DLL out.

Still crashes.

Second is a t-engine.exe with the guts of sdl_get_png_screenshot ripped out, as requested by AIAndy. This should let you play the game, but you lose all screenshot functionality.

Thank you.

In any case, attempting to write a PNG to a file should not be able to bring down a stable modern windows system. The OS should be able to see "hey this user code is doing something really wrong", terminate the process, throw up an error dialog, but otherwise continue running normally. My guess is that there are underlying hardware or driver issues on your systems which are being triggered by the way libpng 1.5 writes files.

I agree. Only a driver can cause a blue screen in modern Windows systems. So it is clear that something in the way taking the screenshot is done triggers a bug in some driver.

After you get to play TOME for a bit, can you guys please let me know which motherboards + storage you have?

Mainboard: Gigabyte GA-EP35-DS3L
Hard disk: Samsung HD103UJ
Graphics: NVIDIA Geforce GTX260

AIAndy, thanks for the hardware info. I'm glad that the screenshot-less build is working for you. However, can you please test a new build with an older libpng library? Grab the SVN 6580 build and extract it over your 1.0.1 install (you probably want to backup your working t-engine.exe and DLLs just in case it crashes out again).

While it would be great to fix the true source of the bluescreen, it might be better to sidestep the issue provided other users aren't affected and newer libpng features aren't needed.

johnnyzero wrote:AIAndy, thanks for the hardware info. I'm glad that the screenshot-less build is working for you. However, can you please test a new build with an older libpng library? Grab the SVN 6580 build and extract it over your 1.0.1 install (you probably want to backup your working t-engine.exe and DLLs just in case it crashes out again).

While it would be great to fix the true source of the bluescreen, it might be better to sidestep the issue provided other users aren't affected and newer libpng features aren't needed.

Thanks for your attempts at fixing this problem.
Unfortunately I have to report that the blue screen happens even with the old libpng.