protonscr

[SteamRT3] fallout new vegas cannot find installation

steamopen
ValveSoftware/steam-for-linux#13022 · opened 2026-03-21 by oggytheman · updated 2026-04-01 · 2 comments · github
1 matching comments, n / p to jump
Ooggytheman 2026-03-21 github

Your system information

  • Steam client version (build number or date): Steam Client Beta - March 19th
  • Distribution (e.g. Ubuntu): cachyos
  • Opted into Steam client beta?: [Yes/No] yes
  • Have you checked for system updates?: [Yes/No] yes
  • Steam Logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]
  • GPU: rtx 4070

Please describe your issue in as much detail as possible:

When installing Fallout: New Vegas while opted into the SteamRT3 client, the game behaves as if it isn’t installed when launched. only way to fix it is to install new vegas using the normal client.

it's worth noting that if the initial install was done thru the normal client switching back and forth between the normal client and rt3 seems to have no effect the game still recognises the installation

Steps for reproducing this issue:

  1. install steam beta
  2. opt into experimental SteamRT3
  3. download and install fallout new vegas
Kkisak-valve maintainer 2026-03-21 github

Hello @oggytheman, this reads like #13007 and/or #13008. Can you check if either of those are relevant to your system?

Ooggytheman 2026-03-21 github

Hello @oggytheman, this reads like [#13007](https://github.com/ValveSoftware/steam-for-linux/issues/13007) and/or [#13008](https://github.com/ValveSoftware/steam-for-linux/issues/13008). Can you check if either of those are relevant to your system?

@kisak-valve #13008 is definitely related not sure about #13007 tho. i installed schedule 1 while in rt3 so if i stay opt in if i try a launch command like PROTON_LOG=1 the log file doesn't show up in home even if i add PROTON_LOG_DIR but once i opt out of rt3 it does.

whats interesting tho is if im using rt3 and if i just write PROTON_LOG the game will not launch so obviously it's still reading the custom command