Windows Joystick ID re-mapping

[Dojo]

Anyone know how to modify the Joystick ID number that Windows assigns to your physical sticks? (sets the order you see in the joy.cpl)

Surprisingly difficult info to find on the Interweb, hoping one of you have had to tackle this before.

[JayPee]

Ehm.. Disconnect all, then reconnect in the order you want them to show up?

[Dojo]

Ehm.. Disconnect all, then reconnect in the order you want them to show up?

No, thanks for the response, but no guessing please. If you don't know, that's fine.

[Badger]

You can use the Target Script Editor and run a script to effectively make windows recognize both the stick and throttle as a single controller, would that be of any help?

[Dojo]

You can use the Target Script Editor and run a script to effectively make windows recognize both the stick and throttle as a single controller, would that be of any help?

Unfortunately not. That sounds like it might produce a virtual joystick. (like vjoy). Whether it did or didn't, the issue I'm having is because I can't definitively set 4 of my joysticks as the first 4, which I need to in order for CryEngine games to recognize them (currently Star Citizen).

What you're describing would effectively give me another joystick, a combination of two or more, which would make the problem worse I'm afraid.

[StiC]

Hey Dojo,
There is a little tool called JoyID which might help you.
I haven't used this myself and I believe it supports the Win32 API, but it could be useful depending on what you want to accomplish.

[Dojo]

Indeed... sounds like the exact solution I was looking for, hopefully it's compatible. Will test in the near. future

Thank you!

[StiC]

I came across another one this morning. This one seems to create another virtual joystick though, so it might not help much.

[Dojo]

This is interesting. It's ok if creates another stick (virtual) if it lets you assign the physical stick ID, which the GUI appears to do. If I combined all joysticks into one virtual stick, and that one stick was recognized consistently as Joystick #1, problem solved.

I did some extreme registry hacking to prevent windows from changing the joystick IDs, which feels fragile, though it's been working for now.