Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
Are you using Developer Mode or made changes in it?
No
Have you disabled/removed all your mods and addons?
I don’t think I have any mods installed. Community folder is empty.
Brief description of the issue:
Autopilot fails to engage in C208 Caravan
Provide Screenshot(s)/video(s) of the issue encountered:
Sorry, I forgot to get a snapshot while the issue was happening. I verified multiple times, that HDG and FLC modes were enabled, and the correct heading and altitude were selected. In all fairness, even if they weren’t, the AP should still have at least turned on, when I hit the AP button. I verified there was no light on, next to the AP button, and no “AP” indication on the PFD.
Detailed steps to reproduce the issue encountered:
Setup a night flight from KSEA to KFHR with C208 G1000, current time and weather. The flight loaded with engine running. The FMS flight plan was setup by MSFS for a point-point flight. I selected altitude 4500 and FLC with airspeed 120, set the heading bug to runway heading and enabled HDG mode. Advanced the power lever and took off. Pressed the AP button on the panel, and it wouldn’t engage (AP light stayed off). I shrugged my shoulders and flew manually, but was irritated by the aircraft not wanting to hold the pitch trim I entered. I finally noticed it was rolling the trim back to some other trim setting that caused a gentle climb, as if AP was engaged and trying to trim, but AP wasn’t indicating on, and it wasn’t holding heading or airspeed, and then it didn’t capture the altitude when I got up there. I didn’t figure out how to “pull the breaker” on the trim, so I ended up constantly fighting the out of trim condition. I have many hours using the G1000 in the SF-50 and other aircraft in X-Plane 11, but not too much time using it in MSFS, maybe a dozen or so hours total in other MSFS aircraft like the TBM-930. This seemed a lot like a bug that needed to be reported; maybe it crept in during a recent update, although I’ve seen other users reporting similar issues back in the beginning, with people commenting that it worked fine for them, so it’s hard for me to know the real story.
PC specs and/or peripheral set up if relevant:
Asus ROG laptop, 256GB SSD about half full, 16GB RAM
Intel(R) Core™ i7-8750H CPU @ 2.20GHz 2.21 GHz
GPU0 - Intel UHD Graphics 630
GPU1 - NVIDIA GeForce GTX 1050 Ti
Build Version # when you first started experiencing this issue:
1.29.30.0 - AFAIK, this is the latest MSFS update as of today (12/11/2022).
For anyone who wants to contribute on this issue, Click on the button below to use this template:
Do you have the same issue if you follow the OP’s steps to reproduce it?
Provide extra information to complete the original description of the issue:
If relevant, provide additional screenshots/video: