"Roblox may not be compatible with some Virtual Reality (VR) headsets" error after today's update

This has 100% started with today’s update, Roblox client updated, restarted, and I started to see the error.

image

This error is from Windows Explorer, I have used a VR headset before with Roblox app but it is not plugged in at this time, I get this error on every time I launch an experience.

This error has had no negative experience to my gameplay.

System info:
VR headset: Oculus Quest 2, default VR app is Steam VR
Windows version: Windows 11 Pro 23H2 22635.3570
RTX 3080, Ryzen 7 3800X

24 Likes

Hello Aerodymier,

In a nutshell, the issue is that VR management software injects a DLL into our process (even if the headset is not active). This is an issue we tried to replicate for a very long time in-house, and we have finally succeeded. The issue manifests itself in the form of a random crash. In other words, there is a good chance that you might not crash at all. With this message, we wanted to make users aware that there might be a crash. Before Hyperion 4.0, the client simply crashed without any indication of why. To be clear, this is not an issue of Hyperion intentionally crashing the client due to badware detection; the problem is that the injected DLL crashes Hyperion.

Of course, the message is just a workaround. We are reaching out to the Oculus team, and we hope that together we can come up with a satisfying solution.

28 Likes

I’m also getting this error every time I start Roblox. I don’t have a VR headset plugged in, I closed all VR software, I disabled VR mode in Roblox’s menu, yet it still pops up every time. The error should tell you what the software is, because I have no idea what’s triggering this.

3 Likes

I uninstalled the Oculus app and the deleted the Oculus folder in C:\Program Files and that solved the problem for me

1 Like

I have been forced to entirely disable my Oculus software due to a different issue so I shouldn’t have any ‘VR software’ actively running yet still receive this warning, is this a mistake or is this simply triggered in many more cases than the aforementioned specific one?

I kind of need my Oculus/Meta software for Quest Link, so I’m not just going to uninstall the app…

1 Like

Please read my post carefully. It is a warning that it might crash, not that it will crash.

You can prevent this in real-time by changing and/or disabling (blank value) the OpenXR runtime at HKEY_LOCAL_MACHINE\SOFTWARE\Khronos\OpenXR in the registry editor, but most VR applications won’t launch in VR while this is the case. You’d have to change it back to it’s original value in order to do that.

Hoping this resolves my issue with the client crashing inconsistently, but very often, even while not in VR.

Edit: It most certainly has :smile:

same problem here, I can no longer play Roblox due to this so will I have to wait weeks or more till Roblox fixes it?

1 Like

I just figured out why I cannot open Roblox.

I deleted Logitech g hub program and Roblox started working… but I need that program to play other games and to use some of my hardware…

Why can’t you play Roblox anymore? Does it crash all the time after you acknowledge the notification? As mentioned, this is just a notification; you should still be able to play.

I thought it’s the notification but figured out Roblox started to work once I deleted Logitech g hub

1 Like

I’ve been getting this and my roblox has been crashing a lot recently as well out of the blue. Nothing changed outside of that so i don’t know why.

Seems one reason for it is the Logitech racing wheel, unplugging it allowed for me to launch roblox

Will there be any sort of announcement to when or if this issue get fixed? This crashing and notifications has been getting out of control for me.

Hello all,

We have been talking with Meta, and the issue was acknowledged, with a fix promised. On our side, we have added a Hyperion fix/workaround that is scheduled to be released with the next client update. Keep in mind that releases don’t always make it on schedule, so there is still room for change. Also, since the issue requires a cross-company effort, there is a limit to how well our fix works until Meta releases a fix on their end.

4 Likes

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.