I made this post on development discussion, and this bug has remained unfixed for almost seven months. It includes all info about the bug and my operating system.
That would be why it was never noticed & fixed. Categories outside #bug-reports do not go through our internal escalation, notification, and tracking process, so any bug posted outside of bug-reports will never be noticed nor fixed. Now that weâre aware of the bug, we can route it to the right team. Iâll ping the VR team to let them know
Itâs been about a month now, I donât want to hound anyone, but is there any news on this being fixed? Maybe a work around I could use?
Considering it has taken the VR team MONTHS to even acknowledge the âSteamVR opening up randomlyâ bug, Iâd say youâre better off praying that they bother to fix it.
The SteamVR opening randomly issue is a SteamVR bug which you can read more about here BIsHmdPresent always returns true ¡ Issue #428 ¡ ValveSoftware/openvr ¡ GitHub. It seems it was closed without being fixed
The VR team took a look at this bug, but they werenât able to nail down anything further. Iâm not on the VR team, but Iâm interested in collecting some more information.
- Yes
- No
0 voters
- Valve Index
- Quest / Pico Link
- Windows Mixed Reality headset
- Varjo headset
- BigScreen Beyond
- HTC tethered headset
- Pimax tethered headset
- Other
0 voters
- Valve Index
- Quest / Pico Link
- Windows Mixed Reality headset
- Varjo headset
- BigScreen Beyond
- HTC tethered headset
- Pimax tethered headset
- Other
0 voters
Also, if you are using a headset with its own software controller (i.e. if you open SteamVR alone, the headset wonât work. You need to open something like Windows Mixed Reality win10 app, Varjo Base, etc for it to work, so basically anything other than the Index/Vive), there were issues with SteamVR update 2.2.3 that caused severe performance issues in headsets not completely using SteamVR which may be impacting you. If you go to SteamVR in steam, Properties, Betas, and downgrade to temp_1.27.5 (you can go back to latest later), wait for the downgrade to complete, restart VR/Studio, and try again, does the issue still happen?
Thank you for responding.
Would it be possible for the VR team to also check out the âSteamVR opening while running ROBLOX Desktopâ bug? The issue has been reported since late last year and only last month did we get a progress report on it.
See the GitHub issue I linked originally. Itâs rooted in a Valve bug, but I believe there is a setting in the escape menu to disable VR to work around this
Interesting. I recall having the escape menuâs VR setting turned off specifically but still having the issue. I had to use the workaround of moving the âopenpathsvrâ folder in %appdata%/local/
to stop SteamVR from constantly opening and crashing.
As I put it back today and opened ROBLOX, the issue isnât even present, so who knows at this point.
I made a request several months ago to be approved to submit bug reports however it got no response. If I had been approved, I would have reported it much sooner. Would it be possible to push to get me approved for bug reports, or perhaps getting someone to private message me to get approved?
I am currently using pretty much all features of the VR engine and I even built my own engine disabling HeadRotation. I have a lot of foresight about limiting factors of the engine:
- I can destroy the core menu and the bar by destroying the VR parts that are a children of the CurrentCamera.
- (Feature suggest) I would suggest adding a callback to detect when the menu is expanded or not in VR
- I coded a simple VR Jet simulator game. However the bottom bar does not rotate with the jet. This is pretty much impossible to fix unless the bottom bar follows the character rotation (which is unlikely) https://www.roblox.com/share?code=ae022bc8e8f06245a8a32d322b9797de&type=ExperienceDetails&stamp=1712677536515
If this happens again you can message @Bug-Support with a message in the format in a bug report, you get a response in about a few weeks to monthes
Sorry, it looks like this was broken in the OpenXR migration (the thread OP linked in the original topic). The VR team is looking at fixing this
Sorry to bump, but is there any news on when this could be fixed? Itâs still happening even after being reported to a roblox staff almost a year ago now. Or a possible temporary fix?
Just got a Quest 3 and I have the same issue. I got it to make games on Roblox and I can only play them. Studio doesnât wanna run them. Saw someone on a post say that turning off the faster play solo beta fixed the issue however thatâs gone now.
Dont know if this is related, but other than having similar issues (Testing in Studio doesnt work via SteamVR, only via Quest Link) another error pops up about Robloxâs own VRBaseCamera module erroring.
This results in the player not being able to move at all. This only started to show up recently. Any news on this?
For me what works when I get this issue is to switch to server view and back to client view.