I found another example that looks like the same transcoded-video regression with experimental SteamRT3 enabled.
Game: Borderlands 3
Behavior:
| SteamRT3 disabled: the game starts with the normal intro video | SteamRT3 enabled: the intro video is replaced by the SMPTE/test pattern placeholder ("Loading. Please Wait.") |
|---|---|
This makes it look less like a Resident Evil 4-specific issue and more like a broader SteamRT3 regression affecting pre-rendered/transcoded video playback.
Proton-GE handles these transcoded videos well. Fixed the exact same issue in another Capcom game for me, after SteamRT3 regression.
In particular, even if the videos are still being replaced by placeholders, PROTON_LOG=1 should now give you a more useful log.
Retested with client version 1774577504.
The videos are still being replaced by placeholders, but PROTON_LOG=1 now produces a log.
Attached: steam-2050650.zip
Can someone please re-test this? This may have been fixed in recent beta versions.
I've tested using a different game (Choppy Cuts) and I'm still seeing the same issue: the menu movie doesn't play in the RT3 client but does play in the original client. The view in the RT3 client is essentially the same as the color bars picture in NTMan's comment, but with the Choppy Cuts main menu on top of it. I don't know if this is the exact same issue as the one reported here, but I'll try to give whatever info I can.
Steam client version: 1780098236
Game: Choppy Cuts
Proton version: 10.0-4
Log: steam-2947650.zip
proton experimentalx1 2026-03PROTON_LOG=1x2 2026-03PROTON_LOG=1`x2 2026-03PROTON_LOG_DIR=/home/mikhail/proton-logsx1 2026-03
Summary:
After enabling the experimental SteamRT3 Steam Client, Resident Evil 4 starts showing corrupted phone/radio cutscenes and missing cutscene audio. At the same time, Proton logging stops working, and Steam Runtime Diagnostics also fails.
What happens in-game:
In cutscenes where Leon communicates via the in-game phone/radio screen, the expected display is replaced with a test pattern / color bars, and the cutscene audio is missing.
Additional regression symptoms:
Control test:
I used the same launch options in both cases:
PROTON_LOG=1 PROTON_LOG_DIR=/home/mikhail/proton-logs %command%
no Proton log is created in /home/mikhail/proton-logs
Proton log is created successfully in /home/mikhail/proton-logs
This strongly suggests the regression is caused by the experimental SteamRT3 Steam Client / runtime layer rather than by the game itself or by my Proton log path.
Steam Runtime Diagnostics failure:
When SteamRT3 is enabled, Help -> Steam Runtime Diagnostics does not work and reports:
"LD_* scout runtime" information:
/bin/sh: 1: /home/mikhail/.local/share/Steam/steamrt64/steam-runtime/amd64/usr/bin/steam-runtime-system-info: not found
CClientJobGatherRuntimeInformation: "scout runtime container" container read output failed
CClientJobGatherRuntimeInformation: "soldier runtime container" container read output failed
CClientJobGatherRuntimeInformation: "sniper runtime container" container read output failed
Reproduction steps:
Settings -> Interface -> Use experimental SteamRT3 Steam Client
PROTON_LOG=1 PROTON_LOG_DIR=/home/mikhail/proton-logs %command%
Expected result:
Actual result:
Environment:
Attachments: