Demigod Forums
I mean 3 times tonight get a game going three times get an unhandled exception.
Now it takes 30 secs to log on , to join games, or make games.
You all did a great job getten the connections to work beter so i see light there
so thats what happened. figured you must have crashed out of that lobby. bad timing too.
try rebooting the comp. kinda low tech and not a permanent solution, but sometimes it helps get rid of some gremlins.
I think part of the reason things end up going bad to worse to good to bad to worse and then maybe good again is because they keep getting pressured by the community to rush these things without properly testing them. Of course, it's partly SD/GPG's fault for rushing the game out, but quite frankly, I think things would be best if they did some more extensive testing with their updates, if only to stop the excessive BAAAAAAAAAWWWing from people who don't understand that these things take time, and this is what we get when we take away their time.
Now, I'm not saying SD/GPG are the greatest publisher/developer in the world, and I'm not saying that we should let them not worry at all about thier title and its networking, but I think that we as a community should have the decency to get off their back and let them do their job the way they're supposed to.
yes i see your point but after 7 weeks you would think gas powered would have had a patch all ready to go by now.
If I remember correctly, Frogboy said that GPG's patch is going into QA next week which means that we might see it late next week or early on the following.
GPG has delivered v1.01 of Demigod to us. It's in internal testing now.
Question: is this mostly lua-based code or underlying engine?
Reason I'm asking, it most of my crashes involve an "unhandled exception" with the stack trace along the lines of "attempting to index nil value" which is a lua issue.
seeing as how you are probably 67 now I doubt it
don't you read the journals? 1.01 patch is schelduled to be out next week i think
Except they didn't. They didn't do a full scale stress test, but that's a hindsight issue -- in hindsight, yeah, they should have. But they didn't really have the experiance to realize one was necessary (to reveal the problem that the code didn't scale very well with the number of users). There were a few minor and annoying bugs in beta, but a lot of us thought it really was ready (other than a few balance tweaks) for release.
Welcome Guest! Please take the time to register with us.
Stardock Forums