Before I create a bug report, I would like to hear if others have the same problems:
First flight today with SU 6, in the Vision Jet. I noticed weird behavior of the autopilot, particularly during descend: when dialing in a new descend altitude, I did not get the Path indication in the AP annunciator panel (and no TOD in the Nav display).
Also, I noticed that the autothrottle stopped working during descend, even though it was activated (control light on). The FMS speed button on the AT panel was also lit. But I had no auto throttle. Moving my physical throttle lever changed thrust settings.
Was there an update of the Vision Jet in SU 6 and avionics stuff now works differently? If so, I would love to understand what exactly has changed. Or did SU 6 break something?
3 flights later (different routes, different airports):
I was not able to reproduce the VNAV and AT problems I described in my post. For me, the SF-50 is behaving normal again.
The only thing getting on my nerves is that I have absolutely no clue what caused that first flight after SU6 to be so weird. But I’m telling myself: If flight simming were easy, everyone could do it
It happened again! First symptom: the flightplan (put together via SimBrief) does not show with all details in the Nav Display. I had the departure and Origin, but none of the waypoints from the SID or STAR. On the PFD, waypoints besides departure and arrival airport are not displayed.
I think this is why the AP does not know what to do - as in: When I try to select nav mode there is no meaningful next waypoint for the AP to fly to, no altitudes, no speeds.
My guess is now that this might have to do with the latest NavData Cycle, or with SU6, or both. Will need more testing and further flights to see if I can establish a pattern…
I’m finding the auto throttle doesn’t work at all with this aircraft. It worked just fine in MFS2020, and I’ve mapped the bravo throttle the way I did before pretty much. Cabin lights don’t function, but worst of all, the auto throttle just doesn’t work like it did before. The ‘SP’ light appears in white in the display, but once the auto throttle is activated, the throttle lever should be inactive and speed should be completely automated whether in manual mode or otherwise.
My Vision Jet problems are gone. What solved my AP and AT problems was to make sure the FD is switched on before anything else. In the past, activating the AP also switched on the FS, but that does not seem to be the case anymore.
With the FD off, I could reproduce all the problems I described above, and with the FD on the automation behaves as expected. Not sure if Asobo made changes to the G3000 in the last update - my feeling is they did.
Another thing I noticed it that VNAV and GS/LOC capture are not as robust as they were in the past, so more attention is needed, and occasionally pilot input. Again, not sure if this is a new feature to make the system behave more like in reality.
But anyways, I got accustomed to how the Vision Jets systems now behave, and I have no more issues. Just wanted to let everyone know!
Thank you StanTGM - this fix absolutely worked for me. Switching on the FD before programming any altitude or Nav instructions into the auto pilot 100% fixed the auto throttle issue I had previously.
That was a very helpful post because I have noticed a possibly related problem since the Citation X update.
I had VNAV activated but no PATH indication ever happened, yet the plane started to descend at the right place. I also get Autothrottle turning off for no apparent reason.
I will have to check and see if the flight director issue is what’s happening.