![]() IMPORTANT: if the car is “lost” due to the active driver disconnecting from the server, all other drivers of the entry must also follow suit and disconnect. Were they not connected to the server, they would show as “ OFFLINE” with a black background. The Driver Swap widget is visible both in the garage screen (left) and the driving HUD (right): In the example below, PAN is driving and STU and VAS are also connected. ![]() The drivers connected to the server see the connection status of their fellow teammates in the Driver Swap widget. The setup of the car must be loaded by the driver who starts the race. The setup, car data and pitstop strategies are transferred as expected between the drivers on swap. Do NOT enter the server using a spectator password when you are a driver in the entry list. ![]() IMPORTANT: All drivers entering the server must do so using the normal server password (if there is one), no matter whether they are driving right away or just waiting in line for the driver swap, or just spectating other cars. Make sure you remember who was the first driver of your entry to join the server and thus establish the entry on the server, as in the event of a car loss due to disconnecting, the same driver will need to rejoin the server first regardless of who drove the car when it was lost. There is no specific order in which the drivers should join the server, but as pointed out above, in order to make it easier for your team to manage active drivers upon joining, it is recommended that whomever is tasked with qualifying or starting the race join the race server first and is defined as the first driver of an entry. Each driver of the entry must select the same car model when joining (livery choice does not matter apart from the first driver to join). The car of the entry is defined by either the entry list (when the car model is enforced) or the selection of the first driver of the entry to join the server. The other drivers of the team may enter and leave the server at any time, without causing problems for the entry or the server. a driver of the team must not disconnect when he/she is currently the active driver of the car. The key requirement of team racing is that the car must at all times be “owned” by one driver, i.e. NOTE to Organizers: make sure that according to the Server Handbook, the encoding of the entry list json file is correctly set to UCS-2-LE BOM.Īdditionally, it is highly recommended to avoid using special characters in the entry list (e.g. To make it easier for your team to manage active drivers upon joining, it is recommended that whomever is tasked with qualifying or starting the race join the race server first and is defined as the first driver of an entry. This will be the lineup that will comprise your entry. Following these guidelines should give you the highest chance of a hassle-free, successful race in a team event with driver swaps.ĭefine multiple drivers for each team/car in the server entry list. Please note that the process is also explained in the Server Handbook, and this guide does not go into detail on features that are not specific to driver swaps or team racing, such as entry lists and event rules that are already explained in-depth in other documents.Īt the end of the document you find a FAQ and links to complementary documents on the basic features of Assetto Corsa Competizione. ![]() The guide is up to date with ACC Steam version 1.5. This guide has been compiled to provide basic support for team-based Multiplayer racing in Assetto Corsa Competizione.
0 Comments
Leave a Reply. |