solved: delays when aiming via virtual desktop

[JohnaVR]

solved: amazing support by the devs!
Obsolete:
Hi guys, i am experiencing horrendous delays when aiming in this game. I didnt measure it, but it feels like there is a delay of more than half a second when i am aiming. Smoothingturning reacts normally (like 30-35ms). Setup: 5800x3d, 4090, 32 gb, dedicated wifi6 router (ap mode, directly connected to my pc via cat7 cable). Before someone asks: No, it is not a general problem. The Q2 is the only device on this ap router, and i made sure that the 5ghz channel i am on is only used by me.

[Roland]

Hey Amazing74 - thanks very much for raising this. At the moment due to technical limitations we can't fully support Virtual Desktop. We are however working on this and hope to be able to release a patch for it soon.

In the mean-time, could I please ask you to test if the problem persits with Airlink?

[JohnaVR]

Originally posted by Roland:

Hey Amazing74 - thanks very much for raising this. At the moment due to technical limitations we can't fully support Virtual Desktop. We are however working on this and hope to be able to release a patch for it soon.

In the mean-time, could I please ask you to test if the problem persits with Airlink?

Yes, i will try air link in the evening and give you feedback - thank you for clarifying!

[JohnaVR]

Originally posted by Roland:

Hey Amazing74 - thanks very much for raising this. At the moment due to technical limitations we can't fully support Virtual Desktop. We are however working on this and hope to be able to release a patch for it soon.

In the mean-time, could I please ask you to test if the problem persits with Airlink?

Sorry, but tried it today. Air link has exactly the same behaviour. Stick turning works flawlessly, reacts immediately, aiming with hands is extremely delayed.

[Roland]

Hey Amazing74 - really sorry to hear. The reason that's strange is because during development we all work with the Oculus Quest 2 and test with it extensively without having seen such behaviour.

We'll all be back in the office tomorrow and try to replicate the issue and I'll get back to you with anything we find out as soon as we can.

Sorry again for the inconvenience!

[JohnaVR]

Originally posted by Roland:

Hey Amazing74 - really sorry to hear. The reason that's strange is because during development we all work with the Oculus Quest 2 and test with it extensively without having seen such behaviour.

We'll all be back in the office tomorrow and try to replicate the issue and I'll get back to you with anything we find out as soon as we can.

Sorry again for the inconvenience!

Np, it is EA and you care. Thx for it. Next weekend i will swap my dedicated ap router: Netgear wax 206 for an asus rt ax55 - since alot of people from the VR community highly recommended it. If this changes something on my end, i will let you know.

[Roland]

Hey amazing74 - Just a short update - we're still working on this one and will have to continue testing. We haven't been able to replicate the issue just yet.

Is there any other app you might be running in the background that could potentially be interfering?

[Roland]

Hey amazing74, we haven't been able to replicate the issue but we discussed 2 ideas that might help:

1.) In the Oculus Settings under "General", could you make sure that for "OpenXR Runtime" it's set as "Oculus is set as the active OpenXR runtime"
2.) Could you check if your GPU drivers are all up to date? It could be related to the 4090.

If the problem persits, would you be able to share a video/recording of the controller aim delay?

[JohnaVR]

I will take a look tonight. First i can assure, that all drivers are up to date. Concerning the runtime i will habe a look. Video: Never did something like this. What do you Imagine exactly?

[JohnaVR]

Originally posted by Roland:

Hey amazing74, we haven't been able to replicate the issue but we discussed 2 ideas that might help:

1.) In the Oculus Settings under "General", could you make sure that for "OpenXR Runtime" it's set as "Oculus is set as the active OpenXR runtime"
2.) Could you check if your GPU drivers are all up to date? It could be related to the 4090.

If the problem persits, would you be able to share a video/recording of the controller aim delay?

Hi Roland, runtime is set to "Oculus is set as the active OpenXR runtime". NVidia driver is 535.98.

[JohnaVR]

Ok, i think the problem has been on my end. My q2 as well as the oculus app have been on the beta channel. i updated them to the latest release and set all my odb setting back to default. i changed my nvidia setting back to vr optimized according to this guide https://beastsaber.notion.site/beastsaber/Ultimate-VR-Performance-Optimization-Guide-3a64adf160344f089591a3a21a2aafd7 and prioritzed oculus and vd streaming service in windows task manager. As a result, the delays were not recognizable any more (at least via air link, didn't test vd so far).

[Roland]

Amazing news!!! Really glad to hear that worked!

I think it might very well been have related to it still being on the beta channel. I'll definitely keep this in mind should anyone else run into it!

What we currently know of VD vs. Airlink is that the controller angle is really off compared to where it should be.