VR Discussions, Questions & Feedback

I'm new to VR and it works perfectly, but I notice that the interior of the car is smaller than it should be, as is the steering wheel, does anyone know how to fix this?

 

When racing, enter in options and change world scale or something like in VR settings.

 

I had this and a full reinstal solved the issue.

 

Good morning, everyone.

I'm experiencing stuttering issues when playing on my Quest 3 using the cable and the Oculus software. This only happens when playing via cable; when I use Virtual Desktop with video buffering enabled, the issue doesn't occur.

I've tried everything—I’ve changed the power plan, enabled and disabled Windows graphical options, adjusted screen resolution, changed the refresh rate, tweaked the Nvidia Control Panel settings, enabled and disabled V-Sync... I've even formatted my PC and the drive where my games are installed, and nothing. Every time I play with the cable, the same problem persists… I'm going crazy.

I don't know if this is a Windows issue, an Oculus issue, or something with the headset itself, but it's really frustrating. My only option left is to play through Virtual Desktop.

Is anyone else experiencing this issue? Is there a solution?

I really appreciate your help. Best regards, everyone!

 

Share your debug tool configuration, so maybe we see something weird in there. You need to change a couple of numbers there if change from virtual desktop to cable or otherwise. Also are you using the official cable, and if so, are you sure it isn't damaged?

 

Where is this option within AMS? I've looked and can't find it.

 

Afaik, there is no way to get back into the game. What removed this issue for me was using a USB A to USB C link cable. The type C end at the pc is not as physically secure as a USB A connection.

 

Seems like it could be a cable issue. try my guide for the quest 3 and see if it helps

 

I've have quite noticeably better performance with VD over Link, in mulitple games, and talking to others (in the DCS community mostly), this isn't uncommon.

I'm using OpenXR, as I suggest everyone does, and VDXR is a better, more efficient runtime than the Oculus version. Oculus software also eats up to 3GB VRAM while running, that can be make or break on edge cases, as well as many other issues with the software Meta seem to not care about it. Even Mbucchia, the person behind OpenXR toolkit and Quadviews Fovated, recommends VD, and he definitely knows a thing or two about all this stuff.

Is there a reason you want to use Link? If VD works, why not just stick to it? You can keep using the cable to keep your headset charged (if it's capable)

 

I was having several Meta link problems lately, so I tried VD to see if it is a viable option for AMS2. I noticed the image was a little stretched and with less clarity compared to link, but I didn't want to spend an hour tweaking so I returned to the problematic link software.

I use link cable mainly for latency and the performance improvements the debug tool brings by setting fov and 700 Mb bitrate, but I'm open to try the VD alternative in order to get rid of the bugs and instability the link software has, so I ask if you kindly can give me some tips about how to best configure VD and the OpenXR toolkit to have a similar experience and performance I have with the cable.

Currently I run the Quest 2 at 90 hz, max headset resolution and 1.2 supersampling with Fov at 0.76 / 0.73 It allows my 3080 12G to run at 85% load in any situation but rain and night for more information.

Thank you in advance.

 

In the end, I was able to solve the problem. There were two factors occurring simultaneously. One was the Windows power plan—when you connect the headset and the Oculus app opens automatically, Oculus changes the power plan to "High Performance." The other issue was the priority of the OVRServer_x64.exe service. By default, it is set to "Normal" priority, but it needs to be changed to "High" priority.

Regarding the Windows power plan, I need to find a way to force the "Balanced" power plan because every time I connect the Meta Link headset, it switches the plan to "High Performance," and I have to change it back to "Balanced" manually each time.

 

Honestly, everyone here says something different. In the end you have to run your configuration marathon yourself. You should pay more attention to the "Photon to Motion ms" with the Oculus Debug Tool than anything else. The 700 bit rate is, for example, an absolute increase in latency.