cannot reproduce and missing track file F _16 auto pilot has stopped working

[baza]

Not 100% sure but since update i cant click on auto pilot and it stays on, Stearing select will but heading hold and pitch will not 

 

Edited July 28, 2023 by baza

[_SteelFalcon_]

still works fine for me

[FusRoPotato]

You probably need to make sure you don't have any other modes active that might inhibit it, like flaps extension mode or refueling door for example.

[Furiz]

6 hours ago, baza said:

Not 100% sure but since update i cant click on auto pilot and it stays on, Stearing select will but heading hold and pitch will not 

 

 

Make sure that trim autopilot disconnect switch is set to NORM not DISC cause that will disable autopilot.

[av8orDave]

Autopilot isn’t working for me either. I’ve never had a problem with it in the past, but it seems completely unresponsive.

I have no mods. Also, I’ve checked my inputs and also stick to make sure I’m not having unintended control inputs. Even added a dead zone. Nothing, no autopilot function.

Playing on the multithread open beta.

[Furiz]

@davidrbarnette It is working fine for me, please check if you have Autopilot Disconnect Switch set to DISC it should be set to NORM. That is the usual suspect.

[av8orDave]

4 hours ago, Furiz said:

@davidrbarnette It is working fine for me, please check if you have Autopilot Disconnect Switch set to DISC it should be set to NORM. That is the usual suspect.

I’ll check. As a note, I’ve not changed anything from prior usage of the autopilot. I’ve never heard of the autopilot disconnect switch, nonetheless used it, so if that’s the culprit, something changed in the default state it is set to.

[av8orDave]

On 8/5/2023 at 1:32 PM, Furiz said:

@davidrbarnette It is working fine for me, please check if you have Autopilot Disconnect Switch set to DISC it should be set to NORM. That is the usual suspect.

Ok, so as follow-up...

Checked that the autopilot disconnect switch is set to NORM. It is set appropriately. Double-checked and cleared all bindings on my HOTAS relating to the autopilot. Made sure I have a bit of a deadzone on my stick so as to not accidentally kill the autopilot. Switched the AP switch to alt hold, and the other switch to strg, and nothing... it doesn't work.

I checked on both Nevada and Syria. I'm using the multithread open beta branch with no mods. I've used the F-16 autopilot for years with no issues.

[av8orDave]

One more update: whatever sense this makes, if I hold down the paddle switch, the autopilot kicks in for both steering and altitude hold and the plane starts holding altitude and follow the path. As soon as I let go, the autopilot goes unresponsive.

[rob10]

If one of you would post a TRACK you'd likely get better answers rather than people having to throw out random guesses based on the most likely causes.

[Furiz]

31 minutes ago, davidrbarnette said:

One more update: whatever sense this makes, if I hold down the paddle switch, the autopilot kicks in for both steering and altitude hold and the plane starts holding altitude and follow the path. As soon as I let go, the autopilot goes unresponsive.

There is your answer then, in normal circumstance if you press the paddle switch you will disengage the autopilot, so if you don't have it pressed and autopilot is not working then it must have inverted somehow. Since when you press it AP works... should be other way around.

 

Edited August 6, 2023 by Furiz

[av8orDave]

41 minutes ago, Furiz said:

There is your answer then, in normal circumstance if you press the paddle switch you will disengage the autopilot, so if you don't have it pressed and autopilot is not working then it must have inverted somehow. Since when you press it AP works... should be other way around.

 

 

Well, it seems you’re pretty close. I’ve discovered through this process that on the Winwing Orion 2, the paddle switch is managed as two buttons. When it is held depressed, it shows as joystick button 8. As soon as you release it, it shows button 7. When I mapped it, I clicked the paddle switch. You briefly see button 8 as the mapping for like a millisecond and then it switches to button 7 as you release it. So the paddle switch was effectively in a continuously held state. When I realized this, I remapped it while holding it down, and now it all works properly. 

All I can say is that this is a strange one.

[Furiz]

@davidrbarnette alright, as I said it was pressed somehow, I don't own winwing stick so I couldn't know in which way it was pressed, anyways glad we came up with solution

Edited August 7, 2023 by Furiz

[autracer]

Not 100% sure but since update i cant click on auto pilot and it stays on, Stearing select will but heading hold and pitch will not 
 

Look for your deadzone of your y axis, maybe not propperly calibrated.

[macedk]

Original poster not replied in 2 weeks now. Chalk it down to user error ?

[dmatsch]

I don't have a track, but have much anecdotal evidence from yesterday's session.  F16 autopilot definitely is non responsive.

From memory, multiple times, I engaged A-A or A-G, then resumed autopilot, then AP stopped responding to either ALT HOLD or PITCH HOLD.  Sometimes it came back, but it definitely didn't respond.

I just don't have the time to play the sim let alone save every track file every time something goes wonky (which is a lot).

[NineLine]

6 minutes ago, dmatsch said:

I don't have a track, but have much anecdotal evidence from yesterday's session.  F16 autopilot definitely is non responsive.

From memory, multiple times, I engaged A-A or A-G, then resumed autopilot, then AP stopped responding to either ALT HOLD or PITCH HOLD.  Sometimes it came back, but it definitely didn't respond.

I just don't have the time to play the sim let alone save every track file every time something goes wonky (which is a lot).

Sorry, we will need to see a track so far we have not seen this. 

Saving tracks takes no time whatsoever, when you end a session and something went wrong, just click save track. 

We appreciate any effort toward helping make the game better.

Thanks.

[Furiz]

16 hours ago, dmatsch said:

Sometimes it came back, but it definitely didn't respond.

This is the key moment here, it tells that it is most likely user error, cause in the world of programming, and assuming you did everything correctly, it will work or it wont work, black and white, it will not happen that it works sometimes and sometimes it doesn't cause that sometimes is a condition that it has met and started working again or stopped working cause of some condition. Therefore it was something you did that enabled/disabled it.

I've said in this post multiple times, check your Paddle Switch (which disconnects autopilot) bindings and make sure that Autopilot Disconnect Switch (which disconnects autopilot) is set to NORM.

On my end autopilot works fine.

[macedk]

Agree with Furiz. 
Many things can kick off the autopilot. (for safety I presume). 

In the physical world. 
1. check joysticks for active button presses. My classic one is air to air refuel. I test and quit out and the switch if left on. 
2. Check you assignments for buttons in game. You may have something double booked. 

In the jet.
1. If you try to flip the switch and it won't stay, the jet is not in the regime where you can use it (air to air refuel switch,  gear down, Autopilot Disconnect Switch, aoa over 15, to name a few) 
2. If on and it flips off (ba dum tiisshh), You have flipped one of the above switches or are doing heavy maneuvering.