UH-60L v1.4 collective axis won't work.

[h3pilot]

I have the UH-60L v1.4 and the collective axis has stopped working.  (It had previously worked, but it has been a while since I've flown it.)

DCS control mapping shows the "collective" axis is still mapped to my Thrustmaster Warthog throttle, but there is a red circle with exclamation point next to the "collective" function name in the left column and also next to the mapped axis name under the throttle column of the same "collective" row.

When I move the throttle lever, there is no movement of the little axis indicator line that is under the mapped axis name in the box.

In the sim, the UH-60L's collective doesn't move.  I also see the same behavior in the SH-60B mod.

My mapped collective axis in the ED UH-1 and AH-64 are both working with my Thrustmaster throttle, so it isn't a hardware issue.

I'm assuming a DCS update has broken the collective axis in the Mods?

Does anyone know how to fix it?

[MAXsenna]

I have the UH-60L v1.4 and the collective axis has stopped working.  (It had previously worked, but it has been a while since I've flown it.)
DCS control mapping shows the "collective" axis is still mapped to my Thrustmaster Warthog throttle, but there is a red circle with exclamation point next to the "collective" function name in the left column and also next to the mapped axis name under the throttle column of the same "collective" row.
When I move the throttle lever, there is no movement of the little axis indicator line that is under the mapped axis name in the box.
In the sim, the UH-60L's collective doesn't move.  I also see the same behavior in the SH-60B mod.
My mapped collective axis in the ED UH-1 and AH-64 are both working with my Thrustmaster throttle, so it isn't a hardware issue.
I'm assuming a DCS update has broken the collective axis in the Mods?
Does anyone know how to fix it?

Those red exclamation marks, might indicate a conflicting axis assignment, though users, of various official modules, report the error from time to time. Try to clear out the mapping, and restart DCS. Bind it again, and check. If that works, fine. But if it comes back, you might have used another module, before hopping in the UH-60L. If a restart of DCS fixes it again, there's clearly some bug/conflict with some other module that uses the same axis, and you must use that workaround, and hope for an update.
Cheers!

Sent from my SM-A536B using Tapatalk

[h3pilot]

On 4/18/2025 at 1:22 PM, MAXsenna said:

Those red exclamation marks, might indicate a conflicting axis assignment, though users, of various official modules, report the error from time to time. Try to clear out the mapping, and restart DCS. Bind it again, and check. If that works, fine.

Clearing the mapping and rebinding didn't work, but I found that right clicking the cell and selecting reset default worked. 

That fixed the collective not working in the SH-60B and UH-60L mods and also the ED Mi-24 and KA-50.

The red exclamation in the mapped cell went away, but there is still one in the function title cell.

 

However, the reset default did not fix the collective in the ED KA-50 III.

[ghostmike]

Something must have been messed up with the last update! I can't use various aircraft in the editor, including the FA-18D, F-14, AJS-37 Viggen Draaken, etc. If these aircraft are included in the mission, they're there, but I can't redeploy them. Likewise, neither Combined Forces works!

[minar]

I have no problem with this mod on the recent dcs update and i use the UL-60L armed and both the SH-60 and MH-60R. Has to be on your end.