#32
|
|||
|
|||
Re: *** 100% SOLVED!!! ***
[ QUOTE ]
What do u guys mean when u say "laggy"? Because Party has been TERRIBLE for me since about mid-March, but i wouldn't call it "laggy" >> more like "crashy". It freezes ALL the time and i have to ctrl-alt-del kill the party process and re-open it and hope that my hand hasn't been folded. I made another post about this awhile back, but basically, it just stops responding and i get the "internet delay...attempting to reconnect" dialog, but it NEVER reconnects...so as soon as I see it doing that, i just kill the process and restart it. For me, it doesn't necessarily get worse when i have more tables open (e.g. sometimes it crashes with a SINGLE table open...) but i do think it has something to do with the lobby window, b/c it crashes a ton when the lobby window pops up (usually b/c i close a table, so the lobby automatically pops up)...or alternatively, i might pull up the lobby to find another table, and boom -- freezes. [/ QUOTE ] The kind of "lag" I was experiencing was not related to network problems; it was somehow related to sudden spikes of high CPU usage. I never had any "Internet delay" problems and the random crash bug I had in February got fixed a while back (I think it was related to IE7 and the lobby's scrolling spam window). When I first started a session everything would be fine, but after 20-30 mins I would start to slowly see the client chug more and more, and things like the flashing arrow that shows who is acting would start to "stall". It would then get progressively worse to the stage where when I pressed a button or opened a new table then client would momentarily freeze for about 1/2 a second. If I just kept on playing then eventually the freezes would get worse and worse and ultimately the client would just crash and try to restart itself. Since I've turned off "font smoothing" and started using 16bit colour while I play everything seems to be working fine again now - possibly even better than it's ever worked before. I'm not sure what is the root cause though and I never had any problems like this at the start of the year on the exact same hardware, so it must be something they did within the last 2/3 updates. Juk [img]/images/graemlins/smile.gif[/img] |
|
|