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.

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

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.

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)

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

I can't get beyond the 'unclaimed account' stuff. I have no idea what 'discord' is all about or how it works!

Way too many problems with Central4 . Fortunately I keep full image backups , and have returned to Central3. Two weeks wasted on poorly Q/A'd orbx software!