BeamNG.drive
Revision as of 17:57, 20 October 2026 by Sonicadvance1 (talk | contribs)
BeamNG.drive

| Storefronts | ||
| Operating Systems | Windows, Linux | |
| Engine | Torque 3D | |
| Architecture | x86-64, Arm64 | |
| CPU Features Used | Unknown | |
| Compatibility | Playable | |
| Type | Game | |
| Render API | Direct3D 12, Direct3D 11, Vulkan | |
| Tested OS | 🟥 arm64ec WINE-Proton |
Steps to Run
No special instructions
Quirks
The game ships native arm64 binaries (since v0.40)
Only the launcher uses FEX, beyond the launcher the game will choose its native arm64 binary which FEX isn't used with at all.
Game embeds chromium
Chromium uses more than 39-bit virtual address space. Host system is required to run a 48-bit VA space configuration for this game to run.
Game stutters a lot
The game is constantly jitting code which causes it to stutter heavily and user a lot of RAM for the JIT cache.
D3D12 renderer is broken ingame (since v0.40)
The game has a case of spiky-polgon-syndrome. This happens on native x86 as well so is not a FEX bug. Only tested with RADV (Sonicadvance1).
Vulkan renderer fails under Proton (since v0.40)
This happens on native x86 as well. This is a Proton bug.
D3D11 renderer crashes with arm64 (since v0.40)
The game crashes inside its own code doing a memcpy. Entirely unrelated to FEX.
Problems/Workarounds
Testing Results
This title has been tested on the environments listed below:
| Test Entries | ||||||
|---|---|---|---|---|---|---|
| Revision | Arch of Title | SoC | GPU | Result | Tester | |
| FEX-2610 | x86-64 | AmpereOne-A192-32x | Radeon RX 9070 | No longer works since v0.40 | Sonicadvance1 | |
| FEX-2607-312-g464ec9d | x86-64 | AmpereOne-A192-32x | Radeon RX 9070 | Works fine | Sonicadvance1 | |