Paint library and iRacing

iRacing paints are local files with specific names in specific folders. Livery Studio works with that convention instead of replacing it.

The app can keep project assets together, export the finished paint, and write the active paint file when you want to test it in iRacing.

Sim-stamped paints use the normal car paint filename. Custom-number paints use the car_num filename. The distinction matters because iRacing loads those files differently.

The app should make that choice explicit enough that you know which type of paint you are pushing.

If Windows blocks the iRacing paint folder, the push flow can fail even when the editor and export pipeline are working correctly.

When that happens, Livery Studio should show a repair path instead of failing silently. The goal is for the app to detect write-block errors, explain the issue, and retry after permissions are fixed.

A practical test is simple: push the paint, open or refresh iRacing, and confirm the expected file appears on the selected car.

If the app exports correctly but iRacing does not update, the next checks are filename, selected car, custom-number mode, active account folder, and Windows write permissions.