Yes, it should. We should choose vectors in the G1000 when we are being vectored for the approach by ATC. But that is not currently supported by the sim ATC. I use “Vectors” as the approach transition in the GPS if I am “self-vectoring”, a.k.a “moving map pilotage”, not something we would do IRL but a workaround for the lack of ATC vectoring at the moment…
Other than eyeballing the runway (when I can see it) in whatever plane I’m flying, and trying to keep a fixed point on it at the same spot on my windscreen as I descend, where can I look to figure that out?
Can’t capture localizer or GS.
With the G100NXi I’ve never been able to capture the localizer or the GS. I uninstalled it and was able to immediately capture the ILS for a successful approach and landing. Has anyone else had this problem?
Any word from WT on updates? I thought they said they were going to do weekly updates, but it has been quiet for a while. Maybe they are prepping for the next WU.
I’ve had the same issues as well. Strange thing of it is I’ve got a buddy that can capture the same one every time and we’re both doing the same things. I’m going to try and remove the mod tonight to see if the stock G1000 works.
Same problem. Flying into KMDW ILS runway 04.
No ILS capture. The needle finally became active but was pointed the wrong way.
Uninstalled and reinstalled and same problem.
Uninstalled and used stock G1000 and it works again.
I duplicated this at several different airports around chicago.
Found several ILS approaches either not capturing or the ILS was about 90 degrees off. This is with the G100NXi.
For now the bug is nearly constant so I am staying with the stock G1000 until this can be worked out. Unfortunately the stock 1000 doesn’t support the VNV and that is a nice feature of the NX.
I look forward to everything being resolved.
Not all r/w GNS nav systems automatically set the CDI to the published ILS inbound course. This feature is not implemented (yet) on the NXi, but I believe WT said it will be added in an update.
If the CDI is rotated 90 degrees (or any other amount), then just use the course set knob to rotate it to the published inbound course on the approach chart for the particular ILS you are flying. It takes only seconds to do this - there is no reason to abandon the approach just because the CDI isn’t initially pre-set to the correct course.
With a basic OBS/CDI like the one illustrated, it’s really not necessary. The aircraft will track a localizer no matter what the OBS is set to.
But, with a mechanical or digital HSI, it’s important to set the CDI to the published localizer course for situational awareness, so the pilot can see the angular relationship between the aircraft’s current heading and the localizer course.
The hold at WINCH is on the published RNAV 12 plate.
I have lived on the Central Coast for forty years: KSBP and KPRB are “home” airstrips for me. (When I moved here KSBP was still an uncontrolled airport, finally getting a tower in the late eighties.)
Do you know about the little Garmin app called FltPlan Go ? It’s a no cost download for your smart phone and/or tablet. It is used for real world flying, and proves invaluable in the flight sim world too. I use it to check the procedure before I load it in the NXi… no surprises that way. I use VECTORS almost exclusively, especially when flying in CAVOK weather in the daytime.
The NXi is a game changer in the sim, and it is still only “early access.” Amazing! It’ll be even more fun when it is fully functional…
Yes. Can’t wait, but am trying to make do with ILS approaches in the meantime. The problem wit the NXi and ILS now is that the AP drifts ever so slightly off course between the “Faf” and the RWY. Yesterday, I tried an experiment. I flew from Watsonville, our home airport, to Monterey for an ILS approach to RWY 10. On that approach, my G36 drifted to the right. Then I flew an RNAV approach to the same runway.
Unfortunately, I ran into trouble because my Logitech multipanel wouldn’t let me dial in 1,700 ft., the altitude for MINCK, the RWY 10 final approach fix. I had to change the flight level in the AP to give the Garmin “permission” to descend below 2,600 ft., the plate altitude at the initial approach fix, ZEBED. So I paused the flight to mouse-diai 1,700 ft. on the in-sim panel. Or so I’d thought I’d done. (When I did that, the flight level on my Logitech panel also changed to 1,700, so I thought.) I hit APR at ZEBED, and the G36 began descending. Then it kept descending, and descending until I realized I was headed for a horrific crash on the Monterey Peninsula, at least a couple miles short of the runway. I disengaged the AP, pushed the throttle full forward on my Logitech quadrant, retracted my landing gear and flaps, and recovered in time to safely land the plane. When I parked the G36, I zoomed in on the PFD for a closer look at the altitude strip and discovered I’d actually mouse-dialed -1,700 ft. The NXi was just following orders.
Known problem with NXi : after you select the localizer by pressing APR, only the VERTICAL component of the localizer is locked. You must then hit the NAV key once- that will track the LATERAL component in addition, and land you on the runway. This workaround will be fixed in later update of the NXi.
NOTE: Forget everything I said here The new version 0.5.0 was released, (as below). (Version 0.4.0 was never released)
Everyone…until Working Title updates the NXi there is a workaround. Before you take off, Change the PFD CDI from GPS to LOC. Set the LOC and heading bug to your destination runway heading. Switch the CDI back to GPS. Dial in the destination LOC frequency on NAV1. Take off, engage auto pilot. At the initial approach fix, when your plane is lined up with the runway heading, switch the CDI from GPS to LOC; the LOC will be on the runway heading. And very important, immediately after you switch from GPS to LOC, hit NAV on the autopilot, because making that switch turns it off. Good luck and good day.
Interesting glitch, or perhaps I missed something with 0.5.0.
Loaded a GPS Point-to-Point plan in the MS Flight Planner (KBID to KMVY). Cold & Dark from a parking space to Runway 33 on the Vineyard.
After T/O and stabilized heading departing Runway 28, I enabled FD, V/S set to 400 fpm for a slow climb to 4,000’, NAV then AP. GPS TERM in CDI so reception is good. Top Line showed routing KBID->KMVY in Magenta.
GPS kept showing white while other annunciators showed ROL AP in Green. Cycled NAV several times, no dice, I was flying last heading no matter what. CDI showed correct Magenta heading East, but the plane was headed on 280 period.
Decided to override using DTO and selected MVY. Activated, and then the FMS started tracking and turned me around.
I’m guessing planning a Flight direct from the sim might have something to do with this. I’ll try an Imported Plan next from Little Nav Map and see if the error is consistent.
Edit:
I have not actually flown a flight with 0.5.0 yet but if you stay in HDG mode and change bearing to intercept the GPS course; at some point within “capture distance”, GPS should change from armed (white) to active and capture.
I downloaded the update and suddenly, I was not able to adjust the altitude in my Logitech multipanel. When I got to the cockpit–on the runway–the altitude, which should have come up all zeroes in the multipanel, read 99,999 ft. I could not change it one way or the other. Neither could I adjust the altitude in the NXi itself. My multipanel and the NXi were getting along fine today, before I updated the NXi. I did all the stuff a layperson would do in this situation: exited MSFS, restarted my PC, restarted MSFS, no improvement; exited MSFS, uninstalled the Logitech plug-in, restarted my PC, reinstalled the plugin, restarted MSFS, panel was still at 99,999 ft. in the cockpit; escaped the flight, went to the content manager, removed the NXi, exited MSFS, restarted the PC, back to MSFS and the content manager, reinstalled the NXi (latest version), started a new flight, multipanel still locked up at 99,999. Finally said heck with it, removed the NXi and reverted to the stock G1000. Stock G1000 and multipanel resumed their working relationship. What gives? Is this idiosyncratic with my setup (Logitech multipanel plus MSFS) or what?