Connection problems after verifying?

lvl60togekiss
lvl60togekiss Posts: 22 Arc User
edited January 2012 in Support Desk
Hello all,
I decided to verify my client because I wanted to listen to the music in the game that had dissapeared.
Since doing this...I have had a few problems:
1. Occasionally the client will close randomly. (Happened when I ported to City of raging tides, and when i was walking around in Archosaur)

2. Since updating the game, I have been getting really bad lag spikes..., ranging from 700-9.5k ping/latency

Generally my ping/latency is around 500.

Whether the new files affect my client or not, I dont know...
But before the verifying I would still be doing the same routine with no problems.

Anyone have similar problem?
Post edited by lvl60togekiss on

Comments

  • SylenThunder - Twilight Temple
    edited January 2012
    1. Porting to RT and Tellus can crash the client on many video cards that are merely average now. Reduce your view distance setting by a notch or two and the problem will be resolved. (At least as far as crashing when teleporting to those locations is concerned.)

    2a. Always reboot after you update. The client has so many memory leaks it isn't even funy anymore, and a huge one is in the patcher. I recommend doing a hard reboot to ensure that the memory cards get cleaned out of any residual data.

    2b. Some of the scripts and process calls within the client are also detected by your security software as possible malicious scripts. The real-time scan will use extra processor time analyzing these functions as they are activated, and also as they pass through your firewall. The impact on your game performance will depend on what security software you have running, and on the workload of your CPU.
    Add the client's working directory to the exception list for your security software's real-time and scheduled scans. Then verify the files a couple of times to ensure that anything that got "cleaned" is restored.

    If you're still experiencing high latency, try rebooting your router, and if that doesn't work, post your traceroute from when you are having an issue.
    [SIGPIC][/SIGPIC]