thanks very much, I'll take a look
-
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?
- Thread starter Fernando Angel G
- Start date
- Messages
- 13
- Country
Sorry for bumping an old thread, but I really feel this is the right place to ask.
I have tried to add two VOR and one NDB to an airport according to old charts. I wonder if there is some known compatibility issues, maybe with the Navigraph navdata or so, because I can not get them, the ILS or the ATC frequencies to show in sim. I have tried to put them in different prio orders regarding where in the xml the navdata has been added and so on with no positive result.
What is really bothering me is the silent fail, because the compiler does not show any errors for the compilation itself.
I have tried to add two VOR and one NDB to an airport according to old charts. I wonder if there is some known compatibility issues, maybe with the Navigraph navdata or so, because I can not get them, the ILS or the ATC frequencies to show in sim. I have tried to put them in different prio orders regarding where in the xml the navdata has been added and so on with no positive result.
What is really bothering me is the silent fail, because the compiler does not show any errors for the compilation itself.
- Messages
- 13
- Country
Seem to have been Navigraphs nav database that caused the issues for me, I have reverted to the default from NAVBLUE.
I am trying to add runways and navaids at the site of an abandoned airstrip in northern Canada called Sawmill Bay. During WWII, it was used to airlift uranium ore from a nearby mine to the US for the Manhatten Project, and after the war a hunting and fishing lodge operated at the site for a few years. The partially overgrown runways can still be seen on Google Earth. I'm using this site because there are no existing airport facilities in the Sim from Asobo. This is the code for the ILS I have added to the airport XML file:
<Ils lat="65.72634245423480" lon="-118.98274298204365" alt="200.09637440834194" end="PRIMARY" range="50000.00000000000000" ident="ILB" magvar="342.100006" heading="265.22586059570312" frequency="111.25000000000000" name="RUNWAY 26 ILS" backCourse="FALSE">
<Dme lat="65.72219383115167" lon="-118.94359359377253" alt="200.41780705284327" range="50000.00000000000000"/>
<GlideSlope lat="65.72219336190740" lon="-118.94359557995112" alt="199.99912158772349" pitch="3.000000" range="30000.00000000000000"/>
</Ils>
The VOR Localizer, DME, and glideslope instruments in the aircraft (CubCrafters NX Cub) respond as they should, so the heading, range, and magvar values seem to be correct, and the lat/long and altitude positions for the localizer, DME, and Glideslope antennae are in the usual positions, based on where you would expect to find them in a real-world airport. My problem is that the VOR1 NAV function won't lock on to either the localizer or the glide slope. I've tried cutting everything else out of my Community folder except this one airport, and that didn't cure the problem. When I fly to Yellowknife, the nearest Asobo airport with an ILS, it works perfectly. I've seen some threads suggesting that I block Navigraph, but when I tried to follow the directions, I couldn't find the specific things the instructions said to block, so I don't think I have Navigraph installed. My airport compiles in the SDK with no errors, and I have run out of ideas to try and fix this. Does anyone see an error in the code for this ILS that I'm not seeing? Thanks in advance for any helpful suggestions.
<Ils lat="65.72634245423480" lon="-118.98274298204365" alt="200.09637440834194" end="PRIMARY" range="50000.00000000000000" ident="ILB" magvar="342.100006" heading="265.22586059570312" frequency="111.25000000000000" name="RUNWAY 26 ILS" backCourse="FALSE">
<Dme lat="65.72219383115167" lon="-118.94359359377253" alt="200.41780705284327" range="50000.00000000000000"/>
<GlideSlope lat="65.72219336190740" lon="-118.94359557995112" alt="199.99912158772349" pitch="3.000000" range="30000.00000000000000"/>
</Ils>
The VOR Localizer, DME, and glideslope instruments in the aircraft (CubCrafters NX Cub) respond as they should, so the heading, range, and magvar values seem to be correct, and the lat/long and altitude positions for the localizer, DME, and Glideslope antennae are in the usual positions, based on where you would expect to find them in a real-world airport. My problem is that the VOR1 NAV function won't lock on to either the localizer or the glide slope. I've tried cutting everything else out of my Community folder except this one airport, and that didn't cure the problem. When I fly to Yellowknife, the nearest Asobo airport with an ILS, it works perfectly. I've seen some threads suggesting that I block Navigraph, but when I tried to follow the directions, I couldn't find the specific things the instructions said to block, so I don't think I have Navigraph installed. My airport compiles in the SDK with no errors, and I have run out of ideas to try and fix this. Does anyone see an error in the code for this ILS that I'm not seeing? Thanks in advance for any helpful suggestions.
For the ILS 26, the DME/GP position looks fine but the ILS/LOC position seems very far from the threshold 08 although you don't mention its position. Also set the magvar to "0". Check that in the "deleteAirport" and "deleteNavigation" that the "deleteAllILSs" is set to TRUE even if there is no ILS there.
Best regards.
Best regards.