New air brake behaviour

[cptmrcalm]

Noticed a little change to the way the airbrake responds to the warthog hotas throttle airbrake switch.

 

It is a minor bug and might give a small clue to any developer reading this. (and may help with other bugs as this is the way these things go sometimes)

 

Its not a major bug - but cost me dearly during a fight.

 

I could not close the air brake.

 

I would flick the airbrake "ON" going from "OFF" (from its rested forward position) straight to "ON" - clicking fully back going straight through a "CENTRE" position.

 

This "CENTRE" position is a 'nothing' area. -tested with windows only forward and fully back register as a "button" confirming that the click in the middle does nothing.

 

Before, I could fully click in one motion to "ON" and "OFF" without problems - getting the desired effect.

 

But now, you have to pause.

 

Meaning once you have clicked to "ON" you have to click into the "CENTRE" position first. Wait one second and then click to "OFF" for the airbrake to close.

 

 

(referring to update relevant when i last used on 21/08/2020.)

 

 

Again - not a deal breaker now that I know - but definitely a change and not a needed one in my opinion.

 

Hope it helps.

 

 

OH and ED - for the love of god. Please - Please - Please - Please sort out the dam low level flying issue with the F18!!! PLEASE!!!

 

i hate this being sucked into the ground nonsense!!

 

(forgive the rant. but maaaaaan that stuff has gotten me killed more times than i can mention!!)

[Frederf]

Some switches in DCS have to take their time animating before the next position change is allowed. User can select A-B-C transition faster than the A-B animation and B-C transition is not allowed because it's not in the B state yet. The problem as you describe is that if you command state C from a state that isn't allowed (e.g. A) that this request will simply be ignored forever.

 

I think it is perfectly reasonable and a good feature for switch states to be able to have finite transition time between states and a requirement to go through their natural switch state order.

 

What I don't think is reasonable is that if state Z is commanded and switch is in between states A and B that the command is completely ignored. Instead it should march through states B C D E F G... as fast as it's allowed to get to Z. Alternatively every time a switch completes a state transition it could look reevaluate the user input to see if it should stay at that state or continue to synchronize to the user desired state.

[cptmrcalm]

Indeed.

 

I thought to raise it because as I say, this wasn't the case before the latest update.

 

Before that, all was well.

 

I suspect the change was something to do with enabling something else to function. Or perhaps, it was a side effect to something completely unrelated.

 

It was really only to help a developer if it was an accident. It may have been intentional which is fine.

 

As i say, now that I know how it behaves, I can work around it.

 

But it caught me off guard and got me killed twice since the behaviour had changed from before.

 

I ended up a sitting duck, and my foe salivated before taking the killing shot - not believing his luck as I just fell down to earth like a floating leaf! lol

[Harker]

@cptmrcalm I checked the input files yesterday, there was no change in the latest OB. Seems like an issue on your end. Are you using TARGET or anything like that? I'm guessing it's something external.

 

Otherwise, try rebinding the keys, keybinds sometimes get messed up for some users, between updates.

[Svend_Dellepude]

Weirdly enough I just noticed the same behaviour. But I have no idea if it was introduced with the latest patch. Could this be something synced to framerates?

[Svend_Dellepude]

Was the switch animated before the last update?

[cptmrcalm]

Hi guys.

 

I don't know if the switch was animated before and to be honest, its not something I've noticed even now.

 

I haven't touched anything else. I don't use target since I use the default assigned to me by DCS.

 

All I know is that before, I could flick from air brake up to air brake off in one fluid motion and you got what you expected.

 

Now you cant.

 

I'll admit that I am curious to know why. But not so much that I must lose sleep over it.

 

Like I say, now that I know its changed, I can discipline myself to hold it in neutral before pushing on the switch to lower the air brake.

 

In fact. I was about to post this and ended up staring out of the window for a moment.

 

I don't get to fly very often, so I cant test now. But now I think about it, I think I can pull back on the air brake switch in one full motion - but cant reverse that.

 

Meaning I can raise the air brake by rapidly clicking back the switch aft - but the issue is with closing.

 

I have to click half way - wait - then one more click forward to close.

 

So now I think about it - I think its just the closing of the air brake that has changed.

 

Windows updates is all I've done - maybe that's messed with the button inputs or something.

 

I don't know. But guys, seriously -its interesting for sure. But not desperate.

[Gripen 4-1]

+1

 

I have the same problem. But some guys simply tell me that my setup is wrong.

But it works in stable.

 

https://forums.eagle.ru/showthread.php?t=283579

[cptmrcalm]

The plot thickens...

 

Interesting.

 

Maaaaaan times like this I wish i could fly more often. Desperate to try this out now.

 

I was getting worried it was just my age. Memory is getting terrible and self doubt is common place these days!!! lol

 

One thing is for sure:- It wasnt like this before.

[AW139]

I'm having the same issue. I made a thread too on it:

 

https://forums.eagle.ru/showthread.php?t=284374

 

Seems like it is a bug that they should probably fix. It was perfect before.

[Svend_Dellepude]

https://forums.eagle.ru/showpost.php?p=4468211&postcount=6

[cptmrcalm]

Finally had a chance to test.

 

Yes. Indeed the new functions are:

 

You can go from fully forward to full aft on the switch (HOTAS a10 warthog) in one motion, passing the centre position and erect fully (snigger snigger) the air brake.

 

Fine. As before.

 

However, clicking fully forward again is ignored. You can no longer do this.

 

So you have to click into the centre position first. Wait. And then click forward again to close the air brake fully.

 

Separate to all of this - and to those reading with any interest (probably very few!), when you click fully back to open the brake, you can pause its travel state by clicking into this centre position to freeze the position of the air brake - so long as you catch it at the desired extent. (in case you dont want it fully upright).

 

Not news to many regular fliers - but to any new-comers, this may be of use.

 

Im ok with the new function. It just caught me off guard is all.

 

 

But interesting that the function has indeed changed.

[cptmrcalm]

@Svend_Dellepude.

 

your message appeared after I sent mine as I must have not refreshed the page.

 

Doesn't seem to matter for me. I can leave the air brake on for a good while and still have the issue.

 

Of course, I say "issue" but I suppose I mean "behaviour". It is what it is.

[Svend_Dellepude]

The issue is that when you release your speed brake switch there is a center command issued on release that is tied with an animation. I think it's that animation you have to wait for. You will have the same issue if you use the retract/off keybind.