ValveSoftware / ValveSoftware/Proton

Train Sim World 6 (3656800)

Open
#10,088 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Game compatibility - Unofficial XAudio2
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Compatibility Report

  • Name of the game with compatibility issues: Train Sim World 6
  • Steam AppID of the game: 3656800

System Information

I confirm:

  • that I haven't found an existing compatibility report for this game.
  • that I have checked whether there are updates for my system available.

https://github.com/user-attachments/files/31352382/steam-3656800.zip

Symptoms

Starting ca. August 11, 2026, Train Sim World 6 started crashing on Linux upon UEVR injection, if started in DX12 mode using -dx12 parameter. It could be linked with the TSW6 patch released on August 6 (https://steamdb.info/patchnotes/24589550/ ), although I encountered it a few days later.

After clicking "Inject", the UEVR overlay appears for a few seconds, but the game is not displayed in the headset in VR mode, and then crashes.

The game continues to work in DX11 mode, but graphics quality is very poor.

Reproduction

  1. Launch Train Sim World 6 in DirectX 12 mode (-dx12 launch option)
  2. Launch UEVR
  3. Select openvr or openxr
  4. Inject
  5. The UEVR overlay is displayed, there is no video in the headset, then he game crashes and an UE crash window is opened.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No repository file or test is named. Start by reproducing the reported DX12 and UEVR injection sequence, then inspect the attached steam-3656800.zip Proton log and compare it with the working DX11 mode. Done would require identifying and addressing the cause of the crash or documenting the relevant compatibility finding.

Written by the indexing model from the issue text.

Assessment

Tech stack
linux
Domain
operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.