Aleph One 1.0 beta 3 has a timing adjustment log feature in the code. This is because the last time timing adjustments were last calibrated, there was a lag-inducing jitter compensation bug active in the code. Now that the bug is fixed, I'm seeking new input on recalibration for beta 4.

You can turn on the logging by creating a folder called TimingDebug in your local data folder--the folder where your Screenshots and Saved Games folders are. If the TimingDebug folder exists, Aleph One will save a log file for each game you host into that folder. The name of the file will include the time the game started (or ended? can't remember) and number of players in the game. To turn logging back off, remove the TimingDebug folder. Logging must be enabled at the start of the game, it cannot be turned on in the middle of the game.

Please enable this logging if you are prepared to send in relevant reports. If you encounter unusual network behavior in a game you are hosting, please post the appropriate report here along with a description of what happened and approximately when in the game it happened.

Some examples of unusual behavior:

• A player who isn't normally jittery is unable to move due to latency tolerance rejecting his inputs
• A normally lag-free and jitter-free player is experiencing unusual lag
• A wired ethernet LAN game is laggy
• A super laggy or jittery player joins and latency_tolerance has trouble keeping the game smooth

Log files contain the names of the players in the game, but not IPs or scores. If you prefer to send logs to me privately, you can use the PM feature.

Here's a reminder of where to create the TimingDebug folder:

Windows XP:
C:\Documents and Settings\<your username>\My Documents\AlephOne\TimingDebug

Windows Vista / Windows 7:
C:\Users\<your username>\Documents\AlephOne\TimingDebug

Mac OS X:
/Users/<your username>/Library/Application Support/AlephOne/TimingDebug

Linux:
<your home directory>/.alephone/TimingDebug

So I gathered a game yesterday that I believe falls into this category:



That player was Swartz. His ping and jitter were not looking too good, and the game was lagging enough so that I had trouble hitting both players. It was more an issue of the players appearing choppy, rather than my movements being choppy. Games before and after this one ran fine for me.

[attachment=4853:20110702200116_3P.txt]

Edit: IIRC, the lag was present for the entire game.

Did vio say anything about the gameplay in that game? It had to have been unplayably laggy for him. How long was this game? There are is no log after the first 30 seconds.

Swartz definitely complained, but I don't recall exactly what Vio said (sorry). I set the time limit to 5 minutes, but things were ridiculously bad, so I aborted the game early to re-gather. I could have sworn we played at least a few minutes, but time passes more slowly when you're not having fun, so maybe it really was only 30 seconds.

I'm seeing the same lockups I had before, but the app crashes now when we quit. see my post in the b3 thread:

http://www.pfhorums.com/index.php?showtopi...amp;#entry93640

also, FWIW, we're playing on his home wifi (wpa2, nat, etc)

I hosted a game today that suddenly crashed. No error message or anything like that, I was just all of a sudden looking at my desktop instead of the game. This happened towards the end of the game. Would the log file help at all in this case?

Edit: Detached attachment.

No, the timing debug will not help debug crashes. Aleph One Log.txt may if you get an assertion failure. Otherwise you may have to install exchndl.dll to get a crash report.