Trying to guage expected game stability (.0295)

Hey there.

Very excited for this game as I am a fan of stardocks previous 4x work.

I just got into the beta the other day and I notice a can't play more than a few turns without my computer completely locking up, black screen, motherboard beep and eventual reboot.

I play alot of games on this machine and nothing else has that problem, so I know it's not a major computer fault. I realize this is a beta, but it seems alot of you are able to play complete games with only a crash or two?

Basically, I'm just wondering whether at this stage I should be bug reporting like crazy, because I have found something others are not experiencing, or is this pretty standard fare at this stage?

8,914 views 13 replies
Reply #1 Top

While it's true that is standard fare, I'd still report it. It could mean the game has a problem specifically with your Type of configuration, in which point they would want to know so they can make it run on as many machines as possible. Hope that helps.

Reply #2 Top

Yeah ok, Ill get too it then. I do have a fairly wierd config actually. (Althlon dual core fx-60, with an AGP 3850 512 video card)

cheers.

 

 

Reply #3 Top

I joined the Beta 1G too and have found that it does crash (actually just came back to the computer after getting a drink and its back on the Windows screen, "Where has the game gone?") but not as bad as what you report.

 

As others have said, autosave is your friend :)

Reply #4 Top

I have a fairly new I7 build and it locks up and crashes on me all the time. 6 gig of RAM and a big pagefile on Windows 7 64bit and it still goes tits up almost every ten minutes. No real bad lock ups like you are saying occur but this is what we are doing. Testing :)

Reply #5 Top

@ Darias and Ravenstrike: The Devs (and us testers) are aware that currently there are some pretty bad memory leaks in the game. This is the most common cause of current "unexplained" crashes I'd imagine. Of course there are other crash bugs, gameplay bugs, bugs related to systems not fully implemented, etc etc, but it shouldn't be locking up systems or causing systems to overheat and shut down. Things like the later definitely deserve a bug report to be filed.


On a side note, a few years ago on a older rig I had there was this problem. I was running a GeForce 7 series video card and I'm a cig smoker. I have a few air purifiers now to solve the problem but back then cig smoke build up would become a problem. Eventually the fans in the video card and my power supply gunked up. They would over-heat and shut down my system but Only when I played games that really stressed my system as these would be the games that would push the system to turn on those fans when temps hit a certain level.

If your comps are working with other games, but not Elemental, check a few other "New" games and see what affect they have on your systems. Games that you've ran for a while now may work fine, while newer games that push your system harder may cause it to over-heat. Just a thought and something to look out for. Also take note you don't need to be a smoker for this to be the case as normal dust accumulation can cause the same thing to happen it just takes a lot longer then it does for a computer in a smoking environment.

I also ended up buying some hepa-filter bags for computers that run in industrial zones. They do increase the internal temp by 1 degree celsius but they keep out All smoke while still allowing your computer to breath.

Reply #6 Top

Basically, I'm just wondering whether at this stage I should be bug reporting like crazy, because I have found something others are not experiencing, or is this pretty standard fare at this stage?
End of quote

Well, you should report at least one crash, with debug.err, dxdiag and memory dump. That will inform the devs about your configuration and problems they may encounter.

If they have nothing to help them fix a problem, they can't fix that problem.

 

Reply #7 Top

Yes report it, but read the beta forum rules on how to report it first so you can give them some useful information. At this point you can expect the game to still be unstable, maybe very unstable on some systems. But part of the reason for the fairly open beta is that the game is played on a wide range of systems.

Reply #8 Top

If your computer is locking up, you probably want to report it. But it sounds like a computer problem, most of us are just having game crash issues and not computer crash issues.

Are you using recent Nvidia drivers? The set released most recently has a severe problem with shutting off the fans and cooking video cards. (Good old Nvidia, they can't do anything right lately.)

Reply #9 Top

(double post)

Reply #10 Top

I think the game is more stable when I entirely disable my secondary monitor, but I can't be certain.

I haven't noticed any instances of the game failing to open/immediately crashing when you try to open it/whatever was going on for a couple of days there.

 

PS- did that baby backdrop somehow get added after a couple of days?  It didn't display on my computer for the first ~two days.

Reply #11 Top

Quoting DariasDruss, reply 4
I have a fairly new I7 build and it locks up and crashes on me all the time. 6 gig of RAM and a big pagefile on Windows 7 64bit and it still goes tits up almost every ten minutes. No real bad lock ups like you are saying occur but this is what we are doing. Testing
End of DariasDruss's quote

Ditto.

Reply #12 Top

I'm pretty sure the game has a few major memory leaks at the moment, I can generally play about 25 turns before it locks up and crashes so I normally play for 20 turns, save, exit and reload.

Reply #13 Top

Quoting econundrum1, reply 12
I'm pretty sure the game has a few major memory leaks at the moment, I can generally play about 25 turns before it locks up and crashes so I normally play for 20 turns, save, exit and reload.
End of econundrum1's quote

The devs have typed about the leaks and in his March FAQ, Brad noted that clearing these problems up is one of the criteria to meet before moving to Beta 2. I think I saw Scott mention something about 100 turns being when the memory leaks start becoming problems, but that seems like something that could vary significantly across different rigs.

p.s. Has anyone found out how to display the turn count in the 0.295 UI?