Unable to fly in the West Coast USA area

Since 1.5.x.0 (currently on 1.5.2.0) I have been unable to fly using VR in the West coast USA area, this has been happening for the last few nights (GMT+1, UK summer time).

I live in the UK and my current server is Western Europe, my Internet connection is 1Gbit/s - typically running at between 800 - 900 Mbit/s.

My PC has a AMD Ryzen 9 7900X, nVidia 5080, 64GB RAM.

VR is Pico 4 Ultra connected via Virtual Desktop.

I am able to fly in and out of London Heathrow and London City airports (both normally quite demanding locations) with no issues with a frame rate at or about 45 FPS (limited at 45 FPS) typically using about 9 - 12 GB of VRAM.

When I select an airport to fly from in the West coast USA area I am still getting 45 FPS and using a similar amount of VRAM but during or shortly after take off the simulation judders to a halt, followed shortly after by the programme shutting down and returning to desktop, VR still working quite happily via Virtual Desktop.

I can reload the flight simulator and if I select a European Airport all works fine but if I again select an airport in the USA (e.g. John Wayne airport, KSNA, LA Intl KLAX, and others) it still crashes back to the desktop at or shortly after take off.

I have tried a number of nVidia drivers from 572.83 through to the current 576.52 and all fail in the same way.

Any suggestions?

I will try other areas of the world like East Coast USA, South America, Africa, etc. to see how they work.

Edit, I have tried a number of GA aircraft and the same happens with each of them.

Edit 2.
Restarted Sim, and tried the following airports:

Logan - OK no issues
Lisbon, Portugal - OK no issues
Beijing - OK no issues
Honolulu - OK no issues
John Wayne - OK no issues

The last one surprised me so I shut down the Sim and tried John Wayne again, this time it crashed to desktop during take-off.

So not sure what is happening.

Try this. Takeoff from Palm Springs (KPSP) and fly west towards KLAX. Do you make it about 1/2 way (a bit west of KONT) and then MSFS studders badly for 2-3 seconds, then crashes? If so, I had the same problem, repeatable 100% of the time. Tried a bunch of different things and finally fixed it by updating my motherboard BIOS. Hasn’t happened since.

Hi, I tried the flight and it crashed to desktop shortly after take-off.

Updated motherboard BIOS and tried again.

Crashed to desktop as I was pressing the shift key to set my position before take-off!

Tried again after a successful take-off and landing in Europe but once again crashed to desktop shortly after take-off from KPSP.

Bummer. Here’s the other thing I did (found online somewhere), might be worth a try. You can always delete the values if it doesn’t help.

  1. Using RegEdit, add the following 32-Bit DWORD Values
    TdrDelay with Hex value of 3c
    TdrDdiDelay with Hex value of 3c
    to
    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\GraphicsDrivers