Rust (252490)

Compatibility Report

• Name of the game with compatibility issues: Rust
• Steam AppID of the game: 252490

System Information

• GPU: GTX 1080ti
• Driver/LLVM version: nvidia 435.24.02
• Kernel version: 5.2.14-arch1-1-fsync
• Link to full system information report: https://pastebin.com/Q8ch0JER
• Proton version: 3.16-9, 4.2-9, 4.11-6

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.

steam-252490.log

Symptoms

There are several problems with this game when run via Proton.

1. EAC doesn't work. I won't elaborate on that because it's a well known issue that impacts far more than Rust.
2. The title screen videos do not play.
3. In-game server browser causes the game to freeze. This issue does not occur when using Wine to run the game in Steam for Windows. Only when using Proton from native Steam.
4. Upon exiting the game, it's process usually remains running in the background until killed with a task manager.

Despite all these problems, once a person manages to get in-game, it works quite well (better than the native version ever did for me).

Reproduction

1. Launch Rust with Proton (any version other than 3.7, which seems to fail to connect to steam's services).
2. You should now be looking at the main menu. There is supposed to be a video playing here, but there isn't. If you hit F1 to bring up the in-game console, you will see a debug message saying that it's loading the video. Clearly something went wrong after that point.
   3a. Click on "Play Game". The game will now crash.
   3b. Alternatively, click on "Quit". The game will hang for a short while, but eventually the window should disappear.
3. Look in your task manager for "Rust.exe". This process will continue to run until it is forceably terminated.

Start by reviewing steam-252490.log and reproducing the listed title-video, server-browser, crash, and lingering-process symptoms with the reported Proton versions. Compare behavior across the reproduction steps and use the existing system information to narrow the affected subsystem. Done means the reported launch, menu, exit, and process-lifecycle problems are addressed and the reproduction steps no longer fail.