Since the excellent update to the avionics in the Boeing 787, I’ve started flying a lot more in this plane.
However, during the flight (and especially towards the end of a hour-long flight), the display usually starts to go “gooey”, i.e. laggy and mis-shapen (not just stuttery). My workaround is to pause the sim, reboot the headset (Quest 2), re-enter the sim and resume flying. This solves the problem at least for a while, though I may need to repeat the reboot later in the flight.
The sim itself is running ok - if I switch to 2D there’s no problem. So I would guess that the memory in the Quest 2 is becoming full, and that rebooting initiates a garbage collection. The fact that this works suggests that the memory is clogged up with unnecessary data. This only happens in the 787, so I wonder if there is a memory leak in the FS coding?
I have 64Gb of RAM and 11Gb of VRAM, so I wouldn’t think these would be a problem. I’m running on Dx12.
Does anyone else have trouble with VR in the 787, especially on the Quest 2?
Not having had this problem for a year, it has now returned, and is much worse.
Every flight I now take in VR, it goes “gooey” about every ten minutes or so. This now happens whichever aircraft I’m using, wherever or whenever I’m flying. I can cure it each time by exiting and re-entering VR without interrupting the flight, but not good during a landing.
I don’t know if a recent update to the Quest software has caused it, or if it is something Asobo has changed. The sync problem I used to have continuously with the RenderThread causing stutters has now miraculously disappeared, so something has been modified somewhere - maybe this is related.
Has anyone else got this problem?
Sorry my friend, don’t know how to visualize your problem, looks like you are on your own on this one. Trial and error is the only solution I guess there is. As you are running in Dx12, did you try Dx11 etc? Did you try a different VR? Some give you a 30 day try before buy so I would really try that one just to rule out HW or SW. Hope this will help somehow. I’m just starting to use Virtual Desktop with Quest2 and i’m very happy with that for now. Read into it before buying but my guess its your system/network issue… let me know
1 Like
Maybe try DX11 with Hags disabled. This uses a lot less Vram imho.
1 Like
Thanks for both the above suggestions. fyi, I’m running in Windows 11, DX11 with HAGS off.
It looks like it’s working OK now, without me changing anything, so I can’t really investigate further. With FS2024 imminent, the problem may go away completely, though I daresay only to be replaced by some others!
1 Like