So, even though the convenience of using the GTN750 or 650 to "auto-tune" frequencies is a plus, one would be wise to verify that they are - in fact - the correct ones for the sim! :He He:

 

Otherwise go there and update FSX/P3D database first:

 

http://www.aero.sors.fr/navaids3.html

 

Dirk.

Well, yes. In fact you can display either V or J airways on the map. One thing to keep in mind though is that the database provided is much more 'up to date' than either FSX or P3Dv2 for that matter, so it's not unusual to find that certain COM and NAV frequencies aren't going to match up with what they provide.

 

I got caught on this very issue when getting acquainted with their operations. I couldn't figure out why KGYY's ILS30 localizer and glideslope were INOP totally...

 

...until it occurred to me to double-check the actual frequency tuned. It was then that I discovered that sometime after FSX/P3D database was compiled, the frequency for ILS30 had been changed. Once I manually tuned what the sim expected, everything began working as designed.

 

So, even though the convenience of using the GTN750 or 650 to "auto-tune" frequencies is a plus, one would be wise to verify that they are - in fact - the correct ones for the sim! :He He:

Thanks, Bill. The disappearance of the dreaded knob and inclusion of airways are the two biggest selling points for me. The airway insertion demo on Aero-TV for the GTN was a big wow, in addition to all the eye candy and data.  

 

I've dealt with the outdated database issue quite a bit. When I was first getting serious with FSX, I was practicing ILSs in low visibility, 2012 charts dutifully in hand, flying into 2008 KBFI with my Duke Turbine. The ILS deviation needle would not center, even though the GPS was indicating I was in the feathered capture zone. Vertical situation indicator was missing completely – yet there was a radio beacon out there somewhere. Suddenly through the fog I saw tree tops and rooftops just below me. Distracted by the absentee ILS, I lost track of altitude and terrain. As it turned out, the frequencies had changed, and I was tuning a VOR 30 miles away in Canada! LOL. Had some issues in the NGX as well since it auto-suggests the up to date frequencies, but nothing quite that terrifying. Now I usually check the FSX map function for NAV frequencies, and cheat with the ~ key to find out COM frequencies. (I justify it by telling myself “~” is the name of my co-pilot). 

Correct, and at this point, only Milviz and A2A have given any indication that they are going to work on this..

Just an FYI, we've also joined the party for the F1 GTN integrations for both FSX and P3DV2 with our recently released Liberty Aerospace XL2 3.0.

More as we proceed on the GA Line.. B)

Otherwise go there and update FSX/P3D database first:

 

http://www.aero.sors.fr/navaids3.html

 

Dirk.

Dirk, I've been aware of that for years and have even tried it out. While it does indeed fix most of the en-route navaids, it falls short by not updating all airport facilities. Even if it did, there remains the problem of new and/or reconfigured airports, where the new localizer will politely bring you down to land on the grass, since the 'physical' runway(s) haven't been similarly located and/or re-located...

 

Unless L-M decides to create a new and updatable unified database for Prepar3D in some future version, we'll continue to have this legacy of discontinuity. :ph34r:

Try installing the trainer - and experiment a little..

You can't run the 750 or 650 without the Garmin GTN 750/650 trainer because I estimate that 95% of the code for the product comes from the trainer.

 

Look at the size of the code we download/install from Flight 1's GTN 750/650, I think basically all they're doing is grabbing some hooks like FSUIPC Does with FSX and P3d, and riding that minimal coding for maximum FSX/P3D GTN 750/650 Garmining.

 

That said, do I think it's a great product for us?

 

Yup!

 

But how do you switch the "Com Freq / Psh Nav >" button at the bottom right of both the GTN 750/650??... doesn't work for me...stays in and tunes the COM mode… I must be missing something … Will someone please show me the error of my ways?

 

Chas

Click on the center of the knob using the mouse wheel "button."

Thank you sir !

 

Is that documented?

 

Regards,

 

Chas

Yes, but one does need to look at the manuals to find it... :Just Kidding:

Yes, but one does need to look at the manuals to find it... :Just Kidding:

Did...

 

Yer haluicifyin . ...manual"S" ?

 

 

...read...IT...NADA.......wheel click works fine...thanks, Padre!

 

...course...you got the in track on the gospel...no fair!

anyone have this thing working in the vc of payware planes yet?

Why yes we do.. Liberty Aerospace XL2. B)

Dirk, I've been aware of that for years and have even tried it out. While it does indeed fix most of the en-route navaids, it falls short by not updating all airport facilities. Even if it did, there remains the problem of new and/or reconfigured airports, where the new localizer will politely bring you down to land on the grass, since the 'physical' runway(s) haven't been similarly located and/or re-located...

 

Unless L-M decides to create a new and updatable unified database for Prepar3D in some future version, we'll continue to have this legacy of discontinuity. :ph34r:

 

Ah ok, I update my airport facilities on a case to case basis (even some add-on airports badly need it already) with ADE and/or AFX, those I fly to/from. So it's also quite doable no rocket sience, just needs time that is pricey.

 

Dirk.

anyone have this thing working in the vc of payware planes yet?

 

Carenado C182Q works nicely with a 750,  Carenado Bonanzas work with a 650, Carenado Baron 2X650..

 

 it falls short by not updating all airport facilities. Even if it did, there remains the problem of new and/or reconfigured airports, where the new localizer will politely bring you down to land on the grass, since the 'physical' runway(s) haven't been similarly located and/or re-located...

Unless L-M decides to create a new and updatable unified database for Prepar3D in some future version, we'll continue to have this legacy of discontinuity.  :ph34r:

 

In regions where ILS are updated by the project (Europe area), it doesn't happen considering ILS data are corrected for sim runway position (the way it is done is explained in FAQ 15) so there is no chance you land on grass unless it is a grass runway ;-)

http://aerosors.freeforums.net/thread/5/faq-answers-related-navaid-updates

For other regions (those where ILS were left untouched), nothing is updated at all (except VORs and most NDBs) so you'll get the default sim configuration. Of course, I agree a new and updatable worldwide database would be the ideal solution but I'm not so optimistic regarding that considering the information is disseminated in numerous files      

Herve, if L-M could rip out or disable the existing system, and create a unified database that would be the ideal situation... :Big Grin: