New problem in VR - phasing double image (ghosting)

User Support Hub Install, Performance & Graphics
, , , ,
1

I have a brand new issue appear yesterday that I have not been able to solve. Any advice would be great!

Since I got the latest Virtual Desktop installed automatically (1.32.9) everything I have carefully and painstakingly ironed out is shot to bits. It was working beautifully before, and now everything I have tried so far is not getting rid of this issue.

THE ISSUE:
It’s smooth flowing, always the correct 36 fps (with Spacewarp so 72Hz in the HMD), but it goes through phases of having a double image so everything looks out of focus, then it snaps back into focus for a bit and repeats this. The offset of the ghost image is not much, but very noticeable and makes me feel quite queasy. Seems to be worse (or more often) if I am turning the aircraft around.

It does seem CPU Load related according to the Dev Mode fps readout but I don’t really understand those numbers. In 2D my RdrThread is 4-5ms, as soon as I switch to VR it jumps up to 26ms. That seems like way too much of a change?

Also don’t know what the new Allocs / frame, Sys Allocs and Avg block size means, but they are usually red in VR for me. Is that bad? How do I get it more balanced? Is the 26ms too high? I feel this is the source of the issue.

I have tried:

  • HAGS off or on (was on originally. Off seems a BIT better in that the bad phases don’t last as long)
  • Disable OXR ToolKit
  • DX 11 or 12 (was using 12 originally)
  • Latest Nvidia driver (I got a 4080 and Quest 3)
  • Recommended driver from the VD Discord for this version of VD (552.44 clean install)
  • Cleared DX caches (all, from Safe Mode)
  • No Mods
  • TAA or DLSS
  • With or without a frame rate limit (letting Spacewarp deal with locking to 36, half of my 72Hz)
  • Looked at various similar threads about RdrThread. But this GHOSTING coming and going is the real issue for me.

I have NOT yet tried:

  • Reset OXR ToolKit (it does this even with that fully disabled so doubt it is this)
  • Revert to previous VD. The developer assured me no chances directly towards VR were in this version, but that IS all that changed on my system since it went bad. Seems a pain to revert so trying to avoid this step).
  • Cable Link, not using VD. I have never done it so not even sure how.

Not sure if it is exclusive to Virtual Desktop (not tried any other connection method) but for sure since the update, this issue started and in all my 6 months of tweaking out other performance problems, I have never seen it act this way before.

It is so frustrating. I literally have spent 6 months since getting the Quest 3 tuning it, finally found very good settings last weekend and it was running BEAUTIFULLY, did not fly for a few days, came back to this update and BAM, it’s pretty much unplayable now.

2D:
18 12_01_07

VR - HAGS on:
17 21_19_23

VR - HAGS off:
18 13_09_22

Does this even when GPU is not anywhere near max:
17 21_21_35

Thanks for reading - tearing my hair out here (again…) :sob:
What else can I do? Why has this suddenly started?

1 Like
2

Similiar topic below.
Quest 3 Ghosting/double image problem - User Support Hub / Virtual Reality (VR) - Microsoft Flight Simulator Forums

1 Like
3

Thanks TP.

Yeah I seen that topic before (and could not find it again today) but see it is quite active, thanks. Maybe I will post there or try the Steam Link way, but it is a bit different problem to mine. Mine comes and goes and it WAS working all fine until yesterday, so I know it SHOULD be able to still do the same now with my current config. So annoying :frowning:

1 Like
4

What? Mr. T is having a ghosting problem?
Can’t be so… You should know how to handle alien creatures.

3 Likes
5

Long shot here but could it be a Quest update. I had one yesterday. Tried googling it and couldn’t find anything about it. I’ve got a Quest 2 and I’m not on beta. It was definitely an Update on my headset not on the metaquest link software which usually gives a notification when updating so I’m not sure :thinking:

6

I am not ruling anything out - it could have been. Not much I can do about that!

Something fundamental has changed. Spent 4 hours trying things today and noticed that now, DX11 runs fairly well (was unusable last time I tried, but 12 still seems a bit more consistent) and also not using Riva Tuner SS to cap frame rate works now (just rely on Spacewarp), where before it was a disaster until I found RTSS to be my saviour. Something has really changed, but it’s made it worse for me than what I had. I am gutted. So sad I can’t just fly and have fun… back to troubleshooting in my limited spare time. I give up! I might just sit it out until November and see if that works (I won’t of course, but I really feel like it right now :frowning: )

7

Not quite the same as what you are reporting but since the latest VD update I get a weird thing about 5 minutes after I’ve switched into VR I get this big slowdown to around 5 FPS and the display gets all laggy on me and I get a few artifacts showing up. It only lasts 30 seconds at most and once it hasn’t occurred it doesn’t happen again until the next time I go out and back in to VR. As long as I am not landing, I usually just push through it but if landing I have to pause the sim until it has gotten over its little hissy fit.

Not very helpful for your specific issue but it does show things have gone a bit strange for others with the latest VD update.

I saw your list of things you have tried and are yet to try. One suggestion I have is to try Airlink if you don’t have a cable to connect your Q3 to your PC. I believe it uses the same occulus software as cable link, which I have tried once but then went back to VD as I found it much better.

I hope you find a solution or that VD gets updated again so that these issues go away.

1 Like
8

I finally managed to solve this issue.

In the end, I uninstalled the VD app from the Q3 Head unit (Settings > Storage > Scroll down to VD > Click the Clear Local Data icon on that row, then click the Trash Can).

Then uninstall the desktop Streamer app from Add/Remove programs.

Then go back to Meta Store in the head unit, redownload and install, run it, it says to go to vrdesktop.net to get the Streamer again and reinstall. All back to normal now! Same current version.

I guess something with updates going on top of each other - maybe cumulatively - messed something up deep inside.

The RdrThread still does jump up from 4ms in 2D to 26ms in VR in the exact same scenario though. Any idea if that is normal?

3 Likes