A new callback request for SPD BRAKE functionality.
-
@Snake122 Are there no toggle switches on the X65 throttle that you could map to the brakes?
Here’s an interesting experiment that might work for you – map the open speedbrakes button to the AFBrakesOut callback but then map the button you want for close speedbrakes to the AFBrakesToggle callback. If the brakes are even slightly open, the toggle callback will fully close the brakes. Obviously, if the brakes are closed, the toggle callback will fully open the brakes
But it may be a perfect solution for those without a toggle switch available, or only have buttons.
Of course, the downside is that you cannot partially close your speedbrakes as the toggle callback is an all-or-nothing affair AFAIK.
-
@Atlas said in A new callback request for SPD BRAKE functionality.:
@Sabre said in A new callback request for SPD BRAKE functionality.:
This is all running in circles. Retract (completely). ))
Thanks.
No, not running in circles at all. I think we’ve now identified the issue at hand here and … well, I’ll just leave it at that.
PICNIC
Atco, I like your enthusiasm, especially when you start explaining to me how callbacks actually work on equipment you don’t have.
BIOS
-
@Sabre said in A new callback request for SPD BRAKE functionality.:
Atco, I like your enthusiasm, especially when you start explaining to me how callbacks actually work on equipment you don’t have.
I’m explaining to you how the callbacks work. These allows you to do things — like replicate how the real thing works — regardless of what hardware you use. Unfortunately, making it work on YOUR hardware is YOUR problem, not mine.
I am amazed that you continue to show your attitude for someone who doesn’t know how to map a speedbrake switch correctly.
-
@Atlas said in A new callback request for SPD BRAKE functionality.:
Unfortunately, making it work on YOUR hardware is YOUR problem, not mine.
That’s exactly why I didn’t ask anything from you here in this thread, with all due respect for you for helping with other issues
Thanks.
-
@Sabre said in A new callback request for SPD BRAKE functionality.:
That’s exactly why I didn’t ask anything from you here in this thread,
Are you also confused at how forums work??
with all due respect for you for helping with other issues
That’s not how “with all due respect” means, nor how it is shown. Your attitude at the people who develop this game and others that come in to help you with your issues show zero respect at all.
I wager my suggestion to @Snake122 in the post above is the functionality you’re looking for. Wind your neck in and go give it a try.
-
@Atlas said in A new callback request for SPD BRAKE functionality.:
@Sabre said in A new callback request for SPD BRAKE functionality.:
That’s exactly why I didn’t ask anything from you here in this thread,
Are you also confused at how forums work??
with all due respect for you for helping with other issues
That’s not how “with all due respect” means, nor how it is shown. Your attitude at the people who develop this game and others that come in to help you with your issues show zero respect at all.
I wager my suggestion to @Snake122 in the post above is the functionality you’re looking for. Wind your neck in and go give it a try.
It’s like talking to an empty drum, I swear! I’ve already tried all of this even before starting this thread, don’t you understand?
-
@Atlas said in A new callback request for SPD BRAKE functionality.:
Here’s an interesting experiment that might work for you – map the open speedbrakes button to the AFBrakesOut callback but then map the button you want for close speedbrakes to the AFBrakesToggle callback. If the brakes are even slightly open, the toggle callback will fully close the brakes. Obviously, if the brakes are closed, the toggle callback will fully open the brakes
I have mapped it that way before. I don’t like that I can accidentally throw them out that way you describe. Under duress it’s too easy to do. I’d rather have partial open from not getting them closed than complete open unintentionally.
No toggle switch under my thumb, I could use one on my pinky, but feels unnatural after all these years. There is a 4 position slider, but I use that for the dogfight switch.
-
@Sabre said in A new callback request for SPD BRAKE functionality.:
It’s like talking to an empty drum, I swear! I’ve already tried all of this even before starting this thread, don’t you understand?
And I’m supposed to know what you’ve tried and what you haven’t? LOL.
I hope you get the solution you so clearly need.@Snake122 said in A new callback request for SPD BRAKE functionality.:
I have mapped it that way before. I don’t like that I can accidentally throw them out that way you describe. Under duress it’s too easy to do. I’d rather have partial open from not getting them closed than complete open unintentionally.
No toggle switch under my thumb, I could use one on my pinky, but feels unnatural after all these years. There is a 4 position slider, but I use that for the dogfight switch.
Are you using 2 buttons for this at least? That way, a small tap or two on open then a tap on close will give you guaranteed closed speed brakes.
-
@Atlas said in A new callback request for SPD BRAKE functionality.:
Are you using 2 buttons for this at least? That way, a small tap or two on open then a tap on close will give you guaranteed closed speed brakes.
Yes, but the problem is with your suggested mapping if I accidentally double tap or had them closed when I though they were open (both easy to do in BFM at times) they are going fully out. It’s only guaranteed of you are in sync or take some time to open. Yes it honestly rarely happens when you are completely out of sync, but in the moments it happens it is almost always a really bad time for it even to give it the tap it open some to then guarantee close. A brakes fully closed callback gives the same functionality of the set it and forget position of the real switch too.
-
@Snake122
I see. To guarantee a closed brake, you’ll have to tap it open then close it again, or program it so that pressing the close button will fire one open command then one close command – which I think is the best way and no need to worry about being “in sync” or anything like that at all.Having a “fully closed” callback is just a bandaid to compensate with different hardware. Using this callback will mean that you cannot just reduce the brake effect slightly, you will have to start over each time. Remember that the brakes only really open or close if the switch is held in that position. A correct switch is 3-way with momentary for open and captive/toggle for close.
-
@Atlas because of the real life switch setting putting brakes out incremently (momentary) is more important than retracting them incremently (option of captive toggle to retract and leave it so the definitely get shut). Obviously incremental retract can be done with the actual switch with focus on using the switch carefully, but for me the sacrifice of the careful use for the reptile brain option under Gs that they value with switch function of the set it and forget it held retract setting is more important to me. I can be careful on extending if needed because I’ll be judging overtake actively or just hold it to be open on an nasty overshoot, but as they say, “airspeed is life” so getting the smash back is more the gross motor function.
-
@Atlas I have 3 buttons on the base of my cheapo stick.
1 => open incrementally, while held (AFBrakesOut)
2 => close incrementally, while held (AFBrakesIn)
3 …for the 3rd button I used to assign to toggle (AFBrakesToggle) but that is both unrealistic and error-prone, as everyone has already beat to death.
now I’ve changed the 3rd button to do what ewildcat suggested
onPress => AFBrakesOut
onRelease => AFBrakesToggle – because toggle always acts as auto-close when the brakes are > 0% openit’s sounds like nothing but it’s amazing what a little quality of life improvement that is (maybe just for those of us with cheapo hotas that don’t have a realistic locking speedbrake switch)
-
@airtex2019 This is brilliant, thank you for spelling it out.
At first I thought it would not be possible to make it work in AL, that it would require hand-editing the keyfile, but I set it up like shown here. My “DX8” button is the one I want to click (aka push and release) in order to do the “Close the airbrakes fully” command:
-
@jayb yep it’s a little obscure UX in Alt Launcher … to define a “onRelease” binding, click the button that says “Press” and it toggles to “Release”.
I should probably make that a proper toggle-button, eh
-
@airtex2019 Yeah, it’s kind of hidden but once you know Maybe mention it in the text where it talks about shift layer, although that is already a wall of text. UIs are hard !
-
@airtex2019 yes please, toggles in AL would be much appreciated.
-
@airtex2019 Good call, that incorporates what @Atlas is saying and removes most the chance for error! So horse is definitely dead now, I’ll take it if @boxer wants add a callback, but that should work too with more pressing things.
The magic of the on release option in AL is used on almost all my rotary switches and some of my DX based double throw switches since AL doesn’t away pick these up yet well. To me it’s not a UI problem, it’s an imagination issue of remembering you can do that, but maybe a toggle in the UI would help.
-
@Snake122 of course, point well made!
@airtex2019 ooohhh… you plebs with cheapo sticks!!
While that is a cool suggestion, you will have to keep the button pressed all the time for the brakes to work. If you map 1) AFBrakesOut and 2) AFBrakesOut, AFBrakesToggle, then you can keep the brakes open without holding the button and button 2 will guarantee a closed brake. Isn’t that better?I use the AL “Release” all the time with my 2-pos and 3-pos switches, that way a 2-pos switch only takes up one pin and a 3-pos switch only takes 2 pins! Whoever came up with that solution is an absolute genius!!
-
@Atlas actually @airtex2019 has the pleb stuff, the X65F is actually quite nice and all metal, gave the TM stuff a run for its money, just didn’t make a large splash in the market due to the force sensitive stick which of course is perfect for the Viper
His on release suggestion works great for me on a hat switch, open is incremental and a for sure close when I tap the open-to-close. Only trade off is that “close” does open at less a little and if I hold the “close” switch it does open further like normal. IIRC, AFBrakesOUT is fully out (I’ve been AL user since 4.35 so It’s been awhile with raw .key callbacks). I still want incremental out hence why I’m going with the AL “Brakes Open.”
-
@Snake122 I remember wanting the X65F due to that force sensing stuff back in the day but if it does not have a proper speedbrake switch implementation as you say, I find that quite interesting. I also remember really wanting the X45 back in my Allied Force flying days.
Of course, the final implementation of this would depend on user preference if a proper speedbrake switch is not available. That’s the beauty of toggle callbacks and switch state callbacks and programming software for our chosen HOTAS!