If there was a dump zip created in [b]C:\ProgramData\Stardock\Elemental - War of Magic[/b] ([b]C:\Documents and Settings\All Users\Application Data\Stardock\Elemental - War of Magic[/b] on Windows XP), please post that too.
kryo
Please open your debug.err file in notepad, and link the contents into a post here via [link="http://pastebin.ca"]pastebin[/link]. This will give us some technical information that can help troubleshoot your problem. The file can be found in [b]My Documents\My Games\Elemental[/b] Be sure to copy the debug [b]immediately after the error occurs[/b]; if you start the game again, the debug log will be erased and recreated for the new session.
If you still have the beta installed there should be an uninstall option in the right click menu, but it'll force an uninstall to upgrade to 1.x either way. If you continue getting decompression errors, please contact [email protected].
Looks like the same on-turn crash that we've already fixed for tonight's update.
Are you sure? There should always be a debug.err file--the game writes it continuously from the time you start it. Even if it doesn't appear to show anything useful, the technical details may offer some clue.
Attacks fully absorbed by armor register as misses--that's most likely what you're seeing. Training archers in parties, squads, or companies should improve their damage.
If your debug.err ends in the units/cities in world counts on a new turn, it's one we've already fixed for tonight's update.
It's propagating to the CDN mirrors.
Please open your debug.err file in notepad, and link the contents into a post here via [link="http://pastebin.ca"]pastebin[/link]. This will give us some technical information that can help troubleshoot your problem. The file can be found in [b]My Documents\My Games\Elemental[/b] Be sure to copy the debug [b]immediately after the error occurs[/b]; if you start the game again, the debug log will be erased and recreated for the new session.
The Snathi are losing their drake king so you can't *marry* drakes... but there will surely be some out in the world to contend with your sword :)
Check for any units on autoexplore or long paths that might be stuck or not using up their moves.
Campaign saves can be loaded from the campaign screen. The normal load screen only shows sandbox saves.
Looks like one we've already got fixed for tonight's update, so you should be set once 1.05 drops.
Please open your debug.err file in notepad, and link the contents into a post here via [link="http://pastebin.ca"]pastebin[/link]. This will give us some technical information that can help troubleshoot your problem. The file can be found in [b]My Documents\My Games\Elemental[/b] Be sure to copy the debug [b]immediately after the error occurs[/b]; if you start the game again, the debug log will be erased and recreated for the new session.
Should be fixed in tonight's update.
[quote]It's SHOULDN'T be because I was too close to a city, because I got this error after getting a too-close-to-city message and moving 1 square farther away.[/quote] The button enable and the actual city spawn were using different distance checks (one checked distance to nearest improvement, one to nearest city center). Tonight's build will fix this.
If the update doesn't complete after a while, hold on until we get 1.05 posted tonight. If you still have issues with that one, go ahead and email [email protected] about this.
[quote]Not to be dense but I'm having a lot of problems with the campaign. There seems no way to bring up quest or logs of what has happened.[/quote] You're looking for the campaign log:
If you're having activation issues, please contact [email protected].
Ctrl+arrow keys can rotate in a pinch.
Oh, that's just a drake IIRC, not a dragon. Check the campaign log, it should tell you what to do next:
Minor race's cities can't level up. We're planning to either remove that limit or communicate better why they can't.
Yep, this one should be fixed in tonight's update.
Another user today mentioned getting past it by running the game as an admin, if you're on a limited user account that's worth a shot.
This one should be fixed for tonight's build. Thanks for your report.