[NO BUG] Very easy to over-g on decceleration

[Ahmed]

Hello,

 

I noticed that it is extremely easy to over-g the aircraft by over 0.5g when decelerating out of transonic regime holding the existing control inputs.

 

This looks like a quite undesirable design feature and probably needs some consultation with SMEs to finetune.

 

Note also on the initial part of the track that it is still not possible to attain the max g as stated on the FCS page at high speeds (5.5 vs 5.7), but I think that this is already reported.

 

Track attached.

 

Thanks

g.trk

Edited September 17, 2019 by Ahmed

[NineLine]

Hello,

 

I noticed that it is extremely easy to over-g the aircraft by over 0.5g when decelerating out of transonic regime holding the existing control inputs.

 

This looks like a quite undesirable design feature and probably needs some consultation with SMEs to finetune.

 

Note also on the initial part of the track that it is still not possible to attain the max g as stated on the FCS page at high speeds (5.5 vs 5.7), but I think that this is already reported.

 

Track attached.

 

Thanks

 

I never saw you over-g the aircraft in your track, which would be over 7.5. Am I misunderstanding what you are asking?

[Ahmed]

Indeed it does not exceed the 7.5g design limit, but it does exceed the g-bucket command limit as shown in the FCS page.

 

Shouldn't the limiter prevent commanding a positive g above the limit displayed in the FCS page while in the g-bucket?

 

My understanding of this g-bucket may be wrong though

Edited September 17, 2019 by Ahmed

[NineLine]

No, it will not prevent it, particularly with a rapid G-onset and in the trans-sonic region.

Edited September 18, 2019 by NineLine

[Ahmed]

Cool, the superhornet manual goes more into detail about that function and indeed it looks like my understanding of it was wrong.

 

The only thing then is that max command g is not being attained at high speeds (it only allows for .1-.2 less than it - can be seen at the begining of my track too). This has been commented several times by RL hornet drivers but I think that it is already reported.