| Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Tarminic
Forsaken Resistance
The Last Stand
   |
Posted - 2008.01.24 20:22:00 -
[1]
They're currently rewriting all of their netcode. I bet that once that happens desync will be fixed. As to how long it will be, I have no idea.
----------------
Tarminic - 31 Million SP in Forum Warfare
Play EVE: Downtime Madness v0.78.2 |
Tarminic
Forsaken Resistance
The Last Stand
|
Posted - 2008.01.24 21:09:00 -
[2]
 Originally by: Martin Mckenna
Originally by: Jenny Spitfire
What is a desynch?
Basicaly as far as I can gather a desynch is when the server stops receiving information breifly from the cliant. This means say you are aproaching a can. On the cliant screen you may be right next to the thing but the server still sees you 10km away from it.
In otherwords the cliant and the server and not running in sync....
That sounds about right. Basically information gets lost between the server and client without either finding out about the lost information. The server thinks that a player is in one location and the client thinks it's somewhere else. Whenever the client attempts to do something the server doesn't like, it's just ignored.
Originally by: wnoop
Rewritting the code in the hope that the bug will disappear instead of finding where the error is?
Fools are bound to make the same mistake again..
Bad coding practice Ccp.
Based on a couple of discussions and my own educated guesses, I think desync is a very subtle bug - they have been trying to locate it for the past six months, and the bug itself has been around (though not very common) for years.
----------------
Tarminic - 31 Million SP in Forum Warfare
Play EVE: Downtime Madness v0.78.2 |
Tarminic
Forsaken Resistance
The Last Stand
|
Posted - 2008.01.24 21:22:00 -
[3]
Originally by: Alora Venoda
Originally by: Tarminic
Whenever the client attempts to do something the server doesn't like, it's just ignored.
Instead of ignoring the nonsense, why not just "detect" the desync and take care of it, even if that means killing the connection?
I can't really say - I don't know if it's just the way the server handles exceptions from the client (my guess is a method that requires as little processing as possible), or if maybe these kind of messages are too common to do anything like killing the connection, or maybe they think that doing that would frustrate players just as much as the desync itself. Hell, without looking at the code myself I don't even know if what I'm saying is anything other than hot air.
I do seem to recall there being some kind of desync button or hotkey that you could use to "reset" the connection and fix the desync, but I have no idea if it's real or just my brain malfunctioning. You have to go to some advanced setting to enable it.
----------------
Tarminic - 31 Million SP in Forum Warfare
Play EVE: Downtime Madness v0.78.2 |
| |
|