ptracker Documentation


Since ptracker 3.2.x there is an installer to easily install ptracker. Just execute the installer, and make sure the correct AC installation dir is selected in the installer window.

Apps must be enabled after installing in the AC launcher under Options->General->UI Modules. Just check the ptracker app and afterwards you'll find the "PT" icon in the game's side bar.


The installer is a little buggy when the given AC directory is wrong. You will have to click away some message boxes (just press OK). After you see the installer window, click on browse and navigate to the AC installation directory (the directory containing AssettoCorsa.exe). You might have to click more messages boxes away. After selecting the correct directory, press Install.
If you really do not like to use the installer, you can use 7z to extract the contents of the .exe installer. The contents will end up in some funny directories, but you will see which files to copy where.
Yes it does with versions >= 3.1.x. Unfortunately KS has removed the information about loading and storing setups from their logs (starting with the 1.3.x versions). So I was forced to seek for a different solution. This requires to load a .dll which depends on the Microsoft Redistributables 2015 package. You might have to install it (ptracker sends a message if this is necessary). I tried to avoid that step, but it seemed to be impossible with the new VS 2015 version. If anyone has suggestions on how to deploy these together with the app, feel free to contact me.
Have a clean lap in single player (e.g., hotlap mode) on the track. It doesn't matter which car. After that, ptracker is able to calculate "soft-splits", as a workaround for a bug in the current (0.22) AC API. Honestly, I didn't expect that this would still be true in AC 1.3.4...
It is in the standard location. AC needs an update trigger, so just click once on the track name in the setup I/O page, and you should see the setup named <sender>_<counter>
No. Your setups are private and you have full control over it. If you do not send a set to someone else, your set stays on your computer. If you send a set to someone, stracker will forward it and delete it immediately after it has been delivered.
The obvious exception is when you use stracker's setup deposit. In this case, the set is stored in the server's database.
This is too difficult in the current state of the AC API. There are already many many workarounds in the timing module for unexpected behaviour of the AC API functions and supporting A/B tracks would be too much effort.
  1. Check if it is a false alarm of your virus scanner software. Temporarily disable it and try if ptracker works. If it does, choose another scanner or report the false positive to the scanner authors. I use to check that the ptracker.exe file has no false positives. Though they have a lot of scanners, I think the list is not complete.
  2. If you are using Windows Defender, you might need to add an exception. Here are some screenshots of a russian windows version, but you will get the point
  3. Check that the file C:\Program Files (x86)\Steam\SteamApps\common\assettocorsa\apps\python\ptracker\dist\ptracker.exe exists, and try to execute it with a double click. A message window saying that ptracker-server-dist returned -1 is normal, all other behaviours are unnormal and might be caused by your AV software
  4. One guy solved his problems by copying the file MSVCR100.dll from C:\Windows\System32 to C:\Program Files (x86)\Steam\SteamApps\common\assettocorsa\apps\python\ptracker\dist
  5. Completely remove the directory C:\Program Files (x86)\Steam\SteamApps\common\assettocorsa\apps\python\ptracker and install ptracker again.
  6. Completely remove the directory <my documents>/plugins/ptracker. Note that this will delete your local lap database.

Change Log

From 3.2.x to 3.3.x

From 3.1.x to 3.2.x


Changes / New Features


Last experimental versions

Version 3.3.6

Version 3.3.5

Version 3.3.4

Version 3.3.2

From 3.0.x to 3.1.x

From 2.8.x to 3.0.x

From 2.7.x to 2.8.x

From 2.6.x to 2.7.x

To 2.6.x