FAQ
As a general rule, when something unexpected happens – e.g. the game does not recognize you or your teammates as “Online” – the entire team leaving and re-entering the server helps in most cases.
Disconnecting the server while not driving the car will not result in any issues. Drivers not currently driving may join and leave the server whenever they wish.
In order to reduce server load in long endurance events with high driver counts, it might be recommended for event organizers to regulate the number of drivers active on the server at any given time, e.g. asking inactive drivers to leave the server, leaving one teammate connected at a time to assist the currently driving player.
Workarounds, Troubleshooting and Known Limitations
Below please find the most common questions and workaround that might come up during team events:
Q: What’s the maximum number of drivers an entry may have?
A: In theory it is not limited, but for the sake of authenticity and keeping client numbers in check, it is generally recommended to stick with real-life rules when it comes to the size of individual teams (i.e. 2 to 4 drivers per car depending on the format).
For reference, in real-life, sprint races usually have 2 drivers per car, short endurance races (3H) can have 2 to 3 drivers, while longer endurance (6H+) events can have up to 4 drivers per entry.
Q: What’s the maximum number of cars an event might have?
A: It highly depends on the event format and the server hardware available for the organizer. It is at the discretion of the organizer to decide the grid size.
Generally speaking, running events for 10+ hours and/or having more than 150 clients can be considered as extreme load, and the stability or success of the event may be affected by the quality of the server hardware and server connection at hand.
Nevertheless, 24-hour races with 40+ entries with 3-4 drivers have been successfully held with sufficient hardware without issues with the server.
Q: I joined the server as a spectating driver and I’m focused on another team’s car.
A: This is normal, click “Drive” and find your car using the Shift+L/R arrow key. Once this is done, pressing Drive at any time in continuation will focus your camera on the correct car. Make sure you check that the Drive mode is focusing on the correct car before taking over the car.
If the player is still focused on a different entry after receiving the car during a swap, pressing Shift+Up Arrow will focus the view to the player car instantly. Note that this requires the possession of the car. While spectating, only the Shift+Left/Right Arrows will cycle the focus as described above.
Q: Do our team need to join the server in a specific order?
A: It is recommended that a team’s qualifying or starting driver joins the server first, to be followed by the other drivers in any order they prefer.
Organizers might require a join order to be respected or instruct the first driver of the entry in the entry list to join first. The first-joining driver will define the car and livery and number selection, unless forced by the server. In the event of a disconnection and loss of car, the original join order must be respected to retain the car’s progress (see next question).
Q: The active driver disconnected from the server, what can we do in order to keep racing?
A: Depending on the server configuration and the team’s ability to perform the correct rejoin sequence, disconnecting is likely to result in a DNF.
However, the team might be able to reconnect and regain control over the original car, being at least 1 lap down. When a car is lost, make sure all drivers of the team first leave the server. After that, it must be the driver of the entry who was originally the first one to join the server that reconnects first, followed by the other teammates. The success of the rejoin will be indicated by the fact that the Driver Swap widget is visible on the HUD with the teammates correctly indicated and the timing widget showing the car’s progress from before the disconnection.
If the driver who originally joined the server first from the team is unable to reconnect and regain the car (due to a prolonged technical issue or ISP/power failure), the original entry unfortunately remains lost and the remaining drivers will not be able to continue the race in the same entry. Unfortunately, losing the car this way qualifies as the ultimate technical issue and it results in a DNF.
Q: A teammate couldn’t make it for the race, will our results still count?
A: The key requirement of team racing is that each driver specified in the entry list must drive at least one stint. To avoid disqualification at the end of the race, the absence of a driver must be communicated to the organizer before the race server is started so that the entry list can be updated by the event admin.
The admin of the event can force a conversion of this DSQ to a stop-and-go penalty, in which case failing to start the race may only impose a hefty time penalty on the entry’s end result instead of disqualification.
Q: Can I compete in a team event as a single-driver entry?
A: Yes, nothing prevents entries with a single driver to participate in team events (at the discretion of the organizer). Should an event have mandatory driver swap pit stop requirement, it will be ignored for entries of a single driver, as long as the other requirements are met (if specified).
Single-driver entries may have a slight advantage during pitstops due to the lack of car transfer and faster reaction to restart the car, which organizers and admins might compensate for with a smaller time penalty if the event format features mandatory driver swaps.
Q: Our team joined the server but we don’t see each other online in the Driver Swap widget (usually also manifested in an incremented race number when joining).
A: This is a sign of desynced entry information that occurs due to an error in the event’s entry list or entry list corruption or an issue due to wrong connecting order.
Event admins might be able to amend the entry list if it is caused by an error (i.e. wrong encoding, formatting or SteamID) or try a server restart that eventually should amend the desynchronization (it might require a few attempts, this is up to the admin).
Q: I experienced a game crash or disconnection after giving the car away, is this affecting the team?
A: If the swap is completed successfully, any issue a spectating driver might experience is irrelevant to the connection status of the entry and the player should be able to reconnect to spectate.
Q: After a driver swap I don’t have Virtual Mirror on anymore even though it is enabled in the options, what can I do?
A: Cycling the driving views (with the F1 key) after taking over the car will bring back the correct mirror settings.
Q: Can my teammate(s) adjust my pitstop strategy?
A: This is not possible in the current version of Assetto Corsa Competizione.
Q: Can spectating drivers see the stint and maximum driving times on the spectator HUD?
A: This is not possible in the current version of Assetto Corsa Competizione.
Q: Can the driver taking over the car see the pit stop countdown before the car is handed over?
A: The receiving driver will see the driving HUD update with driver information (such as pitstop MFD, stint timer and inputs and tyre app) upon receiving the car. It is recommended to use a 3rd-party voice and update them about the countdown progress.
Q: The game has crashed after manually handing over the car with the chat command and pressing the Setup button on the garage screen afterwards.
A: Accessing the setup is not possible while spectating and if the manual driver swap is performed from the garage screen, the UI has no time to hide the Setup button.
As explained above, make sure you enter Drive mode before using the chat command to hand the car over. If the game crash already occurred, do not worry, it is not affecting the car’s state, just simply rejoin the server.
Content and screenshots courtesy of Kunos Simulazioni. Special thanks to Chris Hoeke.