Yeah it works as you say but I have to manually switch from GPS mode, it wont auto switch the CDI. I will give KDCA a go too and see what happens, probably tomorrow now as its getting late here now. Thanks for your help though.
1 Like
I’m having an issue with the label for Nav2 on the PFD (current version). Using the CDI softkey, when I cycle to Nav2 (with a localizer freq on Nav 1 and a VOR on Nav 2), I correctly get the double needle, cyan box around the Nav2 standby freq and the active freq highlights (per page 57 in the Cessna NavIII NXi Pilot’s Guide) BUT the label near the deviation bar stays at “LOC 1” on an ILS. It displays correctly on the default G1000 (after uninstalling the NXi and rebooting). Reinstalling the NXi and rebooting doesn’t fix the issue.
At 10 miles out I armed the localizer and it lock right in I then armed APR and when the I crossed the ball it locked right in.
So was the problem that it did not come out of GPS on it’s own and arm the LOC??
1 Like
Yes, that is exactly what happened, it didn’t switch when I tried it last night manually re-tuning Nav 1 & 2. if the correct localiser frequency is in the flight plan, the G1000 will switch from GPS to Loc1 automatically and lock on too. This cannot happen at EGGP when the plan is loaded from the MSFS map view because the wrong localiser frequency is loaded into the G1000 flight plan. Manually re-tuning Nav1 and 2 doesnt affect the freq in the plan hence the difficulties I have been having. I am going to see later today if I can manualy alter the localiser freq that is loaded into the flight plan on the G1000 but ideally we need Asdobo to sort the airport out and correct their silly error.
I’m assuming you aren’t using Navigraph navdata? It should be 111.75.
I was half expecting this to break it, but when I configured LNM to not use Navigraph for any features, the frequency remained as 111.75. From what you had said I was expected the Asobo data to be different.
No I am not using Navigraph. I am very much at the beginning of learning all about IFR and ILS.
The sim knows that 111.75 is correct, it shows that frequency on the navaids in the flight planning map within the sim, but when you create the IFR flight the sim sets Nav 1 & 2 to the incorrect frequency of 110.50 so the flight plan in the G1000 is also listing 110.50 as the correct frequency, which is of course incorrect.
I was hoping I could just manually adjust that frequency within the plan in the G1000 from 110.50 to 111.75 but I cannot see a way to do that.
If you just want to learn, why not just try an ILS at a different airport?
I have succesfully flown ILS approaches at other airports but that is when the automation works reliably. That’s not really going to help me though when I want to fly to EGGP or any other airport where the Nav frequencies are wrong in the sim. Understanding why it didn’t work at this one airport and how to work around it is, I think, an important part of learning how to use the system.
Its not enough when learning something like the G1000 just to copy what other people say you should do, I need to understand why I am doing something to truly learn.
What I have learnt today though is that if the flight plan in the G1000 doesnt show a valid frequency for the approach, its likely that:-
- The sims navigation database has an error.
- The G1000 will not switch from GPS to Loc1 automatically on approach.
- The Nav1 & Nav 2 frequencies will need to be manually retuned to the correct frequencies.
- The CDI Softkey will need to be used to switch from GPS to Loc1.
I just had a flip through the various charts for EGGP, and that frequency is not in use anywhere at that airport, as far as I can see.
Can you quote which approach you had loaded please?
A small problem here with the NXi: the timer starts in the small window, but remains at 00:00.00 in the main screen.
1 Like
Sure. The flight plan is from EGCC to EGGP using approach ILS 27 via LPL. Load that up in the map and you will find that the sim sets Nav 1 & 2 to 110.50 LUK.
You are correct. If you choose Low Altitude Airways you will get assigned a bogus NAV radio Freq.
But you could manually change it to the correct one. report the bug in the sims NAV database.
Problems not with the g1000 if it was entering the right freq would not work.
2 Likes
You should always verify your ILS frequency with the airport chart anyway as part of your normal procedure. That way you can just correct it if it’s wrong/
3 Likes
No one noticed that the NXi doesn’t work in any aircraft? You can’t adjust altitude, Nav button doesn’t work. GPS course not displayed on right MFD.
No issues before this latest update!
Seeems to be working fine for me/…Baron, Daher and more that I’ve tried so far…Give it the usual recommended treatment. Full shut down and restart seems to fix it for most.
2 Likes
Make sure old G1000 mod is not still installed in Community Folder.
No problems with the NXi for me either.
Please remove the previous NXi patch (zWTnxi-0.10.1-distance-fix) package provided by PMS in your community folder. As mentioned by PMS when the patch was released, you are to remove this patch when the next NXi version is released (which is this current version). There is a new patch available from them for this latest NXi version.
Do note, however, that we do not officially support this patch. PMS are great folks, it’s nothing at all against them, and we love what they’ve done. But, it does cause these kinds of support issues where folks get upset that things are broken, when they’re actually using unsupported and outdated patches. So, use these at your discretion and please follow the provider’s instructions on usage.
5 Likes
@Bishop398 You have my profound sympathy when this kind of thing happens. And it is not just this mod: I find it especially sad when people are highly critical out of the gate when “reporting an issue” in the game in general that turns out to be user error or self inflicted. Instead of reasonably checking their own setup or politely asking, for some people the first response seems to be criticism (sometimes scathing) and “it is not working” .
I DO understand that the sim/game has its problems for some people and I understand some frustration. All I am wishing for is a bit of moderation when first writing about a perceived issue.
3 Likes
Yes, till I have the chance to test I’m assuming that this is an issue with AIRAC 2203 that they included, and if you use Navigraph you won’t have this issue. It’s not the NXi doing this, I expect.
@anon69344611 Try it in a 530 equipped plane, and I’ll bet you have the same issue.