You may try using the old method using scenery.cfg to activate the database entries in the flightsim; this will help to narrow the problem to the addon.xml method.
Here are the steps:
1) Copy these entries in your scenery.cfg file located on ProgramData folder. Insert them, just after the stock scenery entries, and before any other 3rd party addons.
(replace the path below acc. to your file-system Documents path, and the insertion index, or use Lorby Addon Organizer to insert them
Code: Select all
[Area.136] Title=FSAD_Navaids Local=C:\Users\Jose\Documents\fsAerodata Files\Navigation Data\P3D5\Navaids Layer=136 Active=FALSE Required=FALSE [Area.137] Title=FSAD_Approaches Local=C:\Users\Jose\Documents\fsAerodata Files\Navigation Data\P3D5\P3D\PROC Layer=137 Active=FALSE Required=FALSE [Area.138] Title=FSAD_Comms Local=C:\Users\Jose\Documents\fsAerodata Files\Navigation Data\P3D5\Comms Layer=138 Active=FALSE Required=FALSE
3) Run the FSAD config tool, activate the database, and start the simulator afterward.
To revert to the add-on.xml method, just delete the scenery entries, and the tool will regenerate the add-on next time it runs.