Also, this seems to be a regression -- just went back to SteamVR 2.15.6 without changing anything and everything works.
Also, sorry to tag you, @Packetdancer, but I reckon if it is indeed a regression, it's best if treated earlier.
No worries! If this is via vrlink to a Quest headset, I suspect this is a duplicate of another issue that cropped up with a closed-beta game (so wasn't logged in issues here), which I've already fixed in main. However, I'll go see if I can't test with this -- if I'm right about the cause, it'll appear on 2.16.4, but will not turn up on a local build.
Yep, same issue, already fixed. Can repro under 2.16.4, cannot repro under main.
Going to actually fix this on the Quest headset side instead, since the solution in SteamVR broke other things.
I have a Quest-side fix for this now, but there's several other Quest-specific issues I want to address.
Fixed in main (without side effects, this time), but as noted it's in the Quest Steam Link app rather than SteamVR, so it'll be in the next release of that.
The public beta for the Quest app should fix this, if you want to test.
I changed my Steam Link Client to the Public Beta (I think it was 2.2), and tried again. Both games in which I noticed this regression (working in 2.15.6 and not working in 2.16.5 beta) now work!!! 🥇 The games are this one -- One More Delve -- and Spymaster (appid 4391420).
I've experienced an odd thing -- when leaving from VR from the SteamVR overlay, steam link gave me a dialog saying the link was still connected offering me the option to disconnect - but I think it's unrelated to this.
Glad it works! As for the other, that's good to know, though I do know why it would happen. You're correct that it's unrelated to any of this.
Just as an explanation, though, people were often not exiting the VRLink scene, so would bring the shell up later and start a new streaming session (causing the last one to crash), which was creating problems. So it was changed so that if an existing VRLink session was running, we'd bring it to the foreground when you re-launched from the shell.. but that led to people thinking the stream was 'stuck' if they quit and restarted SteamVR on the computer but didn't actually quit the app on the Quest, so it had an outdated session ID.
So, now it does what you've seen: if VRLink is running when you start the shell up again, it will give you the option to Resume or Disconnect. Apparently there's some potential for the VRLink-quit-and-start-shell to have just enough overlap to trigger that state. So before we push the beta to full live, I'll just make it skip the check if we were launched by VRLink quitting (since we already have a flag for that to skip the little startup logo).
Ah, it makes sense. Thanks for the explanation.
Since the beta version has now shipped properly, closing this out. :)
Nothing extracted yet.
Describe the bug
When launching the steam game One More Delve (appid 3847110), it starts with a black screen instead of the game's splash screen and then only colored flashes. But if you bring the steamvr overlay you can see that there are images around.
To Reproduce
Steps to reproduce the behavior:
This is best understood with a video, so I recorded it: https://youtu.be/hX8EQaxvC0U
Expected behavior
Basically the same thing seen behind when the overlay is activated should be seen when it's not
System Information (please complete the following information):
Please use the latest Steam beta client and SteamVR beta for your bug reports!
tar -zcvf ~/Desktop/steam-logs.tar.gz ~/.steam/steam/logs]tar -zcvf ~/Desktop/steam-minidumps.tar.gz /tmp/dumps]steam-minidumps.tar.gz
steam-logs.tar.gz