[Montellese]

I also tried to get my NES30 controller to work but didn't see any recognized input.

If the controller doesn't support XInput it should fall back to DirectInput. This can also be tested with XInput controllers by removing this line: https://github.com/kodi-game/peripheral....s.txt#L113 (controller will fall back to DirectInput) . Does the controller get detected in the debug log?

Looking a bit at the joystick code is it possible that the following log message from CJoystickInterfaceDirectInput::EnumJoysticksCallback() is the reason why this (or any other) controller might not be detected with DirectInput:

Code:

AddOnLog: Joystick Support: ********** HWND: 00000000

Because the code then returns early even though pdidInstance contains information that looks correct like the name being "Bluetooth Wireless Controller" (which is what I see in win7's game controller window.

NVM: That only happens at the beginning (probably because the window doesn't exist yet during boot). The next scan works but it then throws an exception when trying to initialize the discovered joystick. Will investigate further.

EDIT: OK I think I found the issue. At https://github.com/kodi-game/peripheral....ut.cpp#L84 you first copy all the detected CJoystickDirectInput pointers from m_scanResults into the joysticks output parameter (see https://github.com/kodi-game/peripheral....ck.cpp#L32) and then you clean up m_scanResult by deleting every CJoystick pointer it contains but since you previously copied those pointers to another vector you just destroyed the objects that you are later trying to initialize.

Removing the logic that deletes the pointers in m_scanResults gets me further and the joystick is successfully initialized but during the next scan it is recognized again and initialized again and then Kodi freezes.

EDIT2: Looks like a deadlock between the main thread in CPeripheralBusAddon::GetPeripheralsWithFeature() and the thread responsible for scanning for new devices which is stuck at CPeripheralBusAddon::UnregisterRemovedDevices() callin CPeripherals::OnDeviceDeleted().

EDIT3: And the reason why the controllers that are constantly detected never match the ones that have previously been detected is because the call to CJoystickDirectInput::Initialize() which is performed later changes the button, hat and axis count but the comparison is done between an uninitialized and an initialized CJoystickDirectInput object which will most likely always fail.