[RESOLVED] Can’t access airports or airspace in vast area!
Posted: Wed Aug 14, 2019 2:11 am
Since my previous post, I have more info, so I am trying again, starting from scratch, with some Qs raised by prior responses on this and other forums.
I recently returned home from a 2-week absence. P3D seemed normal, but I experienced 2 events before noticing anything was amiss: (1) a big Windows 10 update, and (2) a power outage. It was after these 2 events that I first noticed I couldn’t access California. At first, I thought the problem may lie in Orbx and its west coast regions. Not so, however.
Since last week, I have done numerous experiments: the inaccessible airports and airspace are unrelated to whether they are covered by Orbx landclass or regions; Australia and Papua New Guinea are fine, New Zealand and Samoa not; Denver and Jackson Hole are fine, Las Vegas and everything west (including all of Alaska and Hawaii), not; Japan is OK. So far, all the inaccessible places SEEM to be contiguous, a vast area starting at the US Pacific Time Zone and extending across the Pacific to somewhere between Australia and NZ. But other than that, the sim is working perfectly! : )
All my Orbx sceneries, Global and regional, have been verified and updated and said to be “Installed and up-to date!”
One more datum: when I try to load an inaccessible airport, it seems to load in part – there’s the engine sound and a black screen with red letters at the top right indicating zoom ratio, as normal; but then it crashes to desk.
Others here and on another forum have persuaded me that I need to do a reinstall, although I am inclined to try a repair first. Hence, my questions:
How do I do a repair? Do I just click the repair option on the P3D icon in the Win10 control panel?
What does “reinstalling the client” mean?
How do you do a complete reinstall? Where are ALL the files I must back up before proceeding?
What about add-ons? I have much Orbx scenery, plus Rex Textures and SkyForce3D. Do I ignore them and worry about reinstalling them as necessary after I reinstall P3D?
Obviously, any less drastic suggestions would be welcome.
Good night all, and thanks in advance,
Mac6737
I recently returned home from a 2-week absence. P3D seemed normal, but I experienced 2 events before noticing anything was amiss: (1) a big Windows 10 update, and (2) a power outage. It was after these 2 events that I first noticed I couldn’t access California. At first, I thought the problem may lie in Orbx and its west coast regions. Not so, however.
Since last week, I have done numerous experiments: the inaccessible airports and airspace are unrelated to whether they are covered by Orbx landclass or regions; Australia and Papua New Guinea are fine, New Zealand and Samoa not; Denver and Jackson Hole are fine, Las Vegas and everything west (including all of Alaska and Hawaii), not; Japan is OK. So far, all the inaccessible places SEEM to be contiguous, a vast area starting at the US Pacific Time Zone and extending across the Pacific to somewhere between Australia and NZ. But other than that, the sim is working perfectly! : )
All my Orbx sceneries, Global and regional, have been verified and updated and said to be “Installed and up-to date!”
One more datum: when I try to load an inaccessible airport, it seems to load in part – there’s the engine sound and a black screen with red letters at the top right indicating zoom ratio, as normal; but then it crashes to desk.
Others here and on another forum have persuaded me that I need to do a reinstall, although I am inclined to try a repair first. Hence, my questions:
How do I do a repair? Do I just click the repair option on the P3D icon in the Win10 control panel?
What does “reinstalling the client” mean?
How do you do a complete reinstall? Where are ALL the files I must back up before proceeding?
What about add-ons? I have much Orbx scenery, plus Rex Textures and SkyForce3D. Do I ignore them and worry about reinstalling them as necessary after I reinstall P3D?
Obviously, any less drastic suggestions would be welcome.
Good night all, and thanks in advance,
Mac6737