Hans‑Kristian Arntzen, a key VKD3D‑Proton developer, reportedly described the game as “extremely broken” while preparing compatibility patches for Linux support.
This statement refers to how the game behaves when its Direct3D 12 commands are translated through VKD3D‑Proton—not necessarily to its native Windows performance.
Reports indicate the game requires unusually complex compatibility workarounds in Proton to avoid failures. Some analyses also suggest the engine may perform operations like referencing GPU resources before allocation or modifying descriptor heap data while the GPU is already executing commands—behaviors that Windows drivers may tolerate but that can cause instability in a Vulkan translation environment.
Because translation layers must emulate or reinterpret these behaviors, even small deviations from expected API usage can lead to major problems.
Early Linux testing has revealed several classes of failures affecting both AMD and NVIDIA systems.
Some NVIDIA Linux users have reported reproducible GPU hangs at specific in‑game locations. One example described the game freezing when leaving Miyazu Bay Kakurega and entering the first crossroads, ending with a Vulkan device‑loss error.
Device loss indicates the GPU driver stopped responding to commands, forcing the application to terminate or crash.
Linux players in Steam community threads say the game frequently crashes during startup sequences, benchmark runs, or early gameplay events when using standard Proton builds.
These crashes suggest instability in the rendering pipeline rather than simple configuration errors.
Debug logs from VKD3D‑Proton show warnings about improperly initialized resources and barriers during image transitions, implying that the game’s resource handling may not map cleanly to Vulkan expectations.
This kind of mismatch can trigger rendering corruption, stalls, or GPU driver resets.
Players testing the game during early access have reported a mix of symptoms:
In some cases, players only managed to start or stabilize the game after switching to custom Proton builds or enabling experimental compatibility flags.
Because the Steam Deck runs SteamOS (Linux) with Proton by default, it inherits the same issues affecting desktop Linux systems.
Several experimental workarounds have emerged from early testers.
One commonly shared launch configuration is:
PROTON_VKD3D_HEAP=1 VKD3D_CONFIG=enable_experimental_features,descriptor_heap %command%
These options change how VKD3D‑Proton manages descriptor heaps and memory allocation, which may reduce crashes in some setups.
Some users also report improved stability when:
These solutions are community experiments rather than official fixes, and results vary widely depending on GPU drivers and system configuration.
Improving stability will probably require coordinated fixes across multiple components of the Linux gaming stack.
Possible improvements may arrive through:
Reports indicate that Proton developers are already preparing compatibility changes specifically for Forza Horizon 6. Once those patches land in Proton Experimental or future stable releases, Linux and Steam Deck users may see significantly improved behavior without needing manual tweaks.
Based on current reports, Windows remains the most stable platform for Forza Horizon 6. Early Linux and Steam Deck testing shows the game encountering multiple rendering and GPU stability issues through the Direct3D‑12‑to‑Vulkan translation stack.
For Linux users willing to experiment, custom Proton builds and VKD3D‑Proton launch options may help. But the long‑term solution will likely come from upstream fixes in Proton, VKD3D‑Proton, and graphics drivers as developers work through the compatibility problems uncovered during the game’s launch window.
Comments
0 comments