Disable Throttle Cutoff Detent or set to 0

[EbonySeraphim]

I'm using a Vipril CM3 with a stop-idle detent that presses buttons as I move those axes up. Once I've moved past those "buttons", and full push down, that position is what DCS sees as "0" for the throttle axes in game. This setup works great for all fixed wing aircraft except the F-15E because (I suspect) of the special settings "Throttle cutoff detent" option. The lowest value I can set it is 3, and I cannot turn it off. I'm guessing this means that the module will see a throttle value lower than 3% and registers it as the throttle lever being set to idle, which is absolutely not what I want. Is there any way to disable this so I can pull full back on my detent without shutting the engines off?

 

I'm absolutely sure this isn't actualy the IDLE or STOP button/binding being triggered because the detent is firm, and it's been well tested and long used for multiple modules. It's never shut down the A-10C or F/A-18.

[MAXsenna]

Can you post a picture of how you have mapped it in the controls settings?
My Warthog works fine in every relevant module. But what is does, is press a physical button for getting into cutoff, (on), while releasing the same button to get into idle, (off).
Cheers!

Sent from my SM-A536B using Tapatalk

[Ramsay]

4 hours ago, EbonySeraphim said:

I'm guessing this means that the module will see a throttle value lower than 3% and registers it as the throttle lever being set to idle, which is absolutely not what I want.

Not AFAIK, at 3% or less the in game throttle(s) will be at idle.

4 hours ago, EbonySeraphim said:

Is there any way to disable this so I can pull full back on my detent without shutting the engines off?

The engines do not shut off because the throttle(s) are at "idle", they shutoff when the "finger lift" button(s) are depressed (held down) and the in game throttle(s) move to the "stop" position.

It's sounds like you've already triggered/depressed the finger lift buttons before you've reached the "idle" 3%, so on reaching "idle" - the throttle then moves directly to the "stop" position.

This is my Winwing setup

And a video from Casmo of how it works in game @2:58

https://youtu.be/OOHb-uXLwUk?si=szdD8XrLdb1Ey0PP&t=178

 

Edited November 5, 2023 by Ramsay

[jaylw314]

8 hours ago, Ramsay said:

Not AFAIK, at 3% or less the in game throttle(s) will be at idle.

You posted multiple times, your browser is probably slow

11 hours ago, EbonySeraphim said:

I'm using a Vipril CM3 with a stop-idle detent that presses buttons as I move those axes up. Once I've moved past those "buttons", and full push down, that position is what DCS sees as "0" for the throttle axes in game. This setup works great for all fixed wing aircraft except the F-15E because (I suspect) of the special settings "Throttle cutoff detent" option. The lowest value I can set it is 3, and I cannot turn it off. I'm guessing this means that the module will see a throttle value lower than 3% and registers it as the throttle lever being set to idle, which is absolutely not what I want. Is there any way to disable this so I can pull full back on my detent without shutting the engines off?

 

I'm absolutely sure this isn't actualy the IDLE or STOP button/binding being triggered because the detent is firm, and it's been well tested and long used for multiple modules. It's never shut down the A-10C or F/A-18.

In the F-15E you have a bunch of options:

You can use these as alternatives to the slider setting.   If you set the IDLE and OFF bindings to buttons, it will prevent the slider from controlling the engine state, AFAIK.  Note that depending on the joystick, you can set IDLE to buttonX and OFF to buttonX_OFF or vice versa

[EbonySeraphim]

EDIT: @Ramsay what you said makes me wonder and want to test something. My finger lift bindings are non-momentary switches. Maybe I'm experiencing these problems because the finger lift binding for that engine is being held down the entire time. I'll try pressing and releasing and maybe I get different behavior.

I was probably being misleading, and allow me to be a little nit picky -- it is during startup that I'm having problems. After raising the finger lifts, when I need push into IDLE the following happens with my CM3 setup:

1. The throttle axes at rest in the STOP detent is holding down on the "STOP" DCS binding; DCS sees 0% (technically below) on the throttle axes
2. I start moving the physical throttle into "IDLE", which will settle the DCS axes at 0
3. Along the way, the physical axes moves to a position that comes off of the STOP button binding and activates the IDLE button binding
4. Along the way, the throttle axes DCS sees will register above throttle = 0 as I push past the detent (probably over 3% but I haven't checked) because of the shape of the detent
5. The IDLE button binding will turn off BEFORE I've pushed past the detent
6. When I'm fully past the detent and pull back fully on the throttle, DCS sees throttle = 0 again

Given this setup, during startup when asked to push into IDLE, when I physically pull back on the CM3 throttle such that throttle = 0 again, in game it disables the IDLE setting and goes back into STOP. I can see this happening in the in-game cockpit. I don't know if there's scripting around the 3% such that because I'm pushing past it, and then dipping below it during start up, this is happening. I'll double check but I think this (engine shutdown) does not happen mid flight if I pick a free flight mission.

Maybe these words aren't clear and I have to post a video. If not for my monitor/MFD setup making the controls indicator difficult to grab, I could trivially do this immediately. I'll give this a day or two for suggestions. Part of the understanding is seeing the physical action; I'm quite happy with how I have the CM3 setup for all modules, and what I'm doing seems extremely straight forward and should be reasonably expected and supported.

Edited November 5, 2023 by EbonySeraphim

[LazyBoot]

Are you letting go of the finger lifts after you've passed the detent?

[EbonySeraphim]

This was my issue. My binding was on a physical switch that held the button down the entire time, so I guess that also allowed the throttle position being zero to pull things back from idle in game despite the IDLE button not being pressed. I tested/verified last night but forgot to update until now.