If you fly an approach, which is NOT RNAV, you have to deactivate VNAV first. Use only NAV and the localizer to get under the glideslope. You have to be on the right altitude or lower, to catch it. If you‘re under the glideslope and the approach mode (APP) is activated, the plane will catch the glideslope.
You should see a blinking GP (or is it GS?) at the top of your PFD.
I flew just a few minutes ago a nice ILS approach in Nassau (MYNN). Worked everything well
(…) active navigation source is in LOC or BC prior to passing the FAF for ILS, LOC, LDA, and BC approaches (…)
I have had the same problem with several variations:
1- Localizer is not captured and Longitud enters in a ROL to the right or left. I use the Heading and re direct to the runway and land manually. Sometimes the systems captures the localizer and the Glide.
2- Everything looks right on approach and airplane is following the Glide path and the localizer diamond is right in the center and suddenly it get disconnected, and jumps up.
3- It never captures de localizer no matter what I do. The LOC indicador is there and I click approach but nothing, check if it is the Loc and Nav1 selected but never engages and land manually.
Maybe I am doing something wrong. Is there a manual or guide with the complete procedure? I will appreciate your help.
I’m not willing to accept that I can’t use the TBM 930 with G3000 like before. My annoyance is great because I am now forced to do an IFR rating. Why did the game character disappear? I will cancel m account soon!
You can still fly VFR. There is nothing stopping players from flying VFR using the new G3000. If it’s autopilot related, all the functions for AP still work and are invoked/operated in the same way - HDG mode, ALT mode to hold straight and level, GPS mode for point-to-point (not following an IFR plan) - these functions existed in the legacy 0.7.x G3000 and in fact, you have bonus stuff now that you couldn’t do before for VFR - things like Visual Approaches coupled to the autopilot - the old G3000 couldn’t do that.
I can understand your point of view, but I didn’t want this change. The majority of all players PC and XBox can only fly VFR now. This is not progress but regression.
I did create bug report but it was moved to main feedback thread. It’s not only callouts, even master warning and master caution is silent, it was there before update.
How 'bout that! It worked. Thanks. I’ll use your step-by-step list for a few more routes and then add some more details, like a dark start-up and planning adjustments using charts as I get more comfortable to all the buttons. Baby steps will get me there.
I still have the periodic loss of throttle response on the TBM that I need to figure out.
I had heard of Cape Girardeau many times listening to the radio but never been there in life or simulation before.
Edit: You said, “If anyone can manage to use this to successfully do their first TMB AAU1 ILS landing I’ll be a happy guy.” - Well ImpulseCello286, be happy.
I have the same issue with missing sounds that you mention. I also have the same autopilot problems others have noted such as Approach Mode not engaging when you get to your destination airport. Fingers crossed for the next update.
The main “new” things that need to be done or kept aware of seem to be…
Have to Activate Approach in MDF (in addition to Approach Mode button)
Have to pay attention to each segment of the flight plan
Have to be prepared to modify the flight plan. The World Map generates some strange flight plans now, some have gone halfway to the destination before looping around again at a certain waypoint that’s already been passed or generating a huge figure 8 just prior to landing. Holds are new and I always remove them because they add nothing to the flight other than making it longer. Not an official suggestion (like climbing using VS), just what I do. Flight plan modification (eliminating the extra stuff) has been a must almost every flight so far.
One thing I find is that an RNAV landing just doesn’t need the step where you turn on or engage the Nav radio. So it’s one step simpler at least what I’ve found.
Have you planned the route with the destination being automatic? The first change I want to learn, after a few more flights with your checklist, is adjusting to the approach I get when I’m getting near the destination. Although pre-selecting the runway is something I have always done too, it is not realistic.
I have had issues with flight plans also through simbrief, navigraph and the world map. Every plan i set up for either tbm or longtiude has these weird loops and double-backs added to them or will add the course reversal into the distance and estimated flight time on the mfd. I posted previously in here arpund post 200 i believe. A trip from NJ to Los Angeles and it calculated my distance at over 4000 miles and 10 hours.
Just some observations I’ve seen:
Quite a few of the “fly off track to some ‘random’ point” issues I’ve found so far are a result of a plotted enroute waypoint not being at the start of the selected arrival route. So you get routed off the plotted enroute waypoints to the first waypoint on the arrival route, and eventually back onto an appropriate point of the arrival route. So once I’ve compared where the arrival route starts, and if it’s conveniently close to the enroute plan, I just change the plan so I go to the start of the arrival route, or I just delete the waypoints that take me off the enroute path so I have a more continuous routing to the approach entry point.
Regards
P.S. Part of the issue is that the routing off the enroute track doesn’t show up on the WM. You can’t see the variation until you get into the plane and then it will show up on the route map when you zoom to the affected area.
