Technically, the AP will adjust your pitch upwards to give you a VS matching the selected speed. You must also adjust throttle and the inertial separator to achieve these parameters. The PIM document for the TBM covers optimal climb rates/speeds.
Thanks for the input. Yet I think @MustangPauli refers to maintaining set speed in FLC mode only. I can confirm that in FLC the aircraft appears always to maintain 5-10 kts below the set speed.
Yes, that’s what I’m referring to as well. FLC will adjust vertical speed based on TRQ to maintain the set speed. That’s what I mean by giving you a particular VS. Sorry is there was any confusion. In the TBM, 124 kts in FLC will yield an initial VS of about 2800 fpm at 100% TRQ. It drops as altitude increases.
Working again today, Very odd. I am wondering if its affected by Internet connectivity issues, and if there is a brief outage it drops out. In any case should alarm to alert the pilot. Otherwise today worked perfectly to capture the EGGD ILS 27 Approach in full IFR. Just needs a manual swap over to the localiser when inbound and Approach activiating on the autopilot.
I don’t know if this is a known issue, but yesterday the C172 G1000 acted strangely on me:
It was a short direct VRF hop.
First, the FD/AP annunciator insisted on displaying HDG even though it clearly was in NAV mode.
A little later, when I wanted to prepare my approach, I noticed that I couldn’t change the target altitude. The knob just didn’t do anything. I soon discovered that the same was true for barometric presure, even when pressing B. Everything else seemed to work, including setting the heading bug.
I decided I had to fly her manually and use the steam altimeter. When I began my descent, I noticed that the altitude tape also didn’t move.
At some point while I was staring at the steam altimeter, everything suddenly went back to normal!
The entire episode lasted 15-30 minutes.
Another example of the AP trying to kill me…
It’s a really good idea to show a video, but unfortunately the quality is not good enough. It’s not really clear to me what the settings were before activating the AP. Try again and zoom in a bit…
Unfortunately the upload only allows 5MB video.
But, if you go full screen you can just about see it.
FD&YD are on as well as ALT mode 7900ft, then I turn on NAV mode (FMS source, I’m already flying on the route as you can see). Ten I engage AP and it banks very hard to the left.
I have the same problem in the TBM 930, but it only happens occasionally. I can many flights without issue.
Freezing in all TBM930 modes, either hand flying or AP flying. Mine lasts about 1 minute or less, slightly more if during the day. I suspect it’s something to do with the internet connectivity I have here. I have not tested if it goes away with AI/Live Traffic turned off. Someone once said to clear cache, as errors have creeped into that, again, have not done that. Just too many frustrations to use it until it’s working better. I stay in the forums, and if I want to get black and blue, I try flying the 787 to see if anything has been put out which fixes it. Just waiting for the 29th (think that is next patch release).
Another video, this time in Cessna 172.
I accidentally switched from HDG to ROL but it happens in HDG too (or any other mode)
Regardless the behavior is wrong and very violent.
Seeing the ROL mode makes me think you might want to take a look at this :
Are you guys able to select a Direct To and then fill in a holding pattern at that waypoint?
Because I am not, but this feature is essential to fly on VATsim with IFR rules…
I hope Asobo does expedite the development progress on the G1000/3000
As I said, it also happens with HDG.
Regardless, ROL shouldn’t bank the plane like that. In fact, it should hold the plane at the same level (the oppositie of what is happening).
Normally dont have issues with the AP, but today it was trying to kill me.
Take this for example
It was perfect, then just went berzerk by itself.
I notice that the avionics dont fly straight to the waypoints. If you select a transition or IAP on an approach sometimes the autopilot/avionics will auto create this big sweeping 180 turn to bring you straight in to the fix. Rather than flying direct to the fix and having to execute the procedure turn.
In addition the glidepaths on RNAV approaches are all wacked. You wont capture the GP if you follow the approach plate exact on most approaches that I have done in the USA.
Also direct to is still busted. I rarely can get a direct to work correctly.
Just downloaded my 26GB patch, hoping that the G1000 was improved. A prior entry called the G1000 a “hot mess”. That’s the understatement of the year. It’s almost completely unusable for IFR. What an absolute mess! There are so many bugs and missing features, this is at best a kid’s toy. No certificated pilot can use this for any type of training. Thanks so much for all of the real pilots documenting the issues. Hope Asobo gets some bandwidth to address most of these before all real pilots abandon the platform. I’m going back to X-Plane 11 until then.
Also relieved to hear it’s not all me. I only just learned the G1000/3000 in XP11 but only to the point of not embarrassing myself. I’m still learning and thought I was the problem.
When you play with a flight plan for too long it ends in a freeze (TBM) or a CTD (DA-62) …and with all these broken bits, you DO play with it long enough for a freeze or CTD.
These Garmins aren’t trivial to learn when they work perfectly. Learning on ones that are so completely broken is sadistic and cruel.
I’ll echo @RookyBassoon944 in thanking all of you who really know these devices for articulating the exact problems in a way us learners cannot yet.
Could this problem be related to the AI co-pilot issue? The AI co-pilot doesn’t seem to like turning right and when a flight plan requires this, it’s ignored and the aircraft flies in it’s current heading, going completely off course. This does appear to affect all aircraft. See this.
Hi,
With all stated bugs and wishes related to G1/3000 I want to pull attention over EFIS stuttering issue as well.
I belive most of us aware of this problem but briefly:
EFIS / Glass Cockpit planes (More or less all of them have issue) cause noticable stutter close to ground and during take off and landing while round gauged ones fly silky smooth with same testing hardware and environmental conditions. (You may compare C152 and C172 G1000 yourself)
You may find the details from the link below. Whatever we tried we couldn’t manage to eleminate the problem:
Please consider supporting this issue / topic by voting in relation to this topic.
I hope Asobo will do their best about it in time.
Kind regards.
I had the A320nx freeze today, for about 1 minute, using 1.10.8.0