Confirm an engine is installed
Make sure the car actually contains an engine and that it appears seated in the current build. Do not move to fuel if the core component is still loose, absent, or unclear.
Work through seven A desrt no-start checks: engine, fuel, power, oil, cooling, driver position, and the official R input, then use the interactive diagnostic.
OFFICIAL GAME ARTThis sequence narrows the problem without pretending to know a hidden failure code. If all seven checks pass, the cause remains unresolved and you should inspect visible damage, connections, or current-server differences.
These are planning conditions, not hidden gates or guaranteed item requirements.
Choose the closest observable symptom before changing parts. The matrix narrows the first checks; it does not claim a hidden fault code.
| Symptom | Check first | Next action | Scope note |
|---|---|---|---|
| No response | Engine present, power connection, driver position, and the official R input. | Confirm one visible state at a time, then press R once from the usable driving position. | Silence does not identify a fuel, fluid, damage, or server fault by itself. |
| Cranks but will not start | Fuel state, installed engine state, and any visible oil or cooling warning in the current client. | Stop repeated attempts and change only the first condition that is visibly missing or rejected. | Use this row only if the current vehicle gives an observable cranking response. |
| Starts then stops | Fuel or power continuity, loose connections, visible damage, and fluid state. | Return to a safe baseline, record which state changes immediately before the stop, and retest once. | No universal stall timer or resource threshold is claimed. |
| Starts but cannot move | Gearbox or drivetrain state, wheel attachment, brake state, driver position, and visible damage. | Keep the working start baseline unchanged and isolate one movement condition before replacing parts. | A running engine does not establish that the transmission, wheels, or controls are usable. |
| Overheats after driving | Radiator, water or visible cooling state, engine setup, vehicle load, damage, and the route before the warning. | Stop, record the visible state, restore one cooling condition, and repeat only a short controlled route. | No fixed overheat timer, temperature, or universal cooling recipe is claimed. |
| Mobile or controller input | Current on-screen prompts, selected seat, controller focus, and whether R is only documented for keyboard. | Follow the current client prompt and report the platform; do not map a keyboard key to an invented button. | Official mobile and controller start mappings were not found in the checked public description. |
| Server or update state | Exact experience, server age, current event state, visible part labels, and whether another fresh server behaves differently. | Preserve the failed setup, note the build date, then compare one fresh server without changing the vehicle configuration. | A server difference is evidence of a state or version question, not proof of a specific bug. |
Make sure the car actually contains an engine and that it appears seated in the current build. Do not move to fuel if the core component is still loose, absent, or unclear.
The official premise requires fuel before departure. Confirm the vehicle has fuel and that you are not mistaking a nearby container for fuel already in the car.
Inspect the visible power component or connection used by the current setup. A part that is merely nearby is not necessarily installed or usable.
Inspect the engine's visible oil state before making more start attempts. Exact quantity and consumption are not asserted because the public material is incomplete.
Inspect the cooling setup. Treat this as a maintenance condition, not proof that every no-start problem is caused by the radiator.
Sit in the driver position and make sure the car is in a usable interaction state. Community-documented interaction keys can help move or seat parts, but they are separate from the official start instruction.
Press R from the driving position. If the engine still does not start after every earlier condition is confirmed, stop cycling inputs and inspect for visible damage, missing connections, server state, or a recent update.
Better move: Return to the first unconfirmed system and make one observable change at a time.
Better move: Check the current container, gauge, or interaction state where the game exposes it.
Better move: Inspect placement and interaction feedback before moving forward.
Better move: Use R for starting; keep pickup, drag, push, and sit controls in their own category.
Recheck engine, power, driver position, and R before adding more fuel or fluid guesses.
Open the focused pageTreat the cause as unresolved. Inspect visible damage and connections, then compare the current server with update notes.
Open the focused pageUse the controls page to separate the official R instruction from community-documented object interactions.
Open the focused pageThe official description says to press R to start the engine.
No universal rule is claimed. It is one useful cooling and maintenance check in the diagnostic order.
Follow the current in-game labels and behaviour. This guide does not publish an inconsistent compatibility table.
The cause is not isolated by this checklist. Inspect visible damage, missing connections, server state, and recent updates.