It was annoying before when I had to unplug my vive in order for roblox to not boot up SteamVR whenever I start studio, but now it boots SteamVR no matter how many cables I unplug. Just started happening tonight.
It also boots it in a weird state so that it can’t be closed except by the task manager.
When you press F5 does the test game start in a VR mode? Studio by default boots into VR mode if it looks like it should be running. Perhaps @zeuxcg can shed more light on this.
Video:
It doesn’t run in VR mode, it just starts SteamVR.
https://steamcommunity.com/app/250820/discussions/3/152391285465740813/
Looks like it’s a SteamVR issue.
I’m having this issue too, it’s quite annoying, hope it gets fixed
I’m getting this bug, but it also happens when I join a game. It’s quite annoying.
My mod manager offers the option to disable this:
Here’s the fix, go into SteamVR settings > Developer > Start SteamVR when an application starts
The negative/positive to this is you have to start SteamVR manually now, I personally prefer this
Wait no I was wrong, it’s still happening
We’ve found a way to change out init code for this to stop happening. If Vive is plugged in SteamVR will still start when Studio opens, but if it’s not plugged it it won’t.
This will ship next week. I know some of you want a VR switch in addition to that but that’s a much larger effort that involves product changes so don’t ask me about that 
I’d be okay with it just being a setting that requires studio to restart, if thats possible.
I’ve been able to suppress VR from starting by removing the steamvr_api.dll file, so maybe the setting should make it so ROBLOX doesn’t try to make calls to that DLL file if told to disable it?
The SteamVR fix has shipped - now if your Vive is not plugged in neither client nor studio start SteamVR.
Was this reverted? I’m experiencing this behavior again. My Vive is completely unplugged (power, USB, HDMI) but SteamVR is starting up whenever I open a place in Studio or play a game:
I’m having the same problems and It’s really frustrating.
It wasn’t reverted but it’s possible a new SteamVR update broke the workaround we had to apply. I’m not sure if there’s another workaround possible - I’ll add this on my list to look at but it won’t happen this month.
Confirmed the issue - it happens even if you never had Vive installed, just SteamVR installation is enough. <3 Valve.
I posted the issue on Steam forums, let’s see what they say. http://steamcommunity.com/app/358720/discussions/0/133258092236343488/
New development!
First, I found another workaround that we’ll try to ship soon-ish (it didn’t make the cutoff for next week so it’ll be around mid-May).
Second, Valve has acknowledged this bug and fixed it but it looks like it will only roll out to all Steam users around end of June.
https://github.com/ValveSoftware/openvr/issues/428 has details
After reading through your hotfix code, I was hoping you could explain how it works a little. I’m confused why you’d be able to find lighthouses, don’t those connect wirelessly to the headset/linkbox? Why not look for the headset itself?
The lighthouse comment in the code is slightly incorrect, it refers to the “lighthouse” driver which I believe refers to “headsets that use Lighthouse technology” rather than “Lighthouse base stations”.
The USB devices it actually finds are the devices plugged in through the linkbox, specifically some tracking equipment inside the headset I believe.
Aaaand the fix is live now. I spent the last 3 weeks with Steam/SteamVR both installed so that I could feel the pain. The pain is now gone.
SteamVR is still started if you have your Vive plugged in, but it’s enough to unplug any of the 3 cables so that it doesn’t happen anymore.
