Hawkeye

RE Steps: Failing to remove FsAerodata from the P3DV5 addons folder will result in a startup message every time stating that it can't find the addon files. To eliminate these annoying messages, use the following steps instead of the steps above. 1) Launch FSAD and note where the original P3DV5 files were backed up to (e.g., C:\fsad_backup_org\Prepar3D v5) 2) Navigate to that directory and make note the scenery folders that were backed up (e.g., 0000 through 1107 and World). 3) Navigate to P3DV5 scenery folder (e.g., C:\Lockheed Martin\Prepar3D v5\Scenery) and delete those files 4) Navigate back to the FSAD folder and copy those backup files back into the scenery folder (note - I did this because I wasn't sure if the P3D "repair" option would regenerate them if they weren't found at all). 5) If you have no other P3D versions you can now uninstall FSAD by navigating to C:\Program Files (x86)\fsAerodata and launch the uninst000.exe executable or it may be removed under windows apps. 6) If you only want to remove it from P3DV5 you must navigate to the P3DV5 addon folder (i.e., C:\Users\<Name>\Documents\Prepar3D v5 Add-ons) and delete the FsAerdata folder. 7) Navigate to the folder where you saved your last P3DV5 update executable and launch the "Setup_Prepar3D.exe" executable (suggest doing this as administrator) Select the repair P3D option and let it complete the repair 9) Launch Prepar3D your normal way.

Issue Resolved: The cause of this conflict was indeed FSaerodata (FSAD). I still have my older P3DV4 version with the same Orbx and Flightbeam scenery options. On this P3d configuration, the KPDX ILS worked normally- even with FSAD navaid database installed/enabled. FSAD has an install option for P3dV5 so I assumed full compatibility. After searching similar topics on other forums (AVSIM specifically) I read a post that FSAD is not fully compatible for all navaids with P3DV5, and that as P3dV5 or 3rd party addon databases are further updated it will become even less so. I tried to disable FSAD from the P3DV5 addon folder and that didn't work. The fix is to completely remove FSAD and associated files from P3DV5 and restore the default files. Steps for doing this are provided below: 1) Launch FSAD and note where the original P3DV5 files were backed up to (e.g., C:\fsad_backup_org\Prepar3D v5) 2) Navigate to that directory and make note the scenery folders that were backed up (e.g., 0000 through 1107 and World). 3) Navigate to P3DV5 scenery folder (e.g., C:\Lockheed Martin\Prepar3D v5\Scenery) and delete those files 4) Navigate back to the FSAD folder and copy those backup files back into the scenery folder (note - I did this because I wasn't sure if the P3D "repair" option would regenerate them if they weren't found at all). 5) Navigate to the folder where you saved your last P3DV5 update executable and launch the "Setup_Prepar3D.exe" executable (suggest doing this as administrator) 6) Select the repair P3D option and let it complete the repair 7) Launch Prepar3D your normal way. You will see messages telling you that certain FDAD files can't be found. That is normal because we removed them. Select the option to unload these files from P3D. 9) You now have your normal ILS back.

Hello, I attempted an ILS 10L approach at Portland (freq 111.3) and noted that the glide slope needle deflected as a localizer back course (I.e., I had to turn the opposite direction from the deflection when the 10L front course of 103 deg was dialed into the OBS and had no vertical guidance deflection/off flag). The 28R ILS behaved normally (same freq. used for both). Approaches to 10R/28L also indicated normally. Navigraph Approach Charts don't designate 10L to be a back course approach. I have all Orbx Cityscape Portland and Orbx Pacific Northwest region along with Flightbeam KPDX in use on P3DV5.3. Is this normal behavior for that approach? Can someone check? Are others sim pilots reporting this same issue? I'm not that bent out of shape about this because, hey...what true pilot doesn't enjoy an occasional Localizer back course thrown at them in in the soup? It is just that it took a couple a couple of missed approaches and finally hand flying the Maddog while running on fumes to figure it all out...and only knocked some of the fillings out of my passenger's teeth when I landed. BTY...I also had a subscription to FSAerodata for many years until they stopped offering their (paid) service last year. I downloaded their last cycle (NavData Cycle 2112). and I wasn't sure if might have something anything to do with my apparent back course issue. Their subscriptions displayed the newest worldwide waypoints on the P3D map...and I thought that it updated frequencies (maybe not?)