Custom, per-plane throttle mapping for fixed afterburner-detents.

[1Sascha]

Forgive me if this can already be achieved with what we have, but even if it can, I think a simpler solution would be nice to have.

 

Until VKB finally come out with their digital detents, those of us who have throttles with afterburner-detents are a bit SOL WRT combat/emergency switch-over - at least in LW planes, can't comment on Allied crates cause I don't fly them..

 

 

I had my Virpil CM3's upper detent set to 80% in-game throttle... which works great for the 109s, but doesn't really work with 190s. 80% in the A-3 to A-8 is continuous and 85% is max combat power. When I have my physical detent set to 80%, this means I can't really set the throttle to combat power, because if I push past the detent and to 85%, the physical throttle will start to "wander" forward on the detent and push itself into WEP-territory.

 

Annnnyway, my idea is this:

Have a per-plane setup-option that will let the player set the point at which the in-game throttle goes from combat to emergency power. Kinda like a calibration-dialogue:

 

"1. Pull your throttle all the way back and press X

2. Push your throttle to the point you want to define as "max combat power" and press X                 <--- meaning push it into, but not beyond, the AB detent of your throttle

3. Push your throttle all the way forward to "full throttle" and press X."

 

Done.

 

That way guys with detents could just push the throttle into the AB-detent, define that spot as max combat power. Do that for every plane you fly regularly and you don't have to physically adjust your detent and/or mess with axis-tuning in the throttle's SW.

 

 

S.

[Youtch]

You can set up a profile per plane in Joy2key.

 

It allows you to define the threshold without moving the detent position on cm3.

[1Sascha]

10 hours ago, Youtch said:

It allows you to define the threshold without moving the detent position on cm3.

Well... don't stop there. How do I do that?

 

I've tried messing with throttle-axis deadzones in the IL-2 mapper already but couldn't get the results I wanted that way. And other than upper and lower deadzones, I didn't find anything obvious that would allow me to adjust the in-game throttle's behavior.

 

Also: Is there a convenient way to copy a controller/keymapping profile? I have a *ton* of buttons mapped and I don't want to re-map all of that every time I set up a custom profile for a specific plane.

 

I still maintain that a dialogue-based feature as described in my first post would probably be the better way around this. Should take, like, one minute to set that up for each plane, instead of having to do all this stuff "manually" and possibly having to re-map everything else.

 

 

 

S.

[Youtch]

Check this:

The post from Fenris in the first page

[JG27*PapaFly]

IRL many planes had detents or gates,  but that's difficult to implement via hardware, because the different planes had very different systems for this. Also, I don't like detents that take you to max power as soon as you pass them.  Some planes give you considerable longer WEP time if you only go to 90- 95 percent.

 

I solved this for me by programming purely digital detents via AutoHotkey. As an example,  when I hit max combat power in the 190A series, a chime soundfile is played. At max combat power, I hear a double chime. This is super handy,  especially when the technochat disappears, which still happens very often. I think this would be a great thing for the devs to implement, and quite simple and effective.

[1Sascha]

On 7/30/2023 at 4:31 PM, Youtch said:

The post from Fenris in the first page

Well... yes... but that's with the help of external "crutches". I use Joy2Key myself for a number of reasons, but I'd rather have my games include this sort of stuff. Having to resort to external applications and setting up response curves, etc. shouldn't be the go-to solution.

 

I also suspect I could use VPC's software for this sort of stuff (I know I've done it to get an engine start-up/cut-off behavior from my lower detents), but that would require more work and fiddling with external profiles, curves, etc. plus switching my controller's profile every time I switch planes in-game.

 

IL-2's keymapper really could use an overhaul anyway, and I do hope once we get that, they will implement something akin to what I described in my first post. Doesn't seem too complicated to include and it would make things a lot easier for lots of users.

 

Plus in the case of the 109s at least (don't think I've managed to "MW-50-damage" a D-9's engine yet), this would really be helpful to prevent engine-deaths via operator error.

 

Having to dig into your stick's/throttle's controller SW and/or and third party app and to learn how to set all this up really shouldn't be required any longer in 2023.

 

S.

Edited August 2, 2023 by 1Sascha