ToME: the Tales of Maj'Eyal

Basically, I go about and create a character, put in the 3 stat points, hit tab and then the whole game crashes and logs me out of my account (on the computer). Any ideas?

EDIT: I just tried something: I can go from the STATS tab to the SUMMARY tab, but when I try to go to the TALENTS tab, it just dies. Hope it helps

If you're running the Windows version, look for a file named stdout.txt in the ToME directory. Or at least I think that's the name... it might be slightly different. Look for errors in there, to indicate what's happening.

General hints (may or may not apply here):

If you're upgrading from a previous version, don't just unpack the new ToME archive in the old directory; unpack it in a brand new directory (either by deleting the old one, or by using a different name).

Make sure your video drivers are up to date. ToME uses a lot of OpenGL graphics functions, and is surprisingly (for a roguelike) graphics-intense. Buggy or outdated drivers can cause crashes, and some older graphics cards have serious problems or are missing support for many of the features.

I'm running the linux version. It's been a while since I've tried there, booted into windows and tried ToME there and it works just fine, albeit a bit slower than I'd like, but eh, that's windows for ya. I'll post the stdout in a few hours, I have some other business to take care of first.

The Linux version writes stdout to stdout -- you're expected to be able to redirect it yourself. I would also suggest using the --flush-stdout option so that the log file isn't truncated (due to buffering) when you crash.

What I normally do is mkdir logs and then every time I start t-engine, I redirect stdout+stderr to logs/Charactername thus:

./t-engine --flush-stdout >>logs/Charactername 2>&1

Yes, this means I have to choose the character name first, before even starting the program. :-/

This has many benefits. First, as mentioned, it means I get a full log in the event of a crash (which I haven't actually experienced in a very long time - yay!). Second, it means I have in-game chat logged in realtime, so I can open a second window and do a tail -f | grep on the log file to see the in-game chat that I would otherwise miss when it scrolls irretrievably out of the tiny little window after 0.03 seconds because I happened to be fighting at the time. Third, after I die, I can review the log file to attempt to see what happened.

You know you can click on the game log to see a larger window of your message history? Quite handy when something gets scrolled off your screen.

Oh... no, I didn't know that. How new is that?

Since b26. You mean to tell me everybody doesn't read every line of the changelog of every release?!

Anyway, I'm really hoping the new UI in b29 will have a similar easy, intuitive click like this to see the message.

Okay, here's the stdout for when it crashes... I did the command and the results are attached to this post.