Commander 114

This could be a Navdata issue with your TDS or PMS GTN750. Do you have any other planes that use the same unit, and if so can you reproduce this same issue there?

@Hoff_Flight Ah, thank you for the suggestion. That might have been what it was last time I heard about it too, and I just got tickets mixed up in my head. Thanks.

@Black-Square ooh... good to know. Thanks!

I'm pretty sure that's the only step you would need to take, yes.

[image: 74cdb550-1cfa-4cd6-9b7e-a72b85112a12.png] Thanks for responding both. Here's my cockpit setup. I think I've traced it to my hardware though - the issue only happens when I use the AP panel on my Honeycomb Bravo, and doesn't happen if I use the mouse to control the altitude selector. I use the same controls in all my BS aircraft though and this is the only one it happens in. Any ideas?

Interesting. I noticed I occasionally still get fuel flow in the turbo during the prime, but usually not. I guess it will start to happen more often as it gets colder this fall

Is there any approx ETA on the next patch?

Ok... So on a whim I tried repairing my files (well, verifying my install with Steam -- it repaired two files) and for I forget how many flights now for nearly 10 days making conscious effort to put some VOR-to-VOR navigation using NAV mode into my flight plans I haven't yet experienced any random AP disengaging. That doesn't prove it can't happen... since you can't prove a negative... but it's certainly encouraging. It used to reliably disengage once or twice per flight and so far I've had trouble-free navigation since repairing my files.

@Zacke said in two more questions: sensivity of the mixture/flap bindings: in the manual it's stated one can change the sensivity of the mixture control by using the right friction lock. But is that only for hardware bindings or does even change the sensitivy when I use the mouse? It only changes the sensitivity when using the mouse wheel on the mixture control. Sensitivity of your hardware controls is dependent on your actual physical hardware controls or the binding/sensitivity curves that you've assigned to it. @Zacke said in two more questions: sensivity of the mixture/flap bindings: And I can't bind the flaps to my joystick buttons. I tried the different flap commands (continous etc.) but nothing's happening within the Commander. The ordinary Increase/Decrease Flaps bindings in MSFS should work just fine. Don't use the Continuous ones unless you know what you're doing. If you want the continuous flap control to work, you'll probably need to use third party binding software. There's an example of how to do that with Mobiflight: https://community.justflight.com/topic/11197/axis-control-for-cowl-flaps/26?_=1789410025015

Hello djd565, please read my new post from today (https://community.justflight.com/topic/11360/some-minor-observations). Do you also see the problem the KLN keeps alerting you to change track after passing a flight plan waypoint? Maybe these problems are connected.

@NG7V Don't forget there are two handles for the doors - the lower one opens the door once the upper one is unlocked ... but this doesn't explain why the baggage door doesn't open.

IRL you'd probably look down when you slotted the tablet back into its storage? I find it quite immersive having to look where I'm putting it, rather than just clicking it 'off' and having it 'vanish' ... but I use TrackIR so that makes looking down easy I suppose.

It seems SU6.1 has broken the ability to get into the aircraft by clicking the seat, I can get out just fine but having to Shift + C to get seated now. Can anyone else confirm please? (using VR)

Thanks. Changelog explains my start issue. No doubt I watched pre 1.1 videos. Regarding state saving; I do shut down to black cockpit, but keep the key in place. Back to simulator: Keys often placed on altimeter. Bat - alternator - trim on - once even flap down. Frequencies and alt preset are saved. But this is absolutely minor issues, takes only seconds to clear. If it is only me and the old mediocre PC, do not waste time on it. ---- And yes I do shut down using main menu. . Again - thanks for another wonderful stellar product and support.

@Black-Square ok. I deleted the aircraft and reinstalled from the 0.1.1a installer and RNAV WPT2 is still only working with NAV2 instead of NAV1 with the GNS530/MX170B combo.

I think people are calling the fact that the compass card moves when the gyro spins up "auto initializing," and that's where the disconnect stems from.