GerryJ

I installed 61B and was pleased to fly in and find all was well. I’d previously moved the fsAerodata entries in the scenery config file below all Orbx/FTX entries to resolve issues at other airports. As a test I moved the first FSAD entry (FSAD_Comms) above 61B and immediately got elevation issues and duplicate runways. My aircraft with the RXP GTN 750 and that use their own data such as the MilViz KA350i deny the existence of 61B but list KBVU. Aircraft that use data from P3D show both 61B and KBVU but don’t list any approaches for 61B. I’m not sure what will happen on the next Navigraph/fsAerodata update but for now I’m happy to navigate to KBVU regardless of what Orbx calls it. FYI, that’s the Southern Nevada Veterans Memorial Cemetery bordering the east side of the airport. My father in-law is buried there. Thank you Orbx team for rendering it in such detail.

I haven’t purchased Orbx 61B as yet but did have elevation and duplicate runway issues due to conflicts with P3D’s 61B and updated Navigraph/fsAerodata for KBVU. I fixed it by disabling (not deleting) the conflicting 61B files. If Orbx doesn’t provide some means (optional patch perhaps) of correcting the ICAO designation, then those of us who receive regular Navigraph/fsAerodata updates will have a problem. I do very much want this Orbx scenery though for sentimental reasons. I do find it interesting that Orbx went with the old ICAO for 61B but went with the new ICAO for KGPI, formerly KFCA. I had similar issues there when I installed the Orbx product and fixed it similarly by disabling the duplicates. Another means to eliminate conflicts with Navigraph/fsAerodata is to ensure they are below any Orbx/FTX entries in the scenery config. Doing this eliminated a problem with elevations and duplicate runways at KFHR. You may lose access to updated approaches, etc however.