sadly im still having this problem
2 Likes
i can finally make vr games, Thanks Roblox!
2 Likes
This issue still hasnāt fixed itself. This has been occuring since June and has made VR development impossible unless you have an Oculus headset, which is much less practical than using a SteamVR headset for Roblox development due to reasons irrelevant to this post. This is not a small deal and I canāt believe itās still happening after essentially 3 months, completely halting development for any VR developers using a SteamVR headset.
6 Likes
As of October 14th this is still happening, and is actively impeding my ability to work on my VR project. This is unacceptable that not only is this happening at all but that it has been happening for about 5 to 6 months now. I really hope they fix this bug because I would really like to make a VR project.
1 Like
When developing on my Meta Quest 2 using Steam VR with Virtual Desktop, I consistently run into this problem with OpenXR. This error completely soft locks my play testing, requiring me to constantly re-open Roblox Studio. It has made any form of VR development I want to do incredibly painful and demotivating.
I understand it was said that this was unsupported in another post, but I have absolutely no other way of developing. I am unable to use air link as I do not have a good enough connection to my router, and I do not have any USB 3 or USB C ports on my computer to manually link.
It was also mentioned that this exact error was being actively worked on back in July, 3 months ago.
1 Like
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