Cannot map an axis to Thrust since the patch

[RogueRunner]

As per the topic. Simply cannot map any axis to thrust. 

 

[RogueRunner]

Not just the F16 it seems, same with the Mirage F1 also. 

[BIGNEWY]

Hi some have seen this issue due to unofficial mods and also some have had to use the rescan devices option, or unplug the device and plug it back into the pc. 

thank you 

[Katalan]

Plug the throttle to another usb port. It solves it.  I did it and it worked. 

It happened to any plane/helo with single (AV8, F16,...) engine or the helo collective.

 

 

Edited July 12, 2024 by Katalan

[Deyth]

1 hour ago, BIGNEWY said:

Hi some have seen this issue due to unofficial mods and also some have had to use the rescan devices option, or unplug the device and plug it back into the pc. 

thank you 

I own almost every DCS module. It has nothing to do with mods. Rescanning doesn't work. 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".

Why did you overwrite everyone's values in "Thrust" and "Collective"? Whatever the reason, that's related to the cause of this bug.

[Scotch75]

I just chose JOY_Z or JOY _RZ as required from the drop-down menu in axis assign, and all worked properly (using TM Warthog throttle).

Cheers!


Sent from my SM-G998B using Tapatalk

[buceador]

For balance, I have the F-16 (and the X-56 throttle) and have not experienced any problems.

[LeCuvier]

I confirm that the axis previously bound to "JOY_Z" was either replaced by "JOY_RZ", or "JOY_RZ" was added to "my"binding to "JOY_Z"
for the aircraft modules listed below:

AJS-37
AH-64D Pilot
AH-64 CP/G
AV88NA
Bf-109K
F-15E had "Thrust" binding to "JOY_RZ" added to "my" bindings of Throttle Left and Right to "JOY_RZ" and "JOY_Z" resp.
F-16C
I-16
Ka-50
Ka-50 III
P-51D
Spitfire

It took my time again to correct these unwanted bindings and it's not the first time an update has overwritten my bindings.
@BIGNEWY this is not caused by mods. It's caused by a persistent glitch in the update process which does not "respect" the bindings I had set and which should be sacrosanct.
I understand that software bugs do occur even in the best development process; but I'm running out of patience with this totally unnecessary nuisance.

Edit: I have the TM Warthog throttle and I suspect that the problem is related to default bindings for that specific device which are defined somewhere I don't know where. People who don't have that throttle might not be affrcted.

 

Edited July 13, 2024 by LeCuvier

[Deyth]

1 hour ago, LeCuvier said:

I confirm that the axis previously bound to "JOY_Z" was either replaced by "JOY_RZ", or "JOY_RZ" was added to "my"binding to "JOY_Z"
for the aircraft modules listed below:

AJS-37
AH-64D Pilot
AH-64 CP/G
AV88NA
Bf-109K
F-15E had "Thrust" binding to "JOY_RZ" added to "my" bindings of Throttle Left and Right to "JOY_RZ" and "JOY_Z" resp.
F-16C
I-16
Ka-50
Ka-50 III
P-51D

It took my time again to correct these unwanted bindings and it's not the first time an update has overwritten my bindings.
@BIGNEWY this is not caused by mods. It's caused by a persistent glitch in the update process which does not "respect" the bindings I had set and which should be sacrosanct.
I understand that software bugs do occur even in the best development process; but I'm running out of patience with this totally unnecessary nuisance.

Edit: I have the TM Warthog throttle and I suspect that the problem is related to default bindings for that specific device which are defined somewhere I don't know where. People who don't have that throttle might not be affrcted.

 

 

I concur with everything you wrote although this was worse than just overwriting bindings because it also stopped responding to the hardware input. ED can can try "reset to default" on thrust or collective bindings with a Warthog throttle to repro this unwanted JOY_RZ overwrite.

[Raisuli]

1 hour ago, LeCuvier said:

I confirm that the axis previously bound to "JOY_Z" was either replaced by "JOY_RZ", or "JOY_RZ" was added to "my"binding to "JOY_Z"
for the aircraft modules listed below:

AJS-37
AH-64D Pilot
AH-64 CP/G
AV88NA
Bf-109K
F-15E had "Thrust" binding to "JOY_RZ" added to "my" bindings of Throttle Left and Right to "JOY_RZ" and "JOY_Z" resp.
F-16C
I-16
Ka-50
Ka-50 III
P-51D

It took my time again to correct these unwanted bindings and it's not the first time an update has overwritten my bindings.
@BIGNEWY this is not caused by mods. It's caused by a persistent glitch in the update process which does not "respect" the bindings I had set and which should be sacrosanct.
I understand that software bugs do occur even in the best development process; but I'm running out of patience with this totally unnecessary nuisance.

Edit: I have the TM Warthog throttle and I suspect that the problem is related to default bindings for that specific device which are defined somewhere I don't know where. People who don't have that throttle might not be affrcted.

Bindings, and the way DCS manages to make sure no two modules are the same and most of them are missing large numbers of them, are my number one gripe.  They then come though and 'help' us by re-assigning binding to devices and over-write what we've done.  This includes making us re-add the binding they can't be arsed to put in the modules to begin with.  Big reason I don't fly the A-10C; that thing is a disaster.  After two or three years of begging, and offering to give them the changes to the F-18 LUA file they added one.  One.  At that rate the A-10 will have a reasonable binding set some time after the sun goes nova and swallows Mars.

The F-16 and F-18 respond to the same physical control differently; one works great, the other not so much.  Consistency?  Who needs it.

This is not computer science.  It's not even hard; we're talking about a single text file (.lua) per air frame, and there are plenty of people in the community willing to help.  @LeCuvier is a genius with this stuff.  Consistency?  Different problem, and it's fundamental with ED.

As we used to say in the Navy if 2.5 (barely satisfactory) is "Recognizes correct answer when told" what is "Refuses to accept correct answer when shoved down throat"?

[Thamiel]

Just spent the last 2 hours of this otherwise beautiful morning with my VR googles on my face rechecking and remapping Thrust of my single jet modules. Helos and props are still waiting, though. Now, I'm pissed.  @BIGNEWY Seriously, is it really that hard for ED to keep their hands off my personal keybindings and mappings?

[Major Corvus]

I'm having this exact same issue, and for me it's totally random as to which module is effects. It's either thrust or collective that's effected and remapping the axis doesn't work, neither does rescanning or unplugging the device in question (TM Warthog).

The only fix that seems to work for me is exiting the game and reloading it, and that may or may not resolve the issue on a seemingly random basis.

It's becomming a a bit of a B ache

[Slippa]

The minute the update installed I checked my Spit and found the throttle busted.

Checking bindings I found the red exclamation mark and couldn’t re-assign the binding or get rid of it.

I found the same, either throttle or collectives were broken and spent hours going the long way about fixing them all. I’m using the Warthog too.

- Clear offending binding. Save profile (either way) and restart DCS. Go back to re-assign the binding, if it works, save the profile. 

I managed to get everything fixed but it took two long sessions to get through when I should’ve been flying instead.

 

[Rinze]

On 7/12/2024 at 7:06 PM, Deyth said:

I concur with everything you wrote although this was worse than just overwriting bindings because it also stopped responding to the hardware input. ED can can try "reset to default" on thrust or collective bindings with a Warthog throttle to repro this unwanted JOY_RZ overwrite.

It just happend to have the same problem as you today. I also have the TM Warthog. I did waht Deyth indicated an it works aganin thank you 

[Nialfb]

I recently noticed that I was unable to map most of the controls to my HOTAS throttle and joystick for the F-15C. Here's how I fixed it;

I went to the module settings and disabled/uninstalled the F-15C, this then required a restart. Once restarted I closed DCS. I then carried out a repair for DCS (see link below). I reopened DCS and re-activated the F-15C module, again requiring a restart. Once restarted, everything worked fine and I was able to map my controls to the HOTAS.

A useful link ... https://www.digitalcombatsimulator.com/en/support/faq/709/

I hope this helps.

[Nialfb]

BTW - Did this issue affect the backup of the control bindings? My backups seem unaffected. I carried out the repair as per the above and then reloaded my backup and all was well.