EPTWorkaround For Patch 13 Lag - Page 3
| Blogs > R1CH |
|
CynanMachae
Canada1459 Posts
| ||
|
Etherone
United States1898 Posts
| ||
boesthius
United States11637 Posts
| ||
|
AcrossFiveJulys
United States3612 Posts
| ||
|
Shatter
United States1401 Posts
| ||
|
ZenDeX
Philippines2916 Posts
| ||
|
Kennigit
Canada19447 Posts
On May 26 2010 15:23 AcrossFiveJulys wrote: guys, don't get TOO excited about this, because in the last day or so I haven't experienced any freezes or drops and I'm not using this program (and I was freezing/dropping every game before). You must be the only one because everyone i know had it happen all day today until this came out. | ||
|
TelecoM
United States10686 Posts
| ||
|
deth
Australia1757 Posts
| ||
|
Zelniq
United States7166 Posts
r1ch again comes through with saving us from blizzard's mistakes | ||
|
ZenDeX
Philippines2916 Posts
On May 26 2010 15:44 dethrawr wrote: if r1ch replaced Greg Canessa we would probably have a better service overall. fixed. | ||
|
Luddite
United States2315 Posts
| ||
|
Lemure
189 Posts
| ||
|
semantics
10040 Posts
I assume just blocking udp for sc2 though windows 7's firewall will suffice. Along with removing the udp forwarded ports on my router. Also if i recall correctly Voice chat has always been UDP for sc2, does your thing break voice chat although tiny price to pay. actually looking at what your thing does i can just make a firewall rule to block all outgoing UDP and toggle it on after i sign in, as apparently you can't reach blizz servers without udp. | ||
|
affinity
United States266 Posts
| ||
|
CheAse
Canada919 Posts
| ||
|
Chrisboy
Australia118 Posts
| ||
|
shadowmarth
15 Posts
| ||
|
AcrossFiveJulys
United States3612 Posts
On May 26 2010 15:30 Kennigit wrote: You must be the only one because everyone i know had it happen all day today until this came out. That's interesting. The thing is, as R1ch explained, everyone in the game would have to be using this in order to eliminate the UDP clusterfuck entirely due to the fact that communication takes place between the server and the clients and not client-to-client. So it doesn't make sense to me that so many people are saying it is completely eliminating the problem. So that intuition, combined with the fact that I haven't personally experienced freezing lately, led to my suspicions of the effectiveness of R1che's tool. Now, it is possible that if one person cannot use UDP, then battle.net reverts back to TCP for everyone in the game for some reason. That would explain why the tool completely eliminates the problem. Just in case anyone doesn't understand why R1ch was (apparently) able to fix the problem and Blizzard hasn't yet, R1che's fix essentially forces a rollback to patch 1.12's TCP, which is not what blizzard wants. They want to fix whatever bug is causing such horrid UDP performance. | ||
|
semantics
10040 Posts
| ||
| ||
