Brad Oliver
Civ3/4 Mac programmer
Originally posted by ejday
Okay, last night, after the first crash, I tried reloading the autosaves to no avail. After quitting, though, and coming back in fresh, it would load fine. Can djou essplain dis to me?
No explanation. If you ever come across a case where you can consistently crash Civ3 by following some fixed steps, then by all means e-mail all that info to me and I'll try and crash it here.
About the monitors: I was trying to get it to run in 1280x1024, which is offered in the monitor selection, top half. When I select it, I get an error: "DrawSprocket can not switch to the requested resolution (1280x1024, 16 bit, 1 something or other)," then it makes a rude comment about my mother and quits. Am I missing some caveat mentioned in an earlier post or is this just a shade of the beta blues?
Does your monitor support that resolution at "thousands" of colors? The resolution box in Civ3 doesn't check what your monitor supports when it presents those choices, so it's possible to pick one that isn't supported and then end up with the error message from DrawSprocket.
Something else a little weird: in the Saves folder, all the save icons come up as the little rosetta stone and tag as "Civ III data." The autosaves look like normal map icons and comes up as a normal "Civ III saved game." In the Auto folder, it also generated a "save.tmp" (as Civ III data), and it weighed in at 0 KB. Never seen that before.
That's all normal behavior.
...Speaking of memory, those unusual saves would load fine, and weighed in much lighter than the autosaves. To wit:
Lincoln, 1850 AD.SAV (data) @ 196 KB
~versus~
Civ3 Autosave 1850 AD.SAV @ 1.5 MB
A while back, they introduced compression for the saved-game format, so some files will be dramatically smaller. I believe there's an option in the game to have the autosaves be compressed, but they might have removed that from 1.29 for performance reasons. I don't remember the sordid history of it now.