• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS20 How add a ILS or any NAV to airport?

Thanks - I found that the console window has a lot of erroneous entries in it - but perhaps that is cleared up now?
Not as far as I can see, I use the package tool with -rebuild and then XCOPY to dump it in my community folder. ( you still need to restart the sim though)
 
Ah - OK the odd output comes for me from building the package using the in sim tools. If I use the package tool then I get a clean output.
 
I’ll need to look at the packaging tool again. I used it in the first week, but since then I’ve just used the tool in the sim.
 
This is what I use (you obviously need to update the paths)
Note %MSFS_SDK% should be defined as an environment var by the SDK installer
(also cant believe DOS isn't a code formatting option lol)

Code:
SET FS_TOOL_PATH="%MSFS_SDK%Tools\bin\fspackagetool.exe"
SET PROJECT_XML_PATH="D:\Users\truan\Documents\MyFSProjects\th_eghc_landsend\eghc.xml"
SET PACKAGE_OUTPUT_SOURCE_PATH="D:\Users\truan\Documents\MyFSProjects\th_eghc_landsend\Packages\th-airport-eghc-landsend\*"
SET PACKAGE_OUTPUT_DEST_PATH="D:\MicrosoftFlightSimPackages\Community\th-airport-eghc-landsend\"

%FS_TOOL_PATH% %PROJECT_XML_PATH% -rebuild

RMDIR /S /Q %PACKAGE_OUTPUT_DEST_PATH%

XCOPY /E /R %PACKAGE_OUTPUT_SOURCE_PATH%  %PACKAGE_OUTPUT_DEST_PATH%
 
This is what I use (you obviously need to update the paths)
Note %MSFS_SDK% should be defined as an environment var by the SDK installer
(also cant believe DOS isn't a code formatting option lol)

Code:
SET FS_TOOL_PATH="%MSFS_SDK%Tools\bin\fspackagetool.exe"
SET PROJECT_XML_PATH="D:\Users\truan\Documents\MyFSProjects\th_eghc_landsend\eghc.xml"
SET PACKAGE_OUTPUT_SOURCE_PATH="D:\Users\truan\Documents\MyFSProjects\th_eghc_landsend\Packages\th-airport-eghc-landsend\*"
SET PACKAGE_OUTPUT_DEST_PATH="D:\MicrosoftFlightSimPackages\Community\th-airport-eghc-landsend\"

%FS_TOOL_PATH% %PROJECT_XML_PATH% -rebuild

RMDIR /S /Q %PACKAGE_OUTPUT_DEST_PATH%

XCOPY /E /R %PACKAGE_OUTPUT_SOURCE_PATH%  %PACKAGE_OUTPUT_DEST_PATH%

What is the practical effect of using -rebuild. The SDK documentation says: Force redoing all file conversions.
 
What is the practical effect of using -rebuild. The SDK documentation says: Force redoing all file conversions.
It looks like the package builder supports incremental builds, so if it doesn't think the source file has changed it wont rebuild that component.
The downside is it will take longer, the upside is you get a 'clean' build.
During a normal dev cycle you might want to skip it to get quicker builds, but when doing a build for a 'release' I would always use a forced rebuild.
The time difference for me on a tiny project are negligible.
 
Thanks - I have tried with and without and don't see much difference with a small airport - it's slooow
 
Thanks - I have tried with and without and don't see much difference with a small airport - it's slooow
So, at the end of the fspackagetool output there is a time elapsed - for me without -rebuild its 14ms with it is 100ms.
The problem is it take 30-45 seconds to spin up the app to run the package build.
 
Yep - that is the slow bit. So the difference in build methods is trivial compared to the load up time
 
Yep - that is the slow bit. So the difference in build methods is trivial compared to the load up time
Yeah. I guess if you have a mahoosive project it might be a noticeable difference between -rebuild and not, but until there is a difference I would rather force -rebuild just to be sure it's 'clean'
 
OK, I have successfully added an ILS and NDBDME to my LFOT project. I did this by using ADE for FSX and extracting various bits of the XML airport file. I now need to add the RNAV02 approach which is not present in FSX but is IRL. Is the best way to add the approach in FSX with ADE approach mode and then extract the same bits as ILS? or is there another way?
Cheers
 
Does anyone know what the lat and lon refer to in the <Ils>? is that the beginning of the runway or where the ils antennas should be?


--EDIT:
After a bit of searching in the sample/simpleNavData i found that the lat lon is probably where the ils antennas should be so at the end of the runway.
 
Last edited:
Hi, I've tried to understand the thread but I'm totally new designing airports and I'm not sure where, exactly, should I add those lines. Is it in the XML file that I get when I save a scenery ingame?
 
Hi, I've tried to understand the thread but I'm totally new designing airports and I'm not sure where, exactly, should I add those lines. Is it in the XML file that I get when I save a scenery ingame?
Yep exactly if you open it you can see your <airport> tag
 
Back
Top