why is this so different? i can play 5v5 versus ai in tournament and keep ~5 simspeed through out a match, but online and it drops to 0/-1. didn't see this explained in the few random posts i read
started for me today...pretty annoying. oh, and when it happens it happens to everyone in the game at the same time.
just thought i'd add that i usually play 4v4s fine, but for some reason my last game ended up freezing on me. the game just stopped responding after becoming increasingly jerky (never happened before in my previous 10+ 4v4s). had to reboot my comp because even ending the process didn't actually kill it for some reason....
how are you going to distinguish rage quitting from people with things that come up in real life for whatever reason... the whole point of punishing people who quit a game because they no longer get satisfaction from it is kind of stupid in my mind... but anyway, since it only affects the current game and not accumulated efforts it's not that big of a deal....and probably won't impact much of anything in the long run anyway.
GJ ON YOUR BAD UPDATE. whereas before i could connect to 3v3 and 4v4 no problem, now i cannot even get to the connection screen...it just hangs for 30 seconds and times out. SERIOUSLY GG / lawl
so, why don't you guys release a standalone patch for the the rest of the people who can't do it manually? it just makes sense to help out the people who bought the game play immediately with such an easy work around imo.
ah, it's when you try to update the game though impulse and it gives you an error about non-negative number nonsense and you cannot update demigod. doing the above got my friend past it after he tried other stuff people suggested.
so, i fixed this for my friend. what i did was copy the download queue right before it extracted and deleted the temp files and rar'd it for him. [ link removed ] just extract that to C:\Documents and Settings\All Users\Application Data\Stardock\Impulse\Temporary (which is set as default in impulse, so change if necessary) and try running the update again from scratch. worked for us. steps we took outlined before for reference (some may be unnecessary) 1. updat