Get back
on track.

1. Apply for Early Access if you do not already have an activation code.
2. Download the current Windows installer and run it on the PC you use for iRacing.
3. Launch PRT and enter your Early Access activation code.
4. Launch iRacing and enter a session, then enable the PRT overlays you want to use.

The installer is public, but Early Access requires a valid activation code. If you have not received one, apply here. If your code is rejected or you changed PCs, contact PRT Support with the exact error and your PRT version. Keep your activation code private.

The current PRT app is built for Windows on the PC running iRacing. You can use the website, Early Access application, Discord, and support from your phone, then install PRT on your racing PC.

That is the normal idle state when the simulator is not exposing live session data. Launch iRacing and enter a session. If PRT still waits while you are on track, send support your PRT version, car, track, session type, and a screenshot of the PRT status.

Open Overlays inside PRT, enable the displays you want, and configure the layout for your session. If data or placement looks wrong, include a screenshot showing both the PRT overlay and the corresponding iRacing information. For radar, standings, lap count, inputs, or track-map problems, tell us exactly which overlay is affected.

Use Add Pitmark Bot if you manage a server, or join the Pitmark Discord for releases, tester discussion, support, and feedback.

Early Access currently requires a Pitmark-issued activation code. The PRT app reads the entitlement tied to that activation. If you were accepted but access does not match what you were given, contact support with your PRT version and the error you see.

Include your PRT version, car and track, session type, what you expected, what happened, and the steps that reproduce it. A screenshot or short clip is extremely helpful. If the problem involves standings, lap count, radar, inputs, or the track map, include the matching iRacing display when possible.

PRT uses the live session and telemetry data iRacing exposes so race-night features can work. When a linked cloud/live integration is in use, a live session snapshot can include the car and track, lap and position, lap times and delta, speed, gear/RPM, fuel, incident count, flags, track temperature, and session state. That live snapshot is separate from PRT's smaller durable usage record. Current cloud analytics persist the device identity, optional linked Discord identity, car, track, highest lap reached, and session timestamps—not every raw telemetry sample. Early Access/licensing also stores the contact/application details you provide, invite status, and device binding. Early Access codes are stored hashed rather than as the plain code.

Yes. Testers may stream or record PRT in use. Please describe it as Early Access/in development because screens and behavior can change between builds. If something breaks on stream, a clip plus your PRT version, car, track, and session type is useful feedback. Never show your personal Early Access code on stream, in screenshots, or in public posts.

Have each interested tester use the PRT Early Access application so each person receives their own access path and personal code. For a coordinated league test, email PRT Support with the league name and expected tester count, or join the Pitmark Discord. Personal Early Access codes should not be shared between drivers.

The race-night foundation—Windows app, live overlays, telemetry, standings, proximity, track context, and the core testing loop—is in Early Access now. Persistent history, Driver DNA, smarter coaching, predictive recommendations, and Race Autopsy are still being built toward, and there is not a public release date we can responsibly promise yet. Those capabilities will be exposed for testing as they become ready. See the PRT roadmap and Discord for the current status and release notes.