At least this topic seems at the top spot on the MS radar:
3 Likes
Be careful probably.
Some approaches working not ok, are predefined with non sense IAF somewhere outside. if you see not correct approach definition, you need make screenshot and send to Zendesk with clear infos. Also you can post here that we can confirm that if you’re not sure.
1 Like
Yeah the G1000/G3000 is a mess atm. Editing flight plans in flight doesn’t work, VNAV doesn’t work at all. In the 787 you can’t EREASE flight plan changes if you don’t want to execute them…
i hope they fix the autopilot and the garmins…
autopilot skyrockets after takeoff..
unflyable for me atm…
2 Likes
I’ve had some issues with the aircraft pitching up violently after activating the AP. It seems like the AP doesn’t know how to handle the trim if it’s set to anything more or less than a couple of degrees off the neutral/TO position. If the trim is returned to the TO position before activating the AP you shouldn’t have any issues. It’s obviously just a workaround but at least it will prevent you from stalling and crashing.
1 Like
If you are using an ILS approach… a lot of the frequencies listed in the sim are incorrect. I have better luck getting my ILS freqs from Skyvector website.
Today I entered a longer FP by hand. When I select the last WP and hit “insert after…” I had to type/add a new WP always a second time to make it show up in the FP. The first time it’s just ignored.
I have yet to successfully fly an ILS approach using the Garmin FMS in the Citation Longitude. MSFS freezes every…single…time I attempt to verify waypoints, activate legs, etc. once cleared for an approach. It’s a very frustrating but that absolutely must be fixed ASAP.
The Garmin 1000 has several bugs that are being worked on according to reports. In particular, it is not yet possible to activate legs in the device. At this point, you can only fly the plan you create in the World Map. Also, most are having problems with FLC mode, so only VS should be used by the AP for changing flight levels.
The problem with FLC mode is that you cant see the selected speed in the aircraft before you enable FLC mode. I have a hardware panel “VRInsight FCU” and it lets me see the selected SPD and I can adjust it on the panel. This SPD is always set to 0 at session start. When I pre-select 150kns for example with my external hardware and then hit FLC the autopilot responds correctly and doesn’t try to enter orbit like would normally happen with the speed set at 0. Asobo just needs to allow people without such hardware to see (and adjust) the pre-selected speed before FLC mode is activated. i.e. display the SPD in the PFD as it is in the real Garmin panel even before the FLC mode is activated.
1 Like
@AndyDigital In the TBM9 FLC mode seems to work normally beside the fact that the AP is sometimes pitching quite aggressiv. If you enable FLC mode the current speed is set for FLC.
I prefere to use VS mode to adjust the climb and let took over then by FLC to avoid the strange pitching.
It’s not though, my info above was in regards to the TBM930, its only that and the 350i that I fly in 2020 at the moment.
Maybe its not working for me because I’m using external hardware to enable FLC mode. But a lot of people are complaining about it pitching up and that is because the Auto Pilot is trying to climb at 0 knots.
Once I have selected a SPD it remembers the last selected speed for the rest of that sim session. If I go back to the main menu and load another flight its back to 0 again. Like I say it might be that its the software (LINDA) I use with my hardware that is causing the issue.
1 Like
I use FLC for climb and descent and it seems to work fine like that:
- When you click FLC a blue little bug appears on IAS stripe
- Then, with the 2 little buttons incr/decr, you adjust this blue bug to select a minimum speed for climbing or a maximum speed for descent
- Then the A/P pitches to stay between this min or max IAS value
Works like that in Xcub, C172, or TBM, pretty efficient because prevents to be in over or under speed during climb or descent
1 Like
I’m not a pilot, so I could be wrong on this. However, it’s my understanding that when FLC mode is enabled, the AP should set the speed automatically to the current aircraft speed. All other things being equal, that would resolve the pitching issue when FLC is enabled.
But I think it might be worse than that. If you enabled FLC mode while sitting on the ground, the speed starts at zero, but you can adjust it to a more reasonable value. At first, I could set the speed to Vx in that scenario, and then when I started AP, the AP would adjust the speed of the plane to Vx. Now, though, it just pitches up as if the speed were still set at zero.
2 Likes
I fly the TBM a lot and the only “issue” I’ve encountered with FLC is sometimes it seems to struggle to keep it exactly at the desired speed, e.g. if I set it to 160kt the aircraft might only climb/descend at 157kt or something similar but, I really don’t consider that to be a bug, at least not a game-breaking one. Other than that FLC works fine for me.
Again CTD while using the G3000 in the TBM:
- Done a direkt GPS Flight from A to B. No waypoints/approaches etc.
- Landed, shut down the aircraft
- Restarted the aircraft to fly back
- Set a new origin in the G3000 (the current airport)
- Set a new dest. in the G3000 (the origin from the leg before)
- Set an approach on the dest. → Load app. → CTD
1 Like
This should theoretically work but knowing the current state of implementation I would restart the flight from main menu.
Even in P3D I use to restart the whole computer + sim before every flight leg.
1 Like
Totally agreed. But sometimes I prefere not to restart everything just for the fun of sim.
And CTD is never good. 
Anyone having problems with the G1000 randomly disengaging and then being unable to reconnect? I have used the real thing in a Cirrus, and flying the Cirrus in the sim with the G1000 for IFR is a hit and miss affair. It shuts off randomly. Maybe its supposed to mimic turbulence disconnect, but if so is far too sensitive. Also you should be able to reconnect it.
This is correct. Making changes to either the G1000 or G3000 from the cockpit just isn’t working the way it is supposed to. It is a programming challenge to reset everything in an object like the Garmin devices so that new setups can be operated correctly. It’s easier to start fresh.
The climb rates are going to be decided by your TRQ during the climb. The PIM document for the TBM explains the most efficient climb parameters. The inertial separator also impacts climb efficiency. If you want to fly by the book, the PIM says TRQ should never exceed 100%, so you need to tweak your throttle throughout the climb. The quickest climb rate is 124 kt, giving you about 2800 fpm climb to FL310.