view posts by this user Offline
    Reply with quote Post a reply
Had around 200ish MS. Than Tran mentioned the latency fix. Now I have 40 MS.

Manual version (for those that just don't trust random .exe's):
http://gamers-underground.com/role-play ... -hack.html

Automatic version (for Tran fans):
http://www.wowinterface.com/downloads/i ... cyFix.html

:!:

"Was just waiting for fire to expire."
view posts by this user Offline
    Reply with quote Post a reply
Not to flame, did it really take this fix 2 years to hit this guild? :D
Image
view posts by this user Offline
    Reply with quote Post a reply

m0jjen wrote:
Not to flame, did it really take this fix 2 years to hit this guild? :D

Dunno, just makin' it sure people are aware. I lost that fix last time I reinstalled windows and didn't bother with it since, cause it never actually bothered me. Learnt along the way to live with it.

What does bother me is FPS dropping down to 7 or less in boss fights, especially with AOE. Have no clue as to why, will see if it's fixed after I install raid 5 field and windows 7 64bit. (running on vista 32 now)

"Was just waiting for fire to expire."
view posts by this user Offline
    Reply with quote Post a reply
no comments :D
network dudes surely share my opinion - bunch of crap to make something look pretty.

Image
Dotemall - the sexiest lock in town!
Who obviously stole the BiS cloak, KEKE
view posts by this user Offline
    Reply with quote Post a reply
I'm a network dude and I certainly don't share your opinion. Let me elaborate.

We have 2 nodes communicating. wow (which represents the server) and pc (which represents the client).

Before the fix (default TcpAckFrequency is 2):
wow: SYN #1
pc: ... (no response)
wow: timeout on SYN #1
wow: SYN #2
pc: ACK #1
pc: ACK #2

After the fix (TcpAckFrequency changed to 1):
wow: SYN #1
pc: ACK #1
wow: SYN #2
pc: ACK #2

On downloads and other shit, where you get tons of packets, this default value doesn't matter. In wow, or other online games, where the latency is measured as the packet return trip (from the time server sends SYN to the time it receives ACK from client) this matters. Because of the timeouts and packet resending.

In other words, I had over 200 MS wow latency before the fix. After the fix I have around 40 MS. The game is more responsive.

"Was just waiting for fire to expire."
view posts by this user Offline
    Reply with quote Post a reply
it dosnt work for everyone, but in 95% of the cases it will amke the game flow better
view posts by this user Offline
    Reply with quote Post a reply
down from 120 to 34. Worked for me :D
view posts by this user Offline
    Reply with quote Post a reply
Well, it did not work for me on two OS (different service packs)/hardwares, worked on third (as a value displayed in my "meter"), but I did _NOT_ see any difference. Also checked the packets flow and nothing really changed, only the value of ping displayed, which did not affect my gameplay at all.

Tho if you are claiming this really works, I will do the changes and check once again, since you really seem to know what you're talking about unlike most "network guys" I've met in WoW so far 8)

Image
Dotemall - the sexiest lock in town!
Who obviously stole the BiS cloak, KEKE
view posts by this user Offline
    Reply with quote Post a reply
Well, game became more responsive to me. It's slightly less lag for that initial cast i do when starting my heal spam routine. Also, before I was wondering why sometimes I don't see some healthbars dropping when they are clearly getting damage... I think (my interpretation, not a fact) that it's because people with less lag manage to spam heal them - so i get insta packets with drops and heals which results in health bar staying the same. Didn't notice that happening since the fix.

But all these are minor fixes. Most change I see is while playing CoD MW2... I can pwn more now. :)

"Was just waiting for fire to expire."
Jump to :