Anyone else noticed that the latest patch has removed from their SDK created / modified airport the following items (If you added them)?
- Approaches
- ATC
- Waypoints
- ILS and Glidescope
I have tried opening the project in the SDK and re-building but whilst the items appear in the XML and build correctly they do not ‘render’ when the package is re-copied to the Community folder and re-starting the Sim.
I’m prepared to accept it’s me and how I created the the items in my package but it worked prior to the patch and uses the same detail as the NavData example provided in the SDK.
Perhaps the SDK will need to be updated as well to match the latest patch?
Seems I have possibly found the issue.
When creating the original package I placed the ATC and ILS entries immediately after the AIRPORT statement. On subsequent builds (pre latest patch) the compiler moved the ATC and ILS entries to the end of the xml inside the Airport bracket. The latest patch ignores that positioning. Since rebuilding with the statements back directly under the AIRPORT statement everything is working again.
At the moment I cannot confirm that the statements are moved again to the end (more time required)
1 Like
Hey, i’ve not quite seen the same issue, as my ATC frequencies are still there for all my airports (despite it being at the end of the code as you described, just before the delete code). However instead i have got a different error, with additional frequencies showing up - which i believe are the default ones which are no longer being deleted?
When re-saving existing projects after making the change and pushing the ATC frequencies back up to the top, they are once again thrown to the bottom of the list as well…
I feel it’s the airport delete functions which are messed up for this somehow.
It seems that I have the same problem. Can’t get rid of the default frequencies and replace them with the correct ones. The deleteAllFrequencies=“TRUE” and I have tried having the Com definitions in both places, neither one works. I do think it used to work before the patch, but now th frequencies are screwed up…
Heading of to Zendesk now…
EDIT: Reported!
Hi there. I tried all kinds of ways to get mine working again by moving the statements up under AIRPORT etc and they all failed. What I did not mention in my “solution” post was that the package that now works is not exactly the same
- I created a new package with just the Airport , Polygon (because of its GUID) and runway
- Saved and built
- Re-edited and copy pasted all the original package XML except the COMS and ILS
- Saved and built
- Then added the COMS and ILS under AIRPORT
- Saved and built
What I then noticed was I inadvertently named the package airport-ymoa-oatlands meaning this package starts with airport
Well this built and works in MSFS. I have subsequently edited and rebuilt the package with minor fiddles and it’s still ok. Strangely the COMS and ILS code hasn’t moved.
Any attempt to get the old package working fails. Even copying the new package created with the new SDK and latest MSFS patch and trying to rename to say… oatlands-airport-ymoa (which was the original name) fails. If I rename it back to start with airport- it works!!!
Go figure… I originally logged with Zendesk too
Anyway give the steps above a go.
2 Likes
Hello,
I’m in the process of releasing a bunch of airports I’ve made and am trying to figure out how to add radio frequencies, mainly unicom frequencies, since the airports are very small. Now I found what to add to the .xml file to add and name frequencies, the problem I have though is, that I’m not sure how to include the corresponding lines into the .xml file or where. I’ve tried a little bit around, but whenever I load the package in the developer mode to re-package it with the changes to .xml file, it crashes back to desktop.
Can anyone help me with an example where and with what syntax I need to add the frequencies lines to the .xml file?
Hi. There’s an example in the SDK called simplenavdata
Sorry hit reply too soon… the example shows where to place the com statements directly after the Airport statement. If previous compiles has moved it somewhere else, you must move it back to under Airport again to re-build. You can edit the xml file after you load the project from the inspector. Just don’t click save scenery in the editor otherwise it will clobber your xml changes. Just save the xml only then build the package.
Hope this helps
1 Like
ohhhhh ok, sorry i read your earlier message, just re-named my whole fileset under airport- and it wasn’t working still…
So just to get this straight, you renamed the file set airport-
(for all the original files, or just the build file name?)
Then you edit the xml with the changes, save the XML but do not save the loaded XML before building the project?
Edit:
Arrrgghhhh still can’t get it working to delete the old frequencies 
I’ve renamed everything under the system as you explained, but it’s still bugged out with the old frequencies there! The com frequencies are at the top in the xml i used to save it as you said.
Hi. I think you’re misunderstanding me. I renamed my old folder to _old. Just the root folder so it wasn’t clobbered.
I then created a new folder for a new project.
Created a new project in SDK and made sure in the Inspector it was named airport-code-airportname (replace code and airportplace with yours)
Then placed the airport, polygon and basic runway.
Save and build
You should have a new package in your folder named airport-code-airportname and poly files and a new xml
Exit MSFS
Remove old package from MSFS and replace with your new one
Edit your new XML and copy into it everything from your old saved project XML (it’s in the directory with the poly files) except the comms stuff
Save the XML
Start MSFS
Goto your new airport and go to Dev Mode
Load project
You should see everything
Save scenery
Build
You should now have a complete new airport based on the original called airport-code-airportname
Test in MSFS and it should work. When you’re happy…
Now try editing the project and adding your comms as before
Sorry to be brief but holiday here today and sun is shining and in this town we’re allowed to go 25km in any direction!
1 Like
Thanks. That worked out perfectly!
