reported Adding bind in UI Layer says many 'Currently in Use'. But they are not in use...

[Snacko]

I've checked several of these 'Currently in Use' conflicts in the UI Layer, by checking each individual aircraft.  None of them are real.  There are no conflicts with other binds to the same control.  (And I am not talking about the Red x warnings in some controls.)

I've recently used JoyPro to assign all of my binds, and it's an amazing tool, and worked wonderfully.  I have validate all of my binds, and there are no conflicts. And this only happens in the UI Layer.

Does anyone know how to fix this?  In the UI Layer, when you assign a bind, it loads all of the other aircrafts binds to check for conflicts.  But it's reading something wrong.

[Flappie]

Please make a zip of your Saved Games/DCS.../Config/Input folder and attach it here. I'll see if I can reproduce your issue.

Edited May 31, 2024 by Flappie

[Snacko]

Thanks, it's attached.

It includes the .jp files that JoyPro creates.  I moved them to another folder after zipping and tested again.  It didn't make any difference.  It only happens in the UI Layer..  And each time I restart the game it has different conflicts for the same buttons that I have tested.  Really weird..

I'm going to do a repair and see what happens.

Input.7z

[Flappie]

Thanks. Let's see what we got:

In AH-64 pilot WinWing throttle base1 + F18 handle:

		["d3012pnilu3012cd25vd1vpnilvu0"] = {
			["name"] = "Symbology Select Switch - Up",
			["added"] = {
				[1] = {
					["key"] = "JOY_BTN23",
					["JPK"] = "Apache -Symbology Select Switch - Up",
					["JGRP"] = {
						[1] = "GENERATED-NAME",
					},
				},
			},
		},

In VSF_NF104A WinWing Throttle base 1 + F18 handle:

		["dnilp141u230cdnilvdnilvpnilvunil"] = {
			["name"] = "Scan Zone Up",
			["added"] = {
				[1] = {
					["key"] = "JOY_BTN23",
					["JPK"] = "Common -Radar Elevation UP",
				},
			},
		},

In Su-33 WinWing Throttle base 1 + F18 handle:

		},
		["dnilp141u230cdnilvdnilvpnilvunil"] = {
			["name"] = "Scan Zone Up",
			["added"] = {
				[1] = {
					["key"] = "JOY_BTN23",
					["JPK"] = "Common -Radar Elevation UP",
				},
			},
		},

I stop here.

I agree with DCS: this JOY_23 button is already used in many aircraft.

[Snacko]

Thanks for the reply Frappie!

I forgot to mention which controllers the conflicts were on.  I didn't include that in my original screenshot.  But it was either the WW Combat panel or the Take-Off 2 panel.  So, when you look for the conflicting bind, you have to look at the correct control for the aircraft in contention.  So, let's start over..  

Here I try to assign the JOY_BTN37 on the Combat Panel, and it shows Gear binds on about 20 other aircraft 
(but you can only see 3 in the screenshot.  I couldn't get a screenshot, or copy of all of the ac.  DCS erased it when I pressed ctrl+c, the tooltip disappeared when I took screenshots.)

And the bind is not in the Combat Panel's diff.lua files for these aircraft, so there's no code to show you..  

I did a DCS Repair on 'ALL Files'.  It took about 20 minutes.  Still no Joy..  

It strange that the Same button number is on the Takeoff Panel..  There's got to be something to do with that.  But here are the two filenames in the Mig21 joystick folder:

WINWING F18 COMBAT READY PANEL {3C2398C0-75AA-11ee-8010-444553540000}.diff.lua
WINWING F18 TAKEOFF PANEL 2 {3C232390-75AA-11ee-800E-444553540000}.diff.lua

 

 

[Flappie]

Thanks, it's way easier that way. Let's use the very first warning: MiG-21 Gears Down

I found the JOY_37 button assigned this command in the "WinWing F18 Takeoff panel 2", as shown in your screenshot, so DCS is wrong in this case, indeed.

		["d3121pnilunilcd14vd-1vpnilvunil"] = {
			["name"] = "Gears Down",
			["added"] = {
				[1] = {
					["key"] = "JOY_BTN37",
					["JPK"] = "TOP2 -Gear Down",
					["JGRP"] = {
						[1] = "Flight Controls",
						[2] = "IL2",
						[3] = "DCS",
					},
				},
			},
		},

I'll try and reproduce this on my end, and I'll let you know what I find.

[Flappie]

Issue reproduced a reported.

Thanks for the heads up, @Snacko.

[Snacko]

Yes sir..  I was wondering if it had something to do with MT vs ST..  I was testing in MT all of the time.  But then I tested in ST and it seemed different.  Hard to tell without intense focus..  I'm 65, and don't have it like I used to..