Skip to content
Manual

Manual › Chapter 16

Troubleshooting

The most frequent symptoms, the cause they usually have and what to try, in order.

How to use this chapter#

Problems are grouped by symptom, that is by what you see, not by the cause. Under each symptom the checks are in order: the first one solves it in most cases.

If your case is not here, the assistant inside the app also answers questions written in your own words: Profile → Support.

Sign-in and account#

I cannot sign in#

  1. Check the address: Wrong email or password means exactly that.
  2. If you registered with Discord, you do not have a password: use Continue with Discord.
  3. If the security check fails, disable an ad blocker or VPN on this page, or try another browser.

The companion will not accept my credentials#

The companion asks for no credentials: it has a single button, Sign in, which opens a window on the site page. If that window does not open or stays blank, close it and try again; if it persists, download the installer again and install it over the top.

My sign-in is not remembered#

You are using another app's built-in browser (Discord, Telegram, Instagram). Sessions are not kept there. Tap the ⋯ menu and choose Open in Safari or Open in Chrome, then install the app to your Home screen.

I did not get the confirmation email#

Check spam. If it is not there, try registering again: the address may have been mistyped.

Notifications and alarm#

No notifications arrive#

  1. Permission must be granted on that device: Home → 🔔 Notifications and alarm → Enable.
  2. On iPhone: the app must be installed to the Home screen from Safari. From Chrome, or from a browser tab, notifications never arrive. That is Apple's rule.
  3. The phone's battery saver can suspend notifications for a rarely used app.

Notifications arrive but the alarm does not ring#

Night mode is not automatic: switch it on from Race → Live before going to sleep.

The alarm is too quiet#

The screen stays on by itself; the volume does not go up by itself. Phone on charge, media volume up. Try it first with 🚨 Test the alarm.

I do not get the phone call#

  1. The number must be in international format: +39....
  2. The Call me if I do not confirm switch must be on.
  3. With Do Not Disturb on you need repeated calls enabled in the phone's settings.
  4. The call only fires if you have not confirmed: if you already had, everything is fine.

Reminders arrive at the wrong time#

  1. Check the check-in before swap parameter in the plan: every alert is counted from there.
  2. Check that somebody pressed start when the race actually started. Without it, the plan stays anchored to the scheduled time and everything drifts.
  3. Check that the schedule before the green flag is filled in on the event page.

Telegram sends nothing#

Re-link it from Profile → Settings and use 🔔 Send a test message.

Companion#

It says "Waiting for iRacing" but the simulator is open#

  1. Check the iRacing folder in the companion's Settings: if Documents\iRacing is not in the standard place, it has to be pointed at by hand.
  2. Try restarting the companion with the simulator already open.

It stays on the loading screen and never opens#

Download the installer again from Profile → Settings → Companion and install it over the top. A stuck application cannot start its own update. Settings and sign-in are preserved.

"Last upload" is not moving#

The companion has the data but cannot send it: it is the connection. A red line also appears saying Upload failed.

It records no laps#

  1. Record sessions to disk must be on in the Telemetry on disk card.
  2. A lap only closes at the finish line: half laps, pit exits and rejoins are discarded.
  3. It takes a couple of complete laps before anything appears.

The map says "track reconstructed"#

That lap was recorded without real coordinates — an old companion, or disk recording switched off. Turn it on: from the following laps the racing line is the real one.

Race paces#

It is gone: race paces come from the laps the companion records. Same laps, without depending on an external service. Entries imported back then stay where they are, marked G61, and get replaced as you drive those combinations again.

My hand-typed paces have disappeared#

That cannot happen: hand-typed entries are never overwritten by imports. If you cannot find them, check you are on the right car+track combination.

"No usable recorded laps"#

At least 3 valid laps on a combination are needed before a pace can be derived.

Events, crews and the plan#

I cannot sign up for an event#

Do you read "Sign-up blocked: incomplete personal profile"? The team requires certain profile fields. The list of what is missing is in the message.

I cannot edit the stint plan#

Only the crew chief (⭐) and the team's admins can.

The plan says "estimated pace"#

That driver has no measured pace on that combination. It is not an error, but a plan built on real paces is a different plan: see Performance → Paces.

I recomputed and lost my manual edits#

⚡ Recompute stints rebuilds the plan from scratch. The app warns you first. To try an alternative without losing the current one, use strategies: Save this one, then work on the copy.

I moved a driver and it asked me to confirm#

That stint falls outside the availability they declared. Confirm only if you really have agreed it with them.

The stint times do not match the real race#

Somebody has to press start when the green flag actually falls. From there the times anchor to now and everything lines up.

Pit wall and monitor#

The pit wall is empty#

You need the companion running on the PC of the driver on track, and the plan in live state.

I am a spectator and see nothing#

As a spectator, without sharing the session, standings, radar and weather stay empty. The button is in the companion's Team card.

The tyre wear estimate says "not calibrated"#

It needs at least one stop with a tyre report. Before that it is only a trend, and it says so.

Refuelling calculates nothing#

It needs a few laps with fuel recorded and the remaining race time.

The driver swap was not detected#

The automation works with the plan live and the companion hooked to the racing crew. Otherwise there is Pit now, which closes the stint by hand.

Setups and liveries#

The setup does not appear in iRacing's folder#

  1. The companion must be running: it installs within a few minutes, not instantly.
  2. Check that Install team setups and liveries automatically is on in Settings.
  3. Check your badge: the setups permission may not be there.

I cannot see my livery on track#

You need "Show my car" enabled in iRacing's graphics options.

Opponents cannot see my livery#

An installed livery is only visible to whoever has it on disk. It has to be uploaded to Trading Paints: the companion prepares the correctly named files in Documents › iRacing › paint › !EndurancePRO to upload.

The car appears black on track#

The .tga is 32 bit. It needs to be 24 bit with RLE.

You need iRacing open, even just as a spectator: with no simulator there is nothing to command.

I cannot zoom or pan the camera#

iRacing does not accept zoom, pan or rotate commands from outside: its protocol has no room for them. You turn on the camera tool inside the simulator and adjust there with the mouse and arrow keys.

OBS will not connect#

  1. In OBS: Tools → WebSocket Server Settings, the server must be on.
  2. Port and password have to match.
  3. The status line under the fields says what the gallery can see.

The graphics do not appear in an OBS browser source on another PC#

  1. Use the network address, not the localhost one: there localhost would be the wrong computer.
  2. It is almost always the Windows firewall on the race PC. The gallery checks this and offers a button to open the settings.

The tablet will not connect#

  1. It must be on the same home network.
  2. The address carries a key: without it the connection is closed. If you regenerated the key, every old address is void.
  3. On first start Windows may ask to unblock the network: you have to say yes.

A driver's livery is out of date on the broadcast#

Use Reload liveries in the Direct capture section: the simulator keeps showing the one it read at the start.

If none of this helps#

Open a report from Profile → Support, saying what you were doing, what happened and what you expected. If you know how to make it happen again, write the steps. A screenshot is worth a thousand words — up to three can be attached.