I can get an OOM error.
Consistantly.
But, it is only under a very unique circumstance.
That being, I go to war and in a single turn do far too much.
And I have to be cheating in some way to accomplish it.
If I give myself God-like powers - very superior techs and speed and range so I can eliminate the enemies entire fleet in that single turn, as well as conquer at least around 25 planets in that same turn.
Then at some point in the invasions, the ground textures will turn to solid black and I know I went too far. From that point on, I will get an OOM error if I try to save the game or if the game tries to autosave.
That is virtually the only time GalCiv will crash on me.
I only play DL, granted. But DL has a history of being more memory intensive than any other version. DL does not have many of the memory tweaks that DA or TA has, and I always play gigantic galaxies with 8-9 opponents plus minors.
A lot of the errors, I think, are not the direct fault of GalCiv2* programming - but of the particular system (as in MB, BIOS, OS and other running software - as well as updates to any of these things).
I have very little running in the background at any given time. And I have excluded all the GalCiv2 folders from real-time virus scanning, which can make a huge difference in how the game plays and interacts with the system.
And my system is (rather) very average, and an HP to boot!
2.8 Pentium D.
3GB ram
Nvidia 6800GS
2GB swapfile
"Rather", because the video card is a factory overclocked version with a copper heatsink, and I have taken steps to ensure that system cooling is up to par. All case fans installed, a Zalman CPU cooler and a better (both in cooling and output) Thermaltake power supply.
This game stresses the system like no other game I have played.
Why?
Probably because of the superior AI coding.
It is not just video intensive - it is even more CPU intensive.
The memory problem is more with DL than with later versions, but it is still there.
But if you have a BIOS that needs updating, or a video driver, or a monitor driver, or a chipset driver, or a whatever driver (or software update - virus scanner, etc (anything that runs as a background process), that use memory locations that can conflict), those changes can make the difference between a playable game and an unplayable game.
In many ways, GalCiv2 is the most intense game on the market.
Yet, the devs are among the absolute best when it comes to trying to make the consumer happy, and to making the product as bulletproof as possible.
They work WITH us.
I have not seen this with the likes of EA or DreamCatcher.
Instead of immediately blaming the the game (and the devs), make sure you are doing your own part by keeping everything up to date and clean in your own computer.
Because like I initially said - I only have a single problem, which is both understandable and avoidable if I work things correctly.