noted Upgrading Orbx Airports for the new G1000 NXi

[Eclex]

The KVNY airport from Orbx does not include the ILS runway (16R) frequency (111.3) in its navigation data. By installation, its own data will over-ride the default (or even Navigraph) data, thereby rendering a missing component to the selected GPS system.  The new WT G1000 NXi  GPS in MSFS is capable of vertical-mode RNAV (area navigation with vertical tracking all the way to the runway) . It can, if ILS is chosen, use an approach mode using the ILS localizer (wherein it switches to the localizer at the close approach to the runway. In the Orbx KVNY (Van Nuys) code included with your product, the ILS frequency is missing. Thereby, the automated descent into the runway ends just where the ILS should engage (automatically) with the new G1000 instrument. I sugget that Each of the Orbx airports should be upgraded to include the nav data required to use the new MSFS GPS systems. Within just a few months from now these will include the G1000 (NXi), G3000 , and perhaps others. 

 

Dave

[Nick Cooper]

Hello,

I may have misunderstood but Little Nav Map does not seem to agree with your assessment.

 

[Eclex]

I don't see the  16R localizer frequency displayed.  The point of my topic is its omission in the Orbx version datum. Thereby, the GPS generated approach flight plan cannot include it. (I am not familiar with the little Nav Map or where it gets its information)

 

Edited September 28, 2021 by Eclex

[Eclex]

Little nav Map gets its information from sources outside of MSFS. The GPS units get their info from within MSFS. Airport info comes from either the default nav data, addon nav data such as the Navigraph addon mod, or, in the case of addon airports (highest priority) it uses nav info from the addon file itself. Orbx KVNY is such an addon file, and it lacks the ILS frequency. 

Edited September 28, 2021 by Eclex

[John Burgess]

11 minutes ago, Eclex said:

Little nav Map gets its information from sources outside of MSFS

 

Thanks Dave, that's interesting. I use LNM to try and see what's in the scenery and sometimes see doubles - especially ILS feathers.

 

Just checked at KVNY and the ILS doesn't appear in the Daher MFD so that seems to confirm what you are saying.

 

Living and learning. It is now one of the things I make sure to test.

 

All the best,

 

John

[Sniper31]

1 hour ago, Eclex said:

Little nav Map gets its information from sources outside of MSFS. The GPS units get their info from within MSFS. Airport info comes from either the default nav data, addon nav data such as the Navigraph addon mod, or, in the case of addon airports (highest priority) it uses nav info from the addon file itself. Orbx KVNY is such an addon file, and it lacks the ILS frequency. 

 

1 hour ago, John Burgess said:

 

Thanks Dave, that's interesting. I use LNM to try and see what's in the scenery and sometimes see doubles - especially ILS feathers.

 

Just checked at KVNY and the ILS doesn't appear in the Daher MFD so that seems to confirm what you are saying.

 

Living and learning. It is now one of the things I make sure to test.

 

All the best,

 

John

Actually, Little Nav Map CAN get it's info from MSFS by building a database from MSFS data to include airport info and runway info. If you go to the LNM website, there is an online manual with instructions on how do this as well as how to use all of LNM's features. I rebuild my LNM database about once a month as I add new scenery airports. All the info is then there.

 

Landon

[Nick Cooper]

2 hours ago, Eclex said:

Little nav Map gets its information from sources outside of MSFS.

 

Hello,

while I will leave the discussion of the niceties of the new WT G1000 NXi  GPS in MSFS to others, Little NavMap has proved to be a thoroughly reliable way of checking what data is included in any of the six simulators with which it works.

It can be set to use other databases or it can be set to use only the simulator data and it then tells the user from which simulator files the data is drawn.

 

This is how it looks with all the available Navigraph data added but no simulator database for any simulator.

 

and this is how it looks with data drawn from Microsoft Flight Simulator only.

 

 

Just for your information.

I am sure that John will work with you to solve the problem that seems to have appeared with the new WT G1000 NXi GPS in MSFS. 

[John Burgess]

25 minutes ago, Sniper31 said:

Actually, Little Nav Map CAN get it's info from MSFS by building a database from MSFS data to include airport info and runway info.

 

I must admit I tend to do that more often than most but still interested to try and find why, sometimes, I get double data. ILS's are a particular area. It's not just LNM. We've found more than once when testing we see different things - a rebuild of the content.xml file can be the difference between seeing the default ILS and the one in the scenery when actually flying in the sim.

 

As Nick says, LNM is a great utility!

 

All the best,

 

John

[Eclex]

Keeping the thread on topic,  here is a simple demonstration of the problem. Let's use the TBM GPS as our test bed. With the Orbx KVNY airport installed and the TBM aircraft sitting on the VNY runway, activate the MFD screen and select NEAREST>airports. Press KVNY and select FREQUENCIES. Use the up/down buttons to scroll through all listed frequencies. No ILS frequency will appear. Next go back to the Nearest>airports page and select the Bob Hope airport. Again select frequencies and you will be able to select its own ILS frequency. Clicking on it affords one an opportunity to make it the active localizer radio freq. In this sense, the GPS "knows" the ILS frequency. The G3000 cannot "know" the Orbx KVNY ILS because it wasn't inserted into the downloaded user installation. The G1000 and G3000 will both be upgraded in the months to come to become the MSFS DEFAULT units, and they need to have ILS frequencies installed into the addon airports correctly to work in the new VNAV capable GPS installations. I hope I've clarified my original post.  Thanks

 

Dave

 

[John Burgess]

8 hours ago, Eclex said:

I hope I've clarified my original post.  Thanks

 

Thanks Dave.

 

I did mention in my original response that I had actually gone back to KVNY just to double check the point about autotune in the Daher MFD and confirm it was not there since I suspected that this was another example of that same issue.

 

At the moment, as you know all too well, manually tuning the ILS frequency is the only option.

I'm not for a minute suggesting this is the way it should be but do you know if that work round is effective in the approach mode you are mentioning?

 

I'll certainly raise this again.

 

All the best,

 

John

 

 

[Eclex]

Yes John, the pilot may update the nav freq manually and change the CDI manually to force ILS tracking . I am trying to learn the operation of the (beta) G1000 NXi, which, indeed, provides for complete autosequencing into localizer glideslope control without pilot intervention. That's where i ran into the Orbx airport missing data. The default version of the KVNY works just fine with the NXi gps.  All of the improvements developed for the G1000 NXi will be built into the G3000 later on. The new code is being done by the Working Title team hired by Asobo.  

[John Burgess]

18 minutes ago, Eclex said:

Yes John, the pilot may update the nav freq manually and change the CDI manually to force ILS tracking .

 

Thanks for confirming that Dave. I've raised the issue on our private forums but no promises. It's an issue I would definitely like to see working properly.

 

All the best,

 

John