Autopilot goes knife edge

User Support Hub Aircraft & Systems
, , ,
1

Using the template below will greatly help the team reproduce the issue and ease the process of fixing it. Before posting, search for an existing report. If you are not sure it’s a bug, please first report in User Support Hub.

3 tags are required - add them in the tag section next to the title above:

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue: Autopilot puts the airplane into a 90 plus degree nose low bank around 30 seconds after it is engaged, regardless of modes.

If applicable, which aircraft is experiencing this issue: Caravan, FSS 727-200. These are the only airplanes that I have flown yet with autopilot engaged. So, until further investigation, it can be said to be happening in all planes flown…

[PC Only] Did you remove all your community mods/add-ons? If yes, are you still experiencing the issue?Haven’t tried that yet

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?Thus far, every time autopilot is engaged

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

1.Take off

2.several minutes later engage autopilot
3.

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

What peripherals are you using, if relevant: Honeycomb Alpha and Bravo

[PC Only] Are you using Developer Mode or have you made any changes to it?No

[PC, MSFS 2020 Only] Are you using DX11 or DX12?n/a

[PC Only] What GPU (Graphics Card) do you use?RTX 3070

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

[END OF FIRST USER REPORT]

:loudspeaker: 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:
•

2

Hi @TonyV3711 ,

Thank you for this report. We’ve moved your topic into the User Support Hub.

The Bug Reporting Hub is for posting suspected or confirmed bugs that other users are able to reproduce without duplicating an existing bug report. Using the template or providing all the relevant information about your bug and sim setup is required in order to provide valuable information, feedback, and replication steps to our test team.

If you are not sure if your issue is a bug or need further input from the community, please use the User Support Hub category. If the community can replicate your issue, first search the Bug category to see if there’s an existing topic. If it already exists, contribute to that report. Duplicate bug reports will be closed.

If you believe it is a new report and no duplicate exists, then create a new bug topic using the provided topic template.

All issues caused by or involving third-party addons/mods should be reported to the third-party developer. Assure that no addons/mods are used when reporting issues in Bug Reports.

3

Do you have the same issue if you follow the OP’s steps to reproduce it?
• no

Provide extra information to complete the original description of the issue:
• no issue as described by OP with the C208 autopilot neither all others 1st party aircraft autopilot
@TonyV3711 : maybe a binding conflict ?, have you tried with the default peripherical profiles ?

If relevant, provide additional screenshots/video:
•

4

Do you have the same issue if you follow the OP’s steps to reproduce it?
• No

Provide extra information to complete the original description of the issue:
• Took off with heading mode set, and desired altitude set with VS set to a normal climb rate (or use FLC and set a normal climb speed). After a few minutes I activated the AP, and it locked on the HDG and climbed to the desired ALT without issue. I then set a GPS course, and armed NAV mode, turned HDG to intercept course which it did as normal.
Might check to make sure you’re not engaging AP into roll and pitch mode which will follow the angles you’re set at when AP engaged, and could lead to a stall if not changed.
Regards

If relevant, provide additional screenshots/video:
•

1 Like
5

Still does it, with at least two of the airplanes, one of which (Caravan) is part of the sim, the other is the FSS 727 which is in early days yet for 2024. The out-of-the-box C-172 G1000 works OK. I tried to see if there are any conflicting inputs, but there appear to be none. Of course, the control inputs section of the sim is as incomprehensible to me as high energy particle physics is, despite my having an ATP and 5 type ratings in transport category jets! So there could be issues somewhere that I have been unable to uncover. This started with the 727 somewhat prior to SU2, but since I use FS2020 for most of my work I have only flown a few of the airplanes in 2024 and for all I know, the issue may have been there all along in things like the Caravan. BTW, the autopilot stalled the Caravan with an IAS of nearly 150kts, and despite all corrective inputs after a/p disconnect, it did an oscillatory descent all the way to the ground with plenty of aispeed on the indicator. Yes, I know that it is possible to stall an airplane, in theory at least, at any speed, but there was no g load to speak of when it started out of control…

1 Like
6

I dont have the issue either. Are you enabling autopilot from the controller or from the panel? It could be a binding conflict if you are doing it from the controller.

7

My Honeycomb Bravo does not have most of the autopilot functions operable - FS2024 does not seem to have come out of the box with much of that operating, and I certainly don’t have the expertise to get it going, so all of my A/Piloting is done by using the mouse to press the keys on the screen showing the cockpit view.

I have checked for control bindings in the settings, and removed a few that appeared to be associated with another controller that I only use one axis of for nosewheel tiller steering. Beyond that, I can find no conflicting bindings…

I have to set up the controls for each airplane - when I first invoke an airplane I haven’t yet flown, nothing works - not the yokes, not the throttles, not the view selection with the numeric keyboard, which is how I want views set up so as to make it as much like XPlane as possible. Now with 2024 it appears that we can assign a set of control bindings (is that what they are called?) to an airplane - in fact, that seems to be how you MUST do it. This is more or less similar to XPlane, and is an improvement over FS2020. But somehow, little or nothing appears to be pre-loaded in the way of axis assignments, button assignments, and the like. For example, sometimes the heading bug knobs on the Bravo move the heading bug on the screen, but on other planes not (as it comes out of the box). Likewise for the other parameters on the Bravo autopilot panel. I do have SpadNext, which is necessary to assign knobs and buttons from a custom made (not by me, I assure you!) button box for the G1000, but I don’t use it for anything else at the moment.

Is there any way to look, on one screen, to see all of the assignments for a particular function (say, toggle autopilot) across all devices attached?

8

I’m sure some wizard has come up with a way to extract all that information, but the only way I’ve found to check an input across peripherals in the sim is to enter the text you want to search for on the controls page, and then you can click on each peripheral to see what’s assigned without having to re-input the text again. So it’s fairly quick to check if there are any duplicates across peripherals.
I once had an issue where my flaps would not stay up after I raised them. Finally figured out that I had set up an input on my throttle (which was actually labelled “flaps up/down”, and at some point decided I didn’t like that particular switch since it’s a pain to get to IMO, and set a button on my joystick to raise/lower the flaps. Then I realized that at some point I had bumped the switch on the throttle, and it was counteracting my joystick input.
Hope that gives you a workable way to check for duplicate inputs across peripherals fairly quickly.
Regards