CTD in VR in Longitude always when getting ready for landing

User Support Hub Crashes (CTDs)
, ,
1

Hi,

I have been having CTDs, always in VR, and always when flying the approach phase of the flight.

It seems that if you “slide” your vr view to the middle of the cockpit, centering the object you wish you use, (ex. turning on landing lights above panel, during descent through 10k), it is ok,

but if you stay seated in the captains seat view, and just look to your right and up, when you click on the item, whatever that may be, the image freezes, and you can no longer use vr.

You also can not get out of vr. It just freezes. This is consistent behavior.

The steam main app says that the flight simulator is still running, but it will not exit vr which is frozen. You have to shut down the flight sim, and reboot if you want to use it again.

This behavior has been observed in several of the aircraft, some by Asobo and some third party, but always with the wt g5000 nav system,

but don’t believe the g5000 has anything to do with it, or it would not lock up selecting landing lights, and other non-nav related items.

If anyone else has been experiencing this, it would be nice to hear from you.

Also if Asobo reads these posts, it would be nice for them to look into this, as it is a steady problem, not just a once in a while situation.

Thank you.

2

Thinking about this, I have experienced CTDs in the A320 Neo stock version and possibly the Fly By Wire version when I have been reaching over with the mouse or possibly zoomed in with the mouse to light switches or to autopilot controls. I thought it was perhaps me crashing out of the program by affecting the 2D screen with the mouse position. 2D screen in windowed mode. I have had this with various headsets. Recently though with the 2D screen possibly in full frame mode and using the Varjo Aero, which I am new to, I had a freeze of VR as you describe and again I was reaching over to the lights or autopilot. The VR image froze and moved around with my head movements. This may have been with the Fly By Wire A320 Development Version or initial playing with the ATR 42-600.

3

Yes, that sounds like what I am experiencing. I think it is in the VR coding, as it seems to transcend aircraft and headsets.

4

Could be. I used to get a slightly different issue only with the Quest 2 where I still got a trackable VR image but it was larger than normal and fish-eyed around you. That used to often occur landing at one particular airport. I’ll pay a bit more attention if I get issues again.

5

I have just experienced this same issue twice in the 787 in VR while trying to turn the landing lights on or off. I use the Index and it was definitely tracking my head movements, but MSFS was just frozen. I also couldn’t alt tab into other windows which was strange too. Everything was just sitting until eventually I had to close the program.

Is there a workaround or solution? Could it be that by looking up and right toward the overhead caused and issue where msfs lost focus of the game or something? It’s weird that this has just recently started happening to me with SU 14.

6

Further investigation, using either method of mouse control (classic or lock) shows all works well in vr until you start to use the mouse “right click” button. When you click the right mouse button more than once it seems, and unless you scoot over into the middle of the cockpit to view your item up close, the system locks up, and although steam will show that the flight simulator is still running, it will not move, it is all frozen in time, and cannot release from vr mode. To use the sim again, you must use the task manager to close msfs 2020 and restart - of course you lose you two hour flight, and the logbook does not give you credit for any portion of your flight.

7

One other item to try that I am currently “testing.” If you typically import an ifr or vfr flight plan when on the world map before selecting fly to get into the aircraft, try not adding a flight plan. I read in another thread that the CTD could be related to the flight plan that MSFS or ATC is trying to access during the flight.

I know this is completely unrelated to turning off landing lights and other things, which is when I was experiencing the CTD, but so far not loading a flight plan is working for me :crossed_fingers:. It could make some sense because most of the base aircraft and many others use WT’s code on this front. These planes automatically have the flight plan loaded when jumping in. Here’s hoping this can help someone else :slight_smile:

8

I typically create a flight plan on simbrief, then import it into navigraph charts where I add the SIDs and STARs and APPs. Then I export it to MSFS 2020 where I import it into the global map area. I typically do not import again once in the aircraft. Are you saying I should not import, just make one at the global map, or just make one in the aircraft itself? That last part threw me a bit.

9

You follow a very similar path to what I normally do. Apparently this bug “may” occur when you load a flight plan from simbrief or navigraph on the world map.

Try only setting your starting position on the world map. That worked for me and I could even import my route once in the cockpit. The downside is the in game ATC doesn’t really know your flight plan, but so far it has at least stopped the CTDs.