Open issues & workarounds
Launcher stalls at Starting Theme Engine: keep the failure stage
Kunos’ developer reply to the Starting Theme Engine failure asks for log files in an official-forum support thread. That discussion dates to the early PC release; use its evidence-collection approach without assuming the same launch defect is current. Record whether the launcher appears, the menu becomes interactive or the failure starts when entering a driving session. [1]
Documented steps
- Preserve the log files from the failing session and write down the last visible launcher message. Submit them with a reproducible support thread, including whether Steam or a separate launcher started the session. [1]
Launcher or session failure: keep one reproducible test configuration
The developer requests feedback tied to the same failure rather than an unqualified universal fix. For a useful comparison, keep the chosen car, track, input device and launch method in the report. If extra content is involved, record that content and compare an ordinary installed car/track session without overwriting the original setup. [1]
Documented steps
- Record the original car/track and controller configuration, run the Steam installation check below, then retry the same session. Keep the log from the retry and note whether the launcher or the driving session closes. [1]
Steam crash or missing files: verify the installed game
Steam can check downloaded game content when a launch crashes, textures disappear or other installation files appear missing. This scan repairs the installation; retain a separate copy of any affected save before investigating save compatibility. Some local configuration files normally remain unverified, so that result alone does not identify the cause. [2]
Documented steps
- Restart the computer and Steam. In Library, right-click the game → Properties → Installed Files → Verify integrity of game files. Wait for completion before repeating the same failing launch or load. [2]
- Run one verification at a time and avoid heavy disk tasks during the scan. If the same failure remains, keep the exact error and the game-specific diagnostic files described here for the developer. [2]
Resolved fixes & patch history
Gamepad deadzone behavior is incorrect
The update lists a gamepad deadzone fix. The changelog supplies no universal deadzone value to apply to every controller. [3]
The old pit-stop UI allows excess fuel with a fixed setup
Version 1.14 corrects the old pit-stop UI allowing extra fuel despite a fixed setup. [3]
Session switching breaks the unfinished pit-stop UI
Version 1.14 fixes broken UI interaction when the session changes before a pit stop has finished. [3]
Oculus mode renders incorrectly with no headset attached
Version 1.13 fixes broken rendering when Oculus mode is selected without an Oculus device connected. [4]
Gameplay notes
Controller or pit-stop behavior recurs: identify the affected interface
The retained release records distinguish gamepad deadzone behavior from the pit-stop UI and session-transition corrections. Include the controller/wheel, deadzone setting, session type and whether the problem appears before or after changing sessions. An Oculus rendering correction likewise needs the headset/mode state in a recurrence report. [3]
Sources & verification
Platform and version details belong to the individual issue or guide section. A documented workaround may not resolve every case.
- starting theme engine -never starts :: Assetto Corsa General Discussions official-supportRetrieved
- Verify Integrity of Game Files official-supportRetrieved
- Assetto Corsa v1.14 update and "Ready To Race" DLC available! official-newsRetrieved
- Assetto Corsa v1.13 update available! official-newsRetrieved
