Two or three players minidumping simultaneously. "Record game" causes runtime error. Lobby crashes every two minutes. I don't know about the rest of you but I find this to be worse than the "Black Death" MD period of patch 1.5, where 99% of all game ended in a minidump. Please fix, otherwise MP player count will be even lower than it is today.
Yeah, I've had similar problems here recently. Literally, the past 3 games I've played have ended with either a minidump or somehow losing connection to Ironclad Online (sending me back to the main menu). It is pretty bad...
How to fix most MP crash issues: Put Large Address Aware into the game, to greatly improve mid/late game stability and alleviate RAM related issues.
I'm pretty sure most MDs have nothing to do with RAM issues, given that they can occur at any time.
If you hit the 2 GB limit, you will get a minidump, not a runtime error...
Considering players can still crash at game start, in game lobby, or within a few minutes of the game starting, I think it is pretty clear RAM limitations aren't the issue...
Please write in to support@stardock.com if you're having trouble and would like assistance.
Given the issues I've seen, this game probably has plain old memory allocation errors, like writing to unallocated pointers, double frees, etc. Running out of virtual address space (2GB) doesn't seem to be the main issue. It minidumps or exhibits playback desync heisenbugs often enough with just around 1.2-1.4GB allocated for it, well below where it would run out of address space. Growing the address space does statistically make such bugs less likely to be fatal, but that's not how you fix them for realz.
And /LAA is not magic pixie dust, nor can it be deployed in a totally happy-go-lucky fashion; see http://stackoverflow.com/questions/2288728/drawbacks-of-using-largeaddressaware-for-32-bit-windows-executables
There are many great features available to you once you register, including:
Sign in or Create Account
