Looking to find a way to create custom procedures for an existing airport, BGTL, because the default airport doesn’t really have the correct procedures
I’ve tried looking around online for guides on how to do this but have so far found nothing of actual value. The scenery.xml file doesn’t make sense to me (Where to put it, what’s the format, etc.?) and I can’t work out how to do this in the project editor
Any advice or even an idea of where to look would be appreciated
This would require a modification to an AIRAC, either the stock or a third party like Navigraph since procedures are stored therein? So that would be outside the SDK 's scope.
BGTL does not exist in the base airport data for the sim, so it does not get any navdata in the base navdata package. If you have a third party scenery for it, you can create a navdata package following the SimpleNavData sample in the MSFS SDK. Make sure to remove the `<DeleteNavigation>`tag though so it doesn’t delete navdata for the rest of the world. The XML must be edited by hand, as there is no GUI editor for navdata (it is usually machine generated from a worldwide database). You should use a PackageOrderHint for your package that is higher priority than the third party airport package, so your navdata is mounted later; CUSTOM_AIRPORT_PATCH is probably the right one.
Note: if you rely on waypoints that are defined in the base sim navdata, you will need to keep your package up-to-date as required every 28 days when new AIRAC cycles occur.
Thank you very much! This’ll help a fair bit
Any idea if there’s a detailed guide on the parameters? For instance, random example, if I want to code the THULE1 departure, which is right after departure DCT JODOM then DCT WENSA and SID terminates at WENSA, where would I be able to find how to program that in?
I found this Scenery Overview for P3D but I’m not fully sure how accurately it applies since it looks like some stuff has changed
There is a small amount of documentation at Approach, Arrival, And Departure XML Properties, and the XML schema is fully documented in C:\MSFS 2024 SDK\Tools\bin\bglcomp.xsd.
The parameters largely follow ARINC424. That standard is sadly not freely available, but there is plenty of secondary information on the internet.
For my own navdata packages, I added the schema to the FSData tag so my editor (VSCode with the XML extension) will validate and provide auto-completion hints, like this:
<FSData version="9.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="file:///C:/MSFS%202024%20SDK/Tools/bin/bglcomp.xsd">