Does anyone have problem with com1 radio? It cannot hold the frequency you enter and always revert to 119.00.
I wonder why the NXi Quick reference Guide says the ILS localizer is captured with the APR key and the NXi manual says it’s captured with the NAV key.
I noticed in the WT Nxi only the NAV key works, the APR key only captures the GP/GS.
Quick Reference guide: http://static.garmin.com/pumac/190-02178-00_B.pdf
Manual: http://static.garmin.com/pumac/190-02177-00_A.pdf
Which one is correct?
For purposes of the sim, the only way you’ll get a GP/GS armed or active indicator on the Scoreboard Annunciator is to use APR.
My understanding is:
Quick Ref says APR captures the Glideslope (GS) for vertical guidance.
Manual says NAV captures a LOC for lateral guidance.
So the AP won’t descend below approach altitude upon intercepting the glideslope unless APR is armed.
@GoFasterS4 Sorry, but the Quick Ref clearly says it captures GPS, VOR and LOC with APR key, which used to be the case before the NXi. If now just the NAV captures the LOC and not the APR as the manual says, I guess it is an error in the Quick Ref Guide.
It would be nice if someone who uses the NXi in real life could chime in to say if they capture the LOC with APR in HDG mode (as it used to be) or just with NAV. But probably no one here uses the device in real life.
I know that, the doubt is about capturing the LOC, not the GP/GS.
You’re right, I missed that part.
I have been using this mod for the last few days. (BTW, no CTDs). I was trying to duplicates Kip’s Albany to Manchester flight from his video mentioned above in this thread. When I activated VNV the AP annunciator would show VPTH in white lettering, but would not turn green when the TOD was reached. I did have the altitude set to 2000 feet when the next target altitude was 3600. I tried a VNAV approach at another airport later and it did work. When VNAV worked, I could look in the Active VNV Profile window of the FPL display and see the time until TOD in minutes. On my Albany to Manchester flight when I was about 15 minutes away from TOD, that display showed 2+15. Any idea what 2+nn means? Also I was unable to Pan the map in the MFD but see that that feature is unimplemented. Thanks for the work Working Title is doing for Flight Simulator.
Is the AI flight assistant set to handle comms / air traffic control? This will always override what you put in.
Thanks for the tip. Not sure which item controls com radio, I just turned off everything in assistance menu and the problem is now gone.
1 Like
Thanks for your post; at least the situation is now clear for me. I think I shall use the classic version of G1000 until the G1000 NXi is implemented.
Ever since 0.2 (on Xbox) and using Autopilot, I get death spirals into the ground out of nowhere after for example returning from Pause Menu oder switcthing something in the cockpit. At first I thought it was my Hotas so I just use the Xbox Controller now but it happened again several times today in various planes with the G1000.
I have therefore de-installed the G1000NXi on my Xbox.
The problem was not present at all when I was using version 0.1
But I cannot go back to that version so I go back to using default G1000.
I will watch if the issue is still going on.
Slight chance it’s just one of the buggy Hotfixes that was introduced. I have no more CTDs on Xbox, but Mouse is losing connection all the time and other oddities since Hotfix 2. So maybe the problem lies there, not sure.
I will see if it is the G1000NXi by trying the Default G1000 in the coming days.
After trying the new 0.3 version, I no longer get CTD during sim loading, but I have had a few CTD while flying in the Caravan. After the first CTD about 4 minutes into the flight (after turning my head - track IR), I tried to re-start. From then on, every time I hit “ready to fly” button, it would immediately crash.
I when this happens, I have to remove and re-install the addon from marketplace and then I can hit “ready to fly” again.
I also tried removing it and flying about a dozen flights without any CTD, as a control.
Do you play on PC too, or just the Box?
They are both correct. Those are two different sections, one is referring to lateral only modes and one is referring to combination (lateral and vertical) modes.
NAV is a lateral mode only. The manual is correctly stating that you will capture a localizer laterally by pressing NAV. If you want to capture the localizer (LOC) and glideslope (GS), then you would press APR. This is how it is implemented on our NXi also.
-Matt | Working Title
3 Likes
Hi Matt,
Why is it that it doesn’t capture the localizer for an ILS approach for me by pressing APR when I’m in heading mode? Only by pressing NAV. If I press APR it captures the GS but not the localizer. The localizer needle moves but it’s not captured. To capture the ILS localizer I need to be in NAV mode.
1 Like
The issues reported on where experienced on the xbox version. Which I did state.
I don’t use MSFS on PC anymore. Too many bugs and problems. I’ll try the PC version again in a year or two.
I also had issues capturing the localizer last I tried. Tried intercepting it twice with HDG+ALT active and pressed APR when on a 40-ish degree intercept angle. Both times it went way past the centerline without turning or activating.
1 Like
I don’t think this feature has been implemented yet.
Re: the localizer (this is the EGPE ILS 5 approach, INS transition):
At first I couldn’t get it to show LOC at all, but that changed when I exited SUSP and changed the CDI to LOC1. However, it shows the localizer as bang-on despite being way offset, and is not turning. It is going down along the glideslope though.
Edit: A while later, it did start turning.
That correction angle is a bit small though, isn’t it?
I took over and landed from here:
Another update. I tried the same approach with the stock G1000. Started at EGVZ, added EGVZ → EGPE and ILS 5 with INS transition manually on the G1000, and took off. Only difference in proceduce is that I hit CDI prior to APR the first time, rather than just the second or third.
I also did not have to enter the ILS frequency manually this time, not sure which G1000 is correct in loading that automatically. (Stock G1000 did, NXi did not.)
Initial capture:
Short final:
