ToME: the Tales of Maj'Eyal

Two quick notes on svn 3171: it's using ALL my CPU. Even when I'm not looking at that page in the FvwmPager.
The entire system is sluggish and horrible to use (like this web browser that I'm typing this in) while the game is running. This is the behavior I used to see in older betas (back around, oh, beta 14 or so?), and it didn't reoccur until just now.

Also, when I started my game in svn 3171, the first thing I noticed was that it said Saving: 0% on the left pane, and it never updated or went away. Even several zone-changes later, it still says that. I can never tell when it's actually saving, or when it's done.

Oh, crap... just found that it's MUCH WORSE than just a display glitch.

It's not actually saving.

After hitting Ctrl-X and exiting and restarting the process, there's no saved game. It's totally gone.

Maybe this is related to my attempt to band-aid the broken zlib. Maybe not.

Also, the minimap was totally white when I was playing in Trollmire, and stayed that way when I went into the wilderness and then into Derth. It was actually an attempt to pin down the minimap glitch that caused me to attempt to save-and-exit the program.

Tried copying *all* of the *.[ch] files from zlib-1.2.3.4/contrib/minizip/ into the zlib123 directory. This caused an error in building the iowin32.c stuff. So I deleted iowin32.c and iowin32.h and rebuilt.

New char started: minimap is still white. Still says Saving: 0% forever. Ctrl-X and there's still no saved game in ~/.t-engine4/4.0/tome/save.

So this time I removed all the *.[ch] files from src/physfs/zlib123/ and redid the "svn update -r 3171". This put me back to the zlib 1.2.3 as shipped with T4.

Then I commented out the code in src/lzlib/lzlib.c that checks the version string.

Then I rebuilt, and started a character -- and the "Saving: 0%" problem went away. I saw it actually progress from 0% and then go away.

The minimap is still white.