Release MultiJoystick Tester

robbyp

robbyp
This tool shows all your attached USB devices on one screen, with their button states and axis values:

1632145075175.png


This was developed to support the Elite Dangerous Discovery Project. It may be useful for you to debug any joystick issues, it certainly was for me, especially with Microsoft flight simulator 2020.

As you plug in/out devices, the list of devices automatically update to suit.

I also use this just before I run Elite, to make sure that all the devices are there before you start. This is especially important for some thrustmaster scripts where it does not always work first time.

MultiJoystick Tester source code can be downloaded from here. and compiled using visual studio 2019.

This is an free open source project, you can inspect the code at github. No code is hidden. All is available for you to build or inspect. We welcome contributions to the code base and user reports of any issues, either at our discord or via Github issues.

This software uses the Apache V2 license and is (C) Robbyxp1 @ github 2021. It is provided without warrantee and with no liability, as per the license.
 
Last edited:

Clicker

Clicker
Did not see this previously.

Nice tool.

Having a WARTHOG + TARGET script, I too had the issue whereby the game intermittantly starts but the joystick or throttle were not recognised.
(firmware issue for sure!)

Cheers
 

robbyp

robbyp
I've found, both thrustmaster scripts, and also my ch pro control manager script, are very fickly about starting properly.

I wrote this tool because I kept on using the built in USB controllers dialog, but it only showed one darn stick at a time. And I use three for Elite (Ch pro throttle with control manager script, T16000M, and a game controller) and wanted to see what was happening to all of them and they were all working.

Its also very useful for my new MSFS setup (Honeycomb Alpha Yoke, Bravo Quadrant and CH Pro Pedals). Made setting up the control scheme in MSFS easier because i could double check the device was working.

BTW you can run this at the same time as any game - Windows allows this.
 

Para Handy

Para Handy
Thanks for this, seems very useful. - Just one thing - I know they are not joysticks but My Cougar MFDs don't show, not important.

CHPro Fighterstick, Throttle and Pedals all report in correctly as does the wired xbox 360 controller:

multijoy.jpg


One other thing, again not joysticks just buttons and switches, but logitech flight panels (radio and multi) don't show up either although it seems to be polling the radio panel. Again, this is not an issue, just pointing it out. ( It doesn't see the FIPs either but that is not surprising as they are a different beast altogether. )
 

robbyp

robbyp
Interesting info.

The code enumerates all DirectX devices from the GameControl class, then finds all axis and buttons on that device.

I'm not sure which class the logitech flight panels are, as I don't have one.

If anyone can build the joystick SW we can experiment to find out...
 

Lombra

Lombra
I believe the flight panel stuff uses some proprietary protocol that needs to be implemented directly by client applications.
 

robbyp

robbyp
I guessed it would be something like that, because the visual feed back is not a HDI thingy, so you would need a custom driver for it.
 

robbyp

robbyp
I now have a radio flight panel, and its not a standard HID jpystick device, or any other device type that looks like a joystick, hence it does not show up
 
You must log in or register to reply here.
Back
Top Bottom