AB Detent customization

[Vakarian]

Can we get some sort of customization where the AB detent actually is?

I do get that we have the option of using the gates, but it really feels bad when the AB gate in-game doesn't match my physical controller and if I use those gates than there's always a bit of travel that's left unused.

Having to manually guess where it would be and setting the user curve on the throttle axis is really cumbersome and it's mostly guessing which leaves the throttle response to be "bumpy"

[Raven (Elysian Angel)]

Yes, I had to set "Saturation Y" to 80, same as what I have on the FC3 version.

[MAXsenna]

Very strange they just don't go the RB and Aerges route with their Mirages for all their modules.
While I guess they want it in the controls settings like they tried to implement a few years ago.

Sent from my SM-A536B using Tapatalk

[some1]

This really should be a global feature in dcs input system instead of the need to reinvent the wheel for each addon.

I usually add curves to axis to match my detents, but it's not ideal.

[Slice313]

I am adding curves to the axis to match my detents too, but I would rather have a linear progression... Please ED, add the option to configure the AB gate like other modules have

[Vakarian]

Using this https://www.digitalcombatsimulator.com/en/files/3315617/ I've managed to setup my detent for the WinWing Orion2 with F16 grip on it. The user curve for me looks like this

However, even if there are user addons for this, this is something that should be included in the special settings or in the control manager. There was that AB detent option "few" patches ago but it was removed as it was WiP and not functional. Can you guys please dedicate a dev for this? It is an option needed for more than just Fulcrum

[Lexikdark]

This is more of a Wishlist item that I think would be great for the Fulcrum or any of the Mig/SU's in DCS special tabs. 

I would like to have the ability to tweak the throttle range in the Fulcrum Special tab so I can use the full range of my throttle instead of using the other half of the first half of my throttle before I'm in full AB. 

as well as a AB gate switch in the keybinds menu, that allows me to just not go into AB unless I push the button (though I have no idea if that's realistic or not since I've never flown a real aircraft once in my life, let alone a Mig-29.) 

My reasoning for wanting one or both of these options, is that it lose a lot of immersion when I barely move my throttle and I'm in afterburner. and getting a good feel for it is much harder as well.



 

[Vakarian]

 

[Raven (Elysian Angel)]

4 hours ago, Slice313 said:

I am

You are?
 

[Sryan]

3 hours ago, Vakarian said:

Using this https://www.digitalcombatsimulator.com/en/files/3315617/ I've managed to setup my detent for the WinWing Orion2 with F16 grip on it. The user curve for me looks like this

However, even if there are user addons for this, this is something that should be included in the special settings or in the control manager. There was that AB detent option "few" patches ago but it was removed as it was WiP and not functional. Can you guys please dedicate a dev for this? It is an option needed for more than just Fulcrum

Why do this? I also have a WinWIng Orion 2 with F-16 grip but I set up my Afterburner detents in the SimApp software like this:

 

Edited 15 hours ago by Sryan

[Vakarian]

Huh, I didn't even know that was possible. Thanks, I'll play with that as well.

However, relying on 3rd party apps or tools shouldn't be required to get throttle usage as expected.

[MAXsenna]

6 hours ago, some1 said:

This really should be a global feature in dcs input system instead of the need to reinvent the wheel for each addon.

I usually add curves to axis to match my detents, but it's not ideal.

Yes, absolutely!

And like I wrote they were going that route. Don't you remember after an update we suddenly had a checkbox and slider, (don't 100% remember how it looked), in the axis settings that said afterburner detent (or something). Of course there were complaints when it didn't work because, it wasn't implemented yet, and was removed a few updates later. That's at least two years ago. Maybe the one dev working on it quit?