Screen freezing on servers with latest code..

[slynnes]

I typically 4 box and use to have all kinds of problems on different servers with the old "graphics lock up" but im still there problem. After the updates in...Sept..Oct?..these problems totally went away...until recently. Now when I try to 4 box...i CONSTANTLY get 1/4 locking up when they are just sitting there medding... It's worse then it use to be. I use to be able to log accounts on and off and eventually it would go away, but now it doesnt. It keeps happening. I haven't updated anything in last 2 months on my computer, unless its some lame windows update that screwed me. This basically makes the game unplayable for me. I play on 2 computers to..one at work...one at home..and they are both doing this. Why is this back?????

[trevius]

Which server are you playing on, and exactly when did that start happening again? I know there were some recent stream changes that were meant to prevent possible crashes. I know one of them already had to be reverted due to causing clients to be unable to cast or attack. I wouldn't be surprised if one of the other changes could be causing this new issue.

[slynnes]

Citadel of seekers, ez, random, irreverent in last few weeks

[trevius]

And you are sure all of those servers run current source code? As far as I know, EZ hasn't updated there code in months. So, if that is the case, then I would have to say the problem is definitely on your end.

[slynnes]

Yes it could be on my end. The only thing that I share between the two computers is the character config files so I have the same screen setups and hotkeys. Could the config files somehow contain something that is causing this? Reason I am wondering about this is...on Citadel of Seekers, when making a new character I have had issues with using other server config files. CoS allows some # commands...and what I found was when I copied..lets say my Stormhaven config files and renamed them XXX_CoS.ini, I then go in game and everything looks great, but for some reason I was getting an error like "that spell is unavailable" when I was trying to #zone. I then deleted both INI's for that character and came in "fresh", and the # commands work. How can the ini files afffect the use of # commands?