yep, 5 ctd's so far today after the "fix"Before that I never crashed.
Mythic/GoA crits warhammer for 125523232 damage (0 mitigrated)
Warhammer dies...
The "FIX" lol... fucked up my client bigtime.. CTD all over the place.
Thought it was my pc, tryed new drivers. Got even worse.... Allmoust formatted.. GG
What a great way to kill a game. What kinda retard company would release something this shitty, without f#"#!!ing testing it first?!?!
This is to much..
Not resubbing -_- This game is dead to me
I'm playing on both GoA and Mythic servers. I think I have had about three CTD's in total on the mythic servers since I started playing. I'm lucky to get three hours play in on the GoA servers before I CTD, and this is playing from the same machine, and in theory at least running clients which should be patched more or less the same, so I am guessing it is down to the network.
You are dodging the issue just like Jacobs.
He said that things are tested before we get them, if that was the case Europe would not have gotten the shit patch we got yesterday. What I want is stuff not to be broken, that way I do not need a fix.
This is a duplicate thread so I posted a response in the other one.
This is not a network issue, but a code issue. Some changes applied to the US are not yet applied in Europe, simply because Mythic don't want to send us fixes unless they know they're working satisfactory. If the fixes helped you out with your US client, that's great news indeed. I don't know when we're updating our servers, but it would certainly be interesting to hear your feedback when we've done so!
-Magnus
Fair enough, but my point was that overall since the day the game went live I have hardly ever CTD'd on the mythic servers (only three or four times) and on GoA servers, pretty much every time I play.
Strangely I also experience a lot fewer lag spikes on mythic servers as a UK player. I work strange hours too, so often on mythic at primetime and GoA at primetime, and the difference if frankly astonishing sometimes. That being the case, it still suggests that there is an anonomly somewhere that has less to do with patches and more to do with a hardware or network issue - I am the first to admit I could be wrong, just seems like simple logic to me.