General Questions - Timer synchronization error Anonymous - Fri Jun 06, 2003 3:46 pm Post subject: Timer synchronization error
What is this?
Timer synchronization error (Trained)(391255030)(216.78.162.28 )(sec=87)?
Katie - Fri Jun 06, 2003 4:31 pm Post subject:
It looks like a problem.
Katie - Fri Jun 06, 2003 4:31 pm Post subject:
Of course, I can't help you. I've seen it once before, but I don't know how to fix it.
Dr Brain - Fri Jun 06, 2003 4:44 pm Post subject:
I get it a lot in my zone. Sometimes it kicks the player, some times it doesn't. I'm pretty sure there is nothing you can do about it.
RMJ - Fri Jun 06, 2003 9:37 pm Post subject:
It is caused by packetloss. Nothing much you can do about it.
Mine GO BOOM - Fri Jun 06, 2003 11:24 pm Post subject:
For subspace to work, everyone needs to be using the same clock. Since not everyone in the world uses the same clock update system, every client just attempts to sync up with the server's clock. If you look into the packets, you can understand a bit more about how it does the clock sync, but to skip all that, i'll explain what can go wrong.
If the client's computer just plain old sucks ass, the clock can get fucked up. I've had a few machines like that before, where it loses about 20 minutes every day.
If the client's machine is using a speed-up cheat. This forces the system's clock to go faster, or slower. Very useful for playing old DOS games that play way to fast, or for cheating in online games, since on your screen, your system goes faster, thus recharges/moves faster.
Some huge ass lag happens, where the clock sync gets through, but is so far off, it doesn't know what to do, so just boot/specs them. This the most common reason.
How to check to make sure its not the last one: /*tinfo. If the difference slowly increases/decreases, then their clock doesn't work right on their machine. They can either have my first or second example happening to them. How can you tell the difference? Well, you can't really, because a cheater won't say "oh damn, you've found me."