Elevation conflicts with P3D v4.5 Hotfix2 and 3rd party add-ons

[fsaerodata]

The latest Prepar3D version 4.5 Hotfix2 brings design changes that affect the compatibility of fsAerodata and 3rd party airports and global scenery packages (i.e. Orbx Global) that include airports.

The option to update some of the navdata of 3rd party addons (comms, approaches, ILS stations), by bringing the FSAD scenery entries above the other airport entries, is not possible anymore.

To avoid elevation issues on some airports when running 3rd party addons and fsAerodata together, FSAD entries must be set below 3rd party add-ons.

Update Nov, 9th, 2019.
A preliminary workaround has been released that solves elevation and scenery coordinates conflicts with 3rd party airports when having fsAerodata on top of the scenery list. Recommended for advanced users, due to the rather cumbersome procedure and still the possibility it may not work in all setups.
Download link:
https://www.fsaerodata.com/airac/downlo ... s_1.31.zip
Current version: 1.31 - December, 9th, 2020

Procedure to update elevations on fsAerodata BGL file to match those on 3rd part airports:
1. Disable the fsAerodata(FSAD) database ((press the DISABLE button)
2. Copy to Prepar3D main folder, the exe files supplied on this zip distribution, including the files inside MakeRwys.zip. Don't forget to provide administrator permission to the executable files.
3. Run MakeRwys.exe and let generate the list of addons runways.
4. Enable the FSAD database.
5. Open Windows Explorer and go to the directory where the fsAerodata Comms bgl file is stored:
[Your Documents Folder]\fsAerodata Files\Navigation Data\Comms\scenery
6. Drag the bgl file to AdjustElevation.exe
7. After the tool has finished scanning the airports and tweak the elevations, run Prepar3D and check out the results

You can now move the fsAerodata scenery entries to a higher priority than other 3rd party airports.

Bear in mind, steps 4-7 needs to be run every time there is a new cycle; the complete procedure to be followed after a new scenery package that contains several airports (like Orbx Global) is installed, or you observe elevation conflicts.


Update for users of Prepar3D V5

Steps to follow:
1- Enable the FSAD database on P3Dv5 (press the ENABLE button)
2- Run the Lorby Addon Organizer tool, positioning the three FSAD entries on top; deactivate temporarily the fsAerodata add-on package.
3- Run Makerwys, so it generates a global list of airports.
4- Run the AdjustElevation tool (check for latest version 1.3 compatible with Prepar3D v5)
5- Activate again the FSAerodata add-on package on Lorby tool and run the flight simulator.
These steps must be repeated on every cycle; step 3 can be skipped if there are no changes in the list of 3rd party airports.

[QuaxAero]

Could this tool be enhanced to give a csv list with ICAO-Code and altitude ?
As it doesn't work in my case for addon airports outside the sim folder and I know my addon airports and I can get their altitude from makerwys,
I would create a .txt file, say:
XXXX,1500
XXXY,50
XXXZ,100
and give it to your tool, say by an additional parameter "-l <listname>" and your tool has to process only this airports with the altitude directly read from this list in my .txt file.
I would have to update this list only in the case of an addon airport update.
The tool would run much faster and more experienced simmers would have complete control over the process .

[fsaerodata]

A new version is available that fixes a bug where many airports were unintentionally not scanned and adjusted.
Additionally, an option has been included to allow scanning a custom list of airports and altitudes.

See download link on the first post.

Best Regards,

[jalbino59]

The process does not say if we supposed to re-enable the FSAD DB after following the steps above?

[simba]

Following the steps described, I re-enabled all of the FSAD DBs and put them on top of all of my sceneries.

Regards Roland

[Mischa]

If running a PC with a non US localization be aware that you have to look at your decimal separator and thousands separator. I tried the update several times with my local German configuration and always run into problems with the altitude.

After switching to the US decimal separator "." and thousands separator "," before applying new cycle everything went fine. After the update of the FSAD DB you can switch back to your standard configuration.

Regards,
Michael

[tdumontelle]

I ran through this fix procedure. It did not fix the runway and parking misalignment problems.

[fsaerodata]

I ran through this fix procedure. It did not fix the runway and parking misalignment problems.

Did you run the .exe file under Administrative rights?
This workaround may not work in all systems. In that case, please move the FSAD scenery entries below the 3rd party scenery addons.

[tdumontelle]

I ran through this fix procedure. It did not fix the runway and parking misalignment problems.

Did you run the .exe file under Administrative rights?
This workaround may not work in all systems. In that case, please move the FSAD scenery entries below the 3rd party scenery addons.

I did run it as administrator. Before the fix if I had the comms checked I would have the scenery errors regardless of placement of the files in the scenery layers. After the fix, I can use my comms, but I still can't check either of the approaches scenery entries without the same airport parking errors. So for me, I got the comms improvements back, but still don't have whatever is in the approaches files (assuming these are the landing files that go with approaches on the GPS). Oddly I haven't seen elevation errors anywhere that I've flown yet under any of the setups, but I do stick to a limited number of airports.

Hopefully the installer will be fixed soon.

[karelpatch]

Hello,
This didn't fix it for my ORBX EGJA Alderney scenery. Does it have something to do with the fact the scenery is an add-on? Makerunways is only looking at the sim root directory right?
Thanks!


EDIT: ok it's using LorbySceneryExport so addon sceneries are detected. I don't know why it's not working then