Request: Ability to specify throttle range & afterburner limits per aircraft.

[TEMPEST.114]

I have the warthog throttle with the afterburner detente physically set.

 

I would like a special control bindings section where I am presented with a wizard asking me to click next at the following throttle positions, and it will memorise them, per aircraft;

 

1, idle cut off (per engine)

2. 0% (per engine)

3. 100% (per engine)

4. Zone 5 afterburner (per engine)

 

then the 0-100 potentiometer of each engines throttle will perfectly match up with the dcs aircrafts flight model. 
 

the current hack by playing with dead-zones and curves and saturation isn’t clear, simple or works well.

 

this would probably be about a days work to implement but would be a huge boon for every single player. 
 

please consider it. Thanks. 

[cfrag]

Can't your stick's software do that for you? Or a joystick helper utility like Joystick Gremlin or Voice Attack? That would be the correct place to synthesize general control input.

[Tippis]

3 hours ago, Elphaba said:

the current hack by playing with dead-zones and curves and saturation isn’t clear, simple or works well.

While it would definitely be a nice addition for ease-of-use to have that kind of automated wizard, I'd just like to mention that if you're playing with those, you're making the whole lot harder than it needs to be. Using a custom-curve slider, there are no dead-zones, curves or saturation to deal with (or well… there are, but they serve no purpose) — just different throttle positions and how they map onto the in-game throttle.  Just set the (usually) 70% position (4th from the left) to the accurate AB threshold (usually 15–20), and then linearly populate the other positions from there out to 100 and back to 0.

 

A wizard would be helpful to auto-populate those values, but the underlying functionality would be just that. It's simple, non-hacky, and works well, but yeah, it lacks a bit in the clarity department.

 

[MAXsenna]

I have used Bailey's and "hisnameescapesme's" AB calculator to great success.
But OP is not the first to ask for this, and it's very well implemented in that other old Viper sim.

Sent from my MAR-LX1A using Tapatalk

[TEMPEST.114]

Hi. Yes I've tried doing the user curve. It's horrible, inaccurate and changes the curve from linear everywhere else. It's not good enough.

 

I appreciate other people have been asking for this - that's good that there's some consensus, however why has this still not been implemented, especially with that older 'viper sim' does it so simply, beautifully and accurately?

 

I know the devs must feel pulled in so many different directions, but at some point they have to start bringing things up to a better standard rather than keep adding new modules. No? The binding system is very unfriendly. Especially when you have to find the binding setting, set it, and test it but if you need to go back and correct or change if you aren't back into the last binding you chose, but back at the top level all over again. This is particularly a problem when setting / testing the user curve.

I hope some dev sees this thread, or are they too busy?

[Nomatic]

+1 - would greatly appreciate

[Tippis]

On 9/10/2021 at 4:18 PM, Elphaba said:

Hi. Yes I've tried doing the user curve. It's horrible, inaccurate and changes the curve from linear everywhere else. It's not good enough.

How do you mean? It's as linear as you make the numbers. There's maybe a very slight bend in the kink created by the AB position, but on both sides of that position, the response is as linear as needed and you'd be hard-pressed to notice any variation.