Problems with Virtual Desktop and Q3

VD has been running perfectly until a few days ago. I use both 2020 and 2024 in VR coonected by VD to my Q3. I now have problems connecting to the sim. When I first connect my Q3 I get the desktop in my Q3. I then press a programmed button on my joystick and VR starts in MSFS. If I take a break by reverting back to 2D (usually to make a cup of tea) when I return I now find that I cannot connect to the sim anymore and I just see the virtual desktop in my Q3.
Sometimes I don’t even see the desktop, just a black void. I can press the meta button and the VD settings menu appears but as soon as I press the meta button again the menu dissappears and Im back to the black void.
I have done everything including resetting, reinstalling everything and making sure there are exceptions in my security for VD. Any ideas whats going on? I have a dedicated 6e router.

1 Like

This was happening to me until the recent update. VD and pico 4. Still does it now sometimes but only briefly, less than 10 seconds. Before it would never come back. It seemed to be worse with more complex aircraft and complex airports.

1 Like

i think it is a photo window and i get rid of it by ESC twice

No, that didn’t work. It looks like VD gets stuck between desktop and game.

the Quest 3 is the problem. If you put it to sleep it struggles to connect through VD. If you put it to sleep the IMU gets confused and tracking is off, also Motion compensation in motion rig is way off.
My rule of thumb. Power down or restart the Quest 3 every session. Pain in the #@! but that’s the reality. It is not VD.

SamE issue here. My fix is to close everything VD related in Task Manager and then start VD again. Works every time.

No need to restart the Sim or the headset

1 Like

Had that two, killing VD in the task manager helped as well.

Yeah, that’s what I’ve resorted to doing now. I ran the VD repair tool as well. There’s other people on VD discord who are reporting similar issues which started around the 10th December, about the same time I started to suffer from these problems. Never had a problem before switching in and out of VR on the Q3. Very strange.

same problem here

1 Like

I never put it to sleep, I turn it off and it still happens to me anyway.

Hi , i have the same error on quest 3 , its says ur graphic card drivers are not updated or try to disable hdr , hdr is off drivers are updated ai have 566.14 nvidia , my graphic card nvidia rtx 4070 ti oc , cpu Amd 5800 x 3d , 64 gb ram , windows 10 the game is msfs 2024 , game crash in vr headset in 4-5 min sometimes even faster im on wi-fi 6 , with computer conected with cable gigabit internet

i have to manualy close virtual streamer from task manager , start the game over again or restart the computer & the headset becouse its not streaming enymore

I rolled back to the 560.94 driver. This is the one recommended by the VD team.
My problems started before my Q3 updated to 72 as well.

VD devs recommend using 552.44.

I don’t have that issue with 2020. 2024 is so mucked up I haven’t tried since the release.

Apologies, my mistake. Yes they advise using 552.44.

1 Like

I think the problem occurs when using AV1. Using HEVC 10-bit doesn’t cause any issues, or at least in the time I’ve been testing it, it hasn’t happened. With AV1, it’s rare to have a session that doesn’t crash.

2 Likes

I will try this. VR on MSFS2020 has never been better for me. Super smooth and with great clarity. I can even fly the IFE F14 and Tornado at ridiculous speeds at low level with only the odd micro stutter. I use 2020 far more than 2024 at the moment.

1 Like

I agree. It’s fantastic in every department. Runs smoothly and is clear as day

1 Like

I’ve tried switching the codec from AV1 to HEVC 10-bit, and it definitely fixes the problem. However, I have a feeling that this codec has slightly worse picture quality and affects the FPS. But I may be wrong; it needs more testing.

In the VD Discord, support suggests switching to the older Nvidia driver 552.44. But I could not find anyone reporting that it fixes the issue. Did anyone here try switching to the suggested older Nvidia driver and can report if it helped?

I’m now on 522.44 and although things are slightly better with less black screen freezes it isn’t perfect.