Hi there, I’m sorry to hear about your issues. Unfortunately, I don’t know about any updates to the OpenXR issue, but have you considered developing natively on the Quest 2? My current development flow is to publish to a private place and open it on the Quest app whenever I need to test in VR. It’s not perfect, but we are actively working on improving the VR development flow.
2 Likes
This is currently happening to anyone using Steam VR I believe.
I got a headset to develop with and the next day you guys released this VR update which also introduced this bug.
Haven’t been able to do anything Roblox related with it at all because this bug makes it far too time consuming to be viable.
A fix was promised ages ago but not too surprisingly nothing has been done.
3 Likes
Thank you for the solution, that is something I am able to do. It is a little more tedious to debug client/server issues but that’s better than not being able to playtest 
3 Likes
The same happens to me with my Pico 4. The first time I playtest it works flawlessly, but stopping and restarting the playtest causes this error.
At first I thought it has something to do with SteamVR 2.0 but reading the bug reports suggest it’s an error on Roblox’s side. Hopefully we’ll see a fix or at least a workaround for people that have to rely on SteamVR soon.
4 Likes
I’m still having this issue, how is this still a problem? Has ANYONE fixed this?
1 Like
Still having this issue, i have Pico 4 and this issue happens for no reason, i just start the game in studio and it only works perfectly for the first time, the second time it gives this error, i tried everything i could but it still does that.
1 Like
still having this issue (as of december 11), this error also happens on steam link for quest. still surprised this hasn’t been fixed for almost half a year
1 Like
Late, but does anyone have a fix now? It’s nearing christmas, a nice present would be a fix for this.
4 Likes
The issue is still present. Development is really really difficult thanks to this error causing me to need to restart studio every time I want to test.
Yes this issue is still present, I really wanted to change over to VR development but realized it’s not even viable on Roblox and I doubt it will be any time within the next few years at this rate.
1 Like
Update: It appears this problem seems resolved as I no longer have OpenXR errors the second time I press play in studio. (Valve Index)
2 Likes
ROBLOX will probably never go on the vision pro, even if it is who is gonna buy the apple vision pro - its too expensive and no controllers
To be real, this is solely dependant on if the Vision Pro will get regular upkeep, maintenance, newer model releases that are less expensive. To be honest, it’s completely reasonable that the “Pro” assumes “premium product of the line” like Apple’s iPhone 11 Pro which is a premium product to the iPhone 11. So, what if we wait for an “Apple Vision?”
1 Like
Update: There seems to be an error with the core scripts whenever I run a fresh baseplate. Using Valve Index, however functionality does not seem to be compromised despite the visual of an error.
1 Like
@AurumPhoenix @atfdaj @NobleReign @cryisaguynnx @GrilledSnakeLegs @mbramblet @PoweredToFour @DArkR4v_N @CrownedFigure @Damekn @HooferBevelops @SirteXx @The_BucketHead @ABadScripter15 @doqe_wow @pat7ick @cswaven @Lil_ExcaIibur
Are you still experiencing the issue you reported in this thread (and has since had a dedicated bug report created here Huge VR Compatability issue)?
Can you vote on these polls here so we can get an idea of impact? Huge VR Compatability issue - #5 by Subcritical_alt
3 Likes
I’m still getting issues and to be honest it’s worse than before now. Before I could at least play test once before getting the same error. I’ve voted, and I’ll drop the error just in case.
Specs:
Valve Index
AMD Radeon RX 6700 XT
AMD Ryzen 7 5700 X 8-Core
3200hz 32 GB of DDR4 memory
Error:
2 Likes
For me, it’s hit or miss. Sometimes I don’t get this error but other times the error does occur. The error has occurred more than it hasn’t.
It still occurs and is definitely worse than before. Before, it would only happen if I were to playtest, edit a script, then playtest again, or switch to server view during a playtest. Now, it’s happening on the first playtest without editing any scripts or switching views, making it impossible to develop in VR right now.
1 Like
just got around to being able to try and i can confirm, happened on the first try 
UPDATE: Turning off the “Faster Play Solo” beta feature appears to revert me to the previous behavior of “one playtest and then never again”
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.