protonscr

Five Nights at Freddy's Help Wanted 1 does not render onto the Pico 4 Ultra | Linux Mint

steamvropen bug
ValveSoftware/SteamVR-for-Linux#905 · opened 2026-06-12 by Tidoto · updated 2026-06-16 · 1 comments · github
TTidoto 2026-06-12 github

Describe the bug
FNaF HW 1 when played in VR via ALVR SteamVR does not end up being rendered on the Pico 4 Ultra
in SteamVR its stuck on "Waiting..." with the games icon, despite the game being fully rendered and running when looking at the desktop
everything from head movement to controller movement and even HAND MOVEMENT is properly picked up and responsive when looking at the desktop screen, but on the Pico 4 Ultra it is completely stuck waiting for the game.

To Reproduce
Steps to reproduce the behavior:
setup steamvr for ALVR as instructed: https://github.com/alvr-org/ALVR/wiki/Installation-guide
add -dx12 to FNaF HW 1s launch arguments, otherwise the game will crash.
after connecting the headset and computer and FNaF HW is setup
launch FNaF HW from within steamvr on the pico and watch it not show up on the Pico
why specifically fnaf hw?
when in contact with steam support they asked me to see if a game called "The Lab" worked,
it did,
aside from The Lab and FNaF HW i dont have another VR game to test

Expected behavior
SteamVR should be stuck waiting for the game and the game should be visible on the main desktop

System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
(steamvr beta and regular have an unimaginable desync (up to 5 seconds of delay)only [previous] doesnt have, with the error "something is wrong, please reinstall steamvr (303)
pls fix this before removing the 28.05.2026 previous branch....)

  • Steam client version (build number or date):
    Steam Beta Branch: Stable Client
    Steam Version: 1781041600
    Steam Client Build Date: Tue, Jun 9 23:11 UTC -08:00
    Steam Web Build Date: Tue, Jun 9 21:23 UTC -08:00
    Steam API Version: SteamClient023
  • SteamVR version: 28.05.2026 previous(2.12.14){this is the only version that for me does not have a 5 second delay.}
  • Distribution (e.g. Ubuntu): Linux Mint
  • Steam runtime diagnostics: [generate via Help -> Steam Runtime Diagnostics in the Steam client]

steamruntimediagnostics.txt

  • Steam and SteamVR logs: [generate by running this command in a terminal tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]

steam-logs.tar.gz

  • Minidumps: [run the following command: tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]

steam-minidumps.tar.gz

Screenshots
If applicable, add screenshots to help explain your problem.

Image

Additional context
like i stated before
the Beta and Public Branch are completely unplayable, hence why i use the previous branch
furthermore, i also tried using WiVRn, this had the problem that game would just freeze up
on windows none of these issues exist, i dont even have to add -dx12 to the game launch arguments for it to work
without that argument i sadly also never get anything rendered on my pico
my connection is a stable 1.4gbps(ethernet to router -> wifi 7 6ghz to pico)
hence why i can confirm that these desync issues are for sure a problem with steamvr itself and that only on linux.

PPacketdancer 2026-06-16 github

This sounds like it may be partially an ALVR bug? If you use the public or beta branch with Steam Link (using the APK that's bundled into SteamVR), rather than ALVR, do you see the same problems? ALVR tries to modify SteamVR itself, which can lead to all sorts of unpredictable problems.

At any rate, I just tested several times with SteamVR 2.17.2 (current beta) and Steam Link 2.0.22 (you can use drivers/vrlink/resources/android-steamlinkvr-release.apk that you find in a SteamVR install to get a current build) first with an Nvidia card and second with a Radeon, and I didn't need to add any additional settings to FNAF HW VR. I just ran it and got to the menu without issue.

Admittedly, this was on a Quest 3 and on Ubuntu; I'll dig up a Mint install later and a Pico to double-check, but this feels like it may be an ALVR thing? So I'd be curious whether you see the same problems with a clean install of a current SteamVR build and Steam Link app.

Nothing extracted yet.