Hide duplicate useless Wooting Two HE (ARM) controller

[pulsar hound]

Hello all,

How can we hide/remove the multipe Wooting Two HE (ARM) controller that appears ingame when using the controller function of the keyboard ?

we should normally only have one visible from a game.

[pale lava]

Thanks for posting your support request!

Note: #community_support is only for answering general questions and for troubleshooting.
All order-specific and shipment-specific support must be handled via the Wooting Support Wizard*
(You need to create an account on the Wooting Hub, using the same email address as your purchase. The account is not created for you automatically!)

Troubleshooting your Wooting Keyboard? Try these steps first!
Basic Troubleshooting

Questions about shipping, or what to do if your shipment has a problem?
Possible Problems During Shipping (with Solutions)

Looking for information about your specific order?
You can find that on the Wooting Hub! There you can also add upgrades, update your shipping address, and much more.

Is your order about to ship and you need to pause it for any reason?
Place it on hold via the Wooting Hub!

Do you need to...

• Cancel an order?
• Return/Refund an order?
• Get assistance with placing an order?
• Change the items in your order?
• Change your shipping address to a different country?
• Return a recent purchase?
• Get warranty support?

All of these types of requests need to be made via the Wooting Support Wizard!

[grizzled gulch]

It is due to propably classic controller

[pulsar hound]

What does that means ? Actually my gamepad setting in wootility is set to xbox, not classic controller.

[grizzled gulch]

Still. Four controllers only appear if you use classic controller mode

In xbox only appear ond

[pulsar hound]

I confirm this is not the case :

[grizzled gulch]

X input is classic controller

[coarse lava]

its not

@choum you may got hit by an ancient bug that we fixed in newer firmwares where windows really liked making new controller entries sometimes.

you can get rid of then by just deleting them fron device manager and making sure you enable showibg disconnected devices under the view option

[pulsar hound]

@coarse lava I'm using firmware 5.1.0-Beta3 actually. Can you be a little more precise concerning device to remove under device manager ?

look like wooting is using VID 31E3 and PID 12XX

So the procedure to remove duplicate gamepad entries is :
Disable gamepad mode on the keyboard.
Delete all entrie in device manager with VID 31E3 and PID 12XX
Delete registry key used by joystick
Re-enable gamepad mode (X-box)
and I should now have only one device, correct ?

[pulsar hound]

I delete everything in usb entry related to wooting keyboard (keyboard unplug and gamepad disabled just before)

as soon as I replug the keyboard and re-enable xbox gamepad emulation all 4 controllers are back and visible in some game.

[coarse lava]

@jagged wolf you might have an idea as you have dealt with similar stuff before

[jagged wolf]

There is a mixup of different things here.

1. Depending on the analog mode of the Wooting it will register different device set in the Device Manager / Registry (the last two digits of the product ID depend on the analog mode). That is normal and intensional to ensure compatibility and allow that custom settings can be applied per analog mode.
2. We don't recommend to use the tool USBDeview as this can lead to phantom entries. If you uninstall the composite node of the Wooting the child notes aren't deleted which can results in phantom nodes which are maybe applied incorreclty which can cause weird issues. Like weird or no keyboard inputs.
3. Win doesn't like if a device is not just a controller. Win assigns a joystick ID to the controller interface and so the interface order is important, but sadly the interface order for DirectInput isn't constant and can change every now and them. This can lead that an interface which isn't a controller can get an joystick ID and a game which doesn't properly validates that the interface is actually a controller might show more controller than there are. This can also happen for the Xbox controller as Win creates a classic controller interface for backward compatibility. Uninstalling the device doesn't fix this as the joystick ID is stored in a differently place of the Registry.

So best to don't use USBDeview unless you know for sure what you are doing and how that works.

To deal with the bad joystick IDs these need to be deleted. Wooting had a guide for this but sadly that is no longer available. You can still access that via the Wayback machine (https://web.archive.org/web/20230923200134/https://help.wooting.io/en/article/issue-too-many-gamecontroller-devices-detected-n4efgy/). But the Registry file for just the Wooting devices is outdated and so don't contain the entries for the newer products. So it's the best to use the fix all file, but that deletes all controller settings for all devices, so not just the joystick IDs for the Wootings. Meaning it will delete any calibration or custom setting which got applied to every joystick or gamepad.

If you don't want to lose the custom settings you need to check the Fix_Wooting_Joystick_Calibration file and ensure that it contains all the paths for your Wooting.

You also likely need to apply these every now and them as the OS can scramble up the interfaces again and so likely reapply bad joystick ID at some point. Sadly it seems MS doesn't really anymore about DirectInput.

[pulsar hound]

Hi, the problem is different that the one in your link, I do not have duplicate joystick in joy.cpl, but some game still see multiple wooting controller . Below another example with MFS 2020

as soon as I disable gamepad mode in wootility, gamepad "manette" and all 4 "fake" controller are gone.

[jagged wolf]

What game is this?
Have you tried the fix all patch I provided via the link?

Even the Win Game Controller panel might show the joysticks correctly doesn't mean that the game don't run into this issue. As mentioned above some games handle such issues better than others.

If I understand you right you are using the Xbox mode. So please also try to disable the virtual game controller behind the Xbox controller in the device manager. Best to first find the Xbox node and then change the view to connection. Then you should see the virtual DirectInput game controller from that.

[pulsar hound]

Hello, the game in the capture is Microsoft Flight simulator 2020, Star citizen also have the problem (worse because it can mess up joystick order for this game).

I tried to disable the node, if I made no mistake with your instruction is this one

problem after disabling it : I lost the Xbox gamepad and only have the 4 ghost controllers. What we want is the opposite.

[jagged wolf]

That means that the issue is likely related to the problem with the DirectInput devices I described above. Meaning if you would run the fix all Registry patch it should work. So have you actually tried it as suggested?

As your Xbox controller no longer appears in the game when the virtual DirectInput controller of that is disabled it means that the game doesn't even seems to support XInput (the native Xbox controller support). As mentioned a Xbox controller has a virtual DirectInput controller for backwards compatibility. Because of this feature any game which supports XInput must ignore the DirectInput controller of that device to avoid the problem of seeing multiple controller.

So as the game only seems to support DirectInput it also means that it can have the joystick ID issue. Also the problem you descripted sounded like that.

[pulsar hound]

Hello, I just tried the registry patch that remove everything below and reboot the pc

HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties

HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaResources

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\MediaProperties

Now, I correctly see only the gamepad in MFSX 2020, steam, and star citizen, for this one, the 4 wooting controller are not visible/detected anymore as Joystick.

Before

After

Thank you