2.5 Altitude and speed modes not working as before

[fargo007]

Three of us flying the gazelle, L and M's.

 

The altitude hold mode works for one guy, but not for the other two.

 

FYI we are all verifying that we are within speed and attitude limits for these modes, we see the "Altitude" written in white on the controls display box (Rctrl-ESC), and the switch in the cockpit is correctly thrown.

 

Instead of holding it steady, it only holds steady-ish - and as soon as you release the cyclic, it slowly starts to pitch up into a stall.

 

Speed mode is similarly affected.

[Ramsay]

The 'Auto-pilot' is an extended SAS mode - it doesn't have control of the throttle or collective, only the SAS pitch channel.

 

It should adjust cyclic pitch up or down to maintain the chosen parameter - speed or altitude (instead of attitude).

 

In effect it trades speed for altitude or vice versa, until speed falls/rises below/above the allowed limits (and the mode disconnects) or the pilot intervenes.

 

It sounds like there's still work to be done on the autopilot/SAS control logic but perhaps you weren't trimmed correctly for 'hands free' as it was working for one guy.

 

I've noticed differences between the M, L and Mistral versions in the past, so that might make a difference unless you were all in the same variant, so add as much detail as you can.

Edited February 1, 2018 by Ramsay

[fargo007]

Thanks, I know exactly how it "should" work.

 

The essence of what I'm saying here is that it was working correctly for all three of us in 2.2, but is not in 2.5.

 

We even had the guy it was working for multicrew with me and observe it. It occurs for two of us repeatably in both the L and M.

 

Something's up.

Edited February 1, 2018 by fargo007

[Ramsay]

Thanks, I know exactly how it "should" work.

 

The essence of what I'm saying here is that it was working correctly for all three of us in 2.2, but is not in 2.5.

Cool, that's pretty specific.

We even had the guy it was working for multicrew with me and observe it. It occurs for two of us repeatably in both the L and M.

 

Something's up.

The only 'bug' I can think off that is 'a little' like what you describe, is in the L-39, were the auto-pitch trim tab behaves differently if you have a force feedback or regular joystick, other than that, it may be a regression from 1.5 as there seem to be a few issues (textures and the like) that were fixed in 2.2 but are bugged again as the fix didn't make it into the main 2.5 branch, OTOH this might be a new bug altogether lol

[fargo007]

I've made no hardware or OS changes between the versions. TM warthog stick and hotas. Haven't even recalibrated. I'll pay a visit to the settings and have a closer look.

 

It does seem like it's "trying."

[fargo007]

I got it.

 

Nothing wrong with the Gazelle at all. For some reason in 2.5 the calibration of my stick isn't the same, and it apparently wasn't finding center.

 

A simple recalibration fixed this 100%.

 

Let me thank you for your quick and helpful attention here.

 

/Fargo

[Gizzy]

.... For some reason in 2.5 the calibration of my stick isn't the same, and it apparently wasn't finding center....A simple recalibration fixed this 100%./Fargo

 

Yes, I got this just before the 2.5 update... the Gaz could not hold a level course with full trim hat deflection.. initially I thought they had changed the FM in the last ED update but a windows re-cal sorted it.... so it 'might' be a windows 'thing' from one of their latest updates..