P-51D throttle assignment ignored as of 2.9.6.57650

[Deyth]

After today's update, the throttle assignment for the P-51D simply doesn't work. Moving the throttle (joy_z and/or joy_rz) is not registered by DCS. So far this only seems to be happening for the P-51D. I tried the P-47D and no issues. I cleared and remapped but same thing. The joy_slider1 mapping for the throttle works fine. Anyone else experiencing this?null

[ThorBrasil]

1 hour ago, Deyth said:

After today's update, the throttle assignment for the P-51D simply doesn't work. Moving the throttle (joy_z and/or joy_rz) is not registered by DCS. So far this only seems to be happening for the P-51D. I tried the P-47D and no issues. I cleared and remapped but same thing. The joy_slider1 mapping for the throttle works fine. Anyone else experiencing this?null

I'm also having this problem on F-16, Kiowa, Ka-50, Mi-24P. I didn't see all my modules. I use a Thrustmaster Hotas Warthog. The DCS version is MT.

Edited July 12, 2024 by ThorBrasil

[MAXsenna]

I'm also having this problem on F-16, Kiowa, Ka-50, Mi-24P. I didn't see all my modules. I use a Thrustmaster Hotas Warthog. The DCS version is MT.

Seems it's got something to do with certain hardware. My old TM Cougar had no issues in the Viper. While my K-51 collective was reset from slider and inverted to default. And the Warthog had lost bindings.

Sent from my SM-A536B using Tapatalk

[Deyth]

I also have a Warthog. I’ll have to check all my airframes. This release is a disaster.

[Slippa]

It’s the first thing I noticed yesterday after installing the ‘carnage update’.

The Spitfire throttle was busted. I couldn’t re-assign the binding until someone, might’ve been TerryDactil suggested restarting DCS after clearing the existing broken binding. I did, then I could re-assign the binding and it’s fixed. Try that.

I did a quick scan in a few other modules, Mossie seemed fine, Jug too but I think the Pony had problems too. Missing collective bindings in the OH-6A and was about to check the Kiowa when I had to eat. I’m wondering whether to bother going through everything trying to clean up the mess the update’s done or wait for them to fix it. I have a lot of modules.

Even if I do one a day it’ll prolly be quicker than any ‘hotfix’. 

Warthog HOTAS - MFG Crosswinds - distinguished extinguished piloting on instincts 

Edited July 12, 2024 by Slippa

[Deyth]

I'm still going through all my airframes. My first observation is that anything using the "Thrust" or "Collective" axis is busted. ED overwrote whatever was in there with "JOY_RZ;JOY_Z", no slider, and it simply doesn't work. Airframes that have "Throttle" work. Airframes that have "Thrust Left/Right", like the F-15E, will work as long as you remove the values ED inserted for "Thrust".

[Dogman]

So I have had similar issues to the ones posted in this thread. In my case 13 modules were affected including some jets and prop planes no helicopter modules were affected. In all cases where two thrust binds were available it was always the left thrust bind that had the conflict issue. In a modules where only one thrust bind was available it was the only bind that had the conflict.

 

Thankfully what was looking like a big problem was easily resolved by clearing all conflicted binds noting that the red exclamation badge still showed against the affected bind and a new bind reassignment would not be accepted. I then closed DCS and restarted and found to my great relief that all the red exclamation marks had now gone and I was able to reassign all thrust binds correctly verifying that they worked in game. 

Bullet dodged... PHEW!!!!

[SchumiF399]

Same for me F16 throttle broken, windows sees the axis fine.

[sch_tec_crew]

came back to DCS after several months to fly and enjoy warbirds and couldn't because of this issue. Also using warthog hotas..<profanity> it, I'm tired to troubleshoot this crap.