Manual › Chapter 12

Liveries and setups

Painting a livery in the browser, publishing it to the team and distributing setups the companion installs itself.

The problem it solves#

Distributing a setup to eight drivers usually means: upload it somewhere, announce it on Discord, hope everyone downloads it, and discover at eleven at night that two of them put it in the wrong folder.

Here the loop is different: the team uploads, the companion installs. Nobody has to know where a file goes.

Setups#

Distributing them to the whole team#

From Teams → Files, Share a file with the team: type Setup (.sto), the file, and the recipient — the whole team or a single driver.

The recipients' companions install it into iRacing's folders by themselves within a few minutes.

Distributing them to one crew only#

A setup that applies to a single race does not go to everyone: it lives on the crew's card, in Race → Setups. That crew's members' companions install it automatically.

Updating a setup#

Uploading a file with the same name publishes a new version: it overwrites the one already installed on the drivers' PCs. Nobody needs to be told.

The team folder, from the companion#

The other direction: what you put into the companion's team folder reaches all your teammates. The companion publishes it and the others install it themselves.

Who sees setups#

That is decided by the driver's badge (Teams → Management). Setups and liveries are deliberately separate permissions: a livery goes to anyone who takes to the track with us, a setup is the work of whoever built it.

Liveries#

Getting them to the right driver#

iRacing recognises a livery by its file name, which must contain the driver's customer ID. It is the most common mistake, and here it cannot be made: the system renames the file itself.

The file can be called whatever you like — car_12345.tga, livery.tga, def.tga. Open the driver's card in Teams → Members and use Send livery.

Spec maps#

.mip files upload like any other, naming the car: they land in its paint folder.

So opponents can see it too#

The companion does prepare the work for you, though: it puts the files, already correctly named and sorted by car, into

Documents › iRacing › paint › !EndurancePRO to upload › <Car>

From there you open them and upload to Trading Paints without hunting or renaming anything.

Seeing your own livery on track#

You need "Show my car" enabled in iRacing's graphics options. Without it the simulator shows the stock livery even with the file in place.

The livery workbench#

A livery editor inside the app: you draw in the browser and publish to the team.

What makes it different#

What gets saved is not an image: it is the layered document. And a text layer can be bound to the driver's number.

The consequence is the whole point: on publishing, the same drawing becomes one file per driver, already named for their customer ID and carrying their number. A livery drawn once dresses eight cars.

The cars' real guides#

Every official iRacing template contains a layer group called Turn Off Before Exporting TGA: the wireframe of the seams, the bodywork mask, the mandatory areas, the number boxes. There are four to seven per car, and they are exactly the guides you need while drawing.

In the workbench they become a tick box per guide.

For some cars there are also the stock liveries contained in the template: complete full-texture graphics, excellent as a starting point.

The preview cannot lie#

The drawing on screen and the exported file go through the same function. What you see is what comes out, at the real 2048-pixels-per-side resolution, generated only at file time.

The .tga format#

The file comes out at 24 bit with RLE compression, which is what iRacing expects.

Publishing#

On publishing, the files land in Teams → Files and the companions install them from there. For opponents to see them, the Trading Paints step still applies.

Summary#