Anyone ever notice...

...that sitting at a menu interface, doing nothing, DG fully saturates a processor core? Please, tell me you're not doing UI polling...

Also, please, for the love of God, thread every single bit of code that does any networking, no matter how trivial. The whole click on a menu and freeze for 20 seconds thing has got to stop. When I say freeze, I mean that the app stops responding for so long that it frequently elicits "not responding" from the process manager. This is a very bad sign. We may not be able to control the net, but we can control the percieved responsiveness of the app (and it will surely abate much teeth gnashing.)

Keep up the good work. I'm hooked.

Locked Post

Advanced Search

Watch this post

Do not email me updates for this post Email me updates for this post

Successfully updated karma reason!

Yes this is why I only play in windowed mode with TM open. It stops responding once in awhile for so long or the game crashes due to connection problems when joining certain games like skirmish it's necessary.

Successfully updated karma reason!

I have also been having this problem on a consistent basis.

Successfully updated karma reason!

kryo

Join Date 05/2003

+458

If you run the game with /nosound (add it to the end of the target path in the shortcut properties), is it better? Some users have reported performance issues with the sound system that the Moho engine uses.

Successfully updated karma reason!

Quoting PistolPeteX8,

reply 2

I have also been having this problem on a consistent basis.

If /nosound does work, please post to the pinned topic and also email stardock as per the pinned topic instructions, this is the only way we are likely to get a resolution

Successfully updated karma reason!

/nosound does indeed help. With /nosound I get simspeeds of around 8 for the first 20 or so minutes (without /nosound I get simspeeds around 3-4 for those 20 min) ... however, no matter what at some point during the game everything slows to an unplayable crawl and I get to 0 or -1 simspeed.

I have sent them the email with the game and dxdiag logs, but the response I got certainly doesn't fill me with hope that the issue will ever be fixed. *sigh*

Successfully updated karma reason!

Actually kyro, if you are still reading this (and I hope you are), I was wondering if you know why on Earth the game uses more processing power (and heats my system more) when I am trying to connect to other users than it does in the midst of graphically insane four-demigod duels? Because my temps spike to 80C when searching for games and never go above 72-3 in-game =/

Successfully updated karma reason!

wow, that's one hot CPU you've got there. i'd be more than a little concerned there unless you've got an old P4 tank-of-a CPU.

Successfully updated karma reason!

...that sitting at a menu interface, doing nothing, DG fully saturates a processor core? Please, tell me you're not doing UI polling...

Of course it does satureate a processor core. It renders stuff in the background. It's not because of UI polling

Also, please, for the love of God, thread every single bit of code that does any networking, no matter how trivial. The whole click on a menu and freeze for 20 seconds thing has got to stop. When I say freeze, I mean that the app stops responding for so long that it frequently elicits "not responding" from the process manager. This is a very bad sign. We may not be able to control the net, but we can control the percieved responsiveness of the app (and it will surely abate much teeth gnashing.)

I agree, this is very annoying.

Successfully updated karma reason!