Confirm the engine identity
Photograph the current label before mapping a community alias. Keep BAZ and Engine-D, or Engine-E and Racing, separate until the current client supports the relationship.
Review 13 community-named A desrt engine leads, keep aliases and update status explicit, and compare fit, resources, acceleration, speed, and range safely.
CURRENT-BUILD FIELD FILEThe current community comparison names 13 engine leads, but the list is not an official roster and several aliases or post-update measurements remain unresolved. Use the names as an index: V8, BAZ/Engine-D, Engine-L, Engine-E/Racing, Engine-U, Jet, Injection, SMZ, Engine-H, Electric, Van, VAZ, and Engine-M. Confirm the current in-game label before merging aliases or choosing by performance.
Not independently tested: this site has not reproduced the exact interface, component labels, spawn, compatibility, or performance in a live current client.
Creator video title lead: a public title can establish a topic worth checking, but it is not an official changelog and is not treated as proof of every detail shown in footage.
| Field | Current answer | Evidence |
|---|---|---|
| Community roster | 13 named engine leads | Secondary community comparison |
| Video index | A creator video title claims to cover all engines | Creator video title lead |
| Official roster | Not found on the checked official game or event page | Official pages checked |
| Comparable measurements | Incomplete and not collected on one shared post-update basis | Community-reported; not site-tested |
These steps verify observable behaviour without inventing a menu path or hidden value.
Photograph the current label before mapping a community alias. Keep BAZ and Engine-D, or Engine-E and Racing, separate until the current client supports the relationship.
Confirm that the engine attaches and produces a usable vehicle state. A strong community result is irrelevant to a vehicle that cannot use the same setup.
Note the starting and ending fuel or battery state, plus any oil, cooling, or other visible requirement. Do not compare a partial run with a full-route result.
Keep vehicle, load, terrain, direction, server build, and damage condition constant. Record acceleration behaviour, route time, resource change, and whether the run completed.
Separate speed, long-distance efficiency, acceleration, beginner availability, cargo, and experimental goals. One engine can be a strong lead in one scenario and a poor fit in another.
Preserve both names as unresolved aliases until the current client or a primary source connects them.
Record the exact vehicle and build. Do not score a compatibility failure as low speed or low power.
Check route, load, server build, damage, resource start state, and whether both tests reached the same finish.
Source labels describe what each link can support—not what its title appears to promise.
Supports the old-garage, repair-and-fuel, procedural-world, solo/multiplayer, and R-to-start premises. It does not list the feature-specific steps on this page.
The title and creator identity were verified through public metadata. Footage, completeness, naming, and current-build accuracy were not independently reviewed.
Names 13 leads and discloses partial post-update measurement coverage. It is a secondary, mostly single-tester source rather than official data or broad consensus.
A current secondary comparison names 13 leads, but this is not an official roster and some aliases remain unresolved.
Choose by scenario. The provisional tier page summarizes community-reported leads while preserving data gaps.
No. The available community source says only part of its consumption data was remeasured after the update.