[chiefwigms]

I'm having an issue (just updated from Jarvis 16.1) -

I've searched, but all the resolutions seem to be try new builds. So far I've tried :
kodi-17.4-Krypton-x86.exe
KodiSetup-20170201-88afea0-retroplayer-17.exe
KodiSetup-20170825-dca0d9f-retroplayer-18alpha1-x86.exe
KodiSetup-20170927-dff8c2c-master-x86.exe

with no luck. I'm on Win7 x64 Ultimate, using ScpToolkit. XInput tester works fine and shows all the buttons mapping. In Computer Management, the controller is listed under "Microsoft Common Controller For Windows Class -> Xbox 360 Controller for Windows".

In Kodi, if I go to System Settings -> Input, and check Peripherals, nothing is listed. If I go to Add ons, then go to My add-ons -> Peripheral libraries, Joystick Support (1.4.2 in the latest builds) is checked. When I select configure in new builds, both Enable XInput & DirectInput are turned on.

Not sure what I'm doing wrong - I can't be the only one using a PS3 controller on W7 with this problem..

https://imagebin.ca/v/3dGTy9P0qA7E
https://imagebin.ca/v/3dGUZvf7PSe1
https://imagebin.ca/v/3dGV4q3ZKhIn
https://imagebin.ca/v/3dGVCKdYaE4Q

[PatK]

Not sure you are doing anything wrong might just be the Alpha nature of the software atm. Did you select in controller profiles, PlayStation Controller? A proper debug log (wiki) posted to a public pastebin might be useful for anyone looking into this with depth.

[flhthemi]

Doesn't SCPToolkit make Windows think that the PS3 controller is a xbox controller? So if that's the case Kodi should see it as a xbox controller and maybe Kodi just can't deal with that.

I use SCP for playing games and have never tried it for Kodi.

[chiefwigms]

Log from 10/9 (KodiSetup-20171009-81991e8-master-x86): https://pastebin.com/FX96qVd2

You figure someone would have noticed similar issues in Krypton (I know the Leia builds are experimental).

I didn't see an XBOX 360 Controller as a controller option in the Get More menu - I did add a Playstation controller - both Kodi & Playstation controller time out (in the above log).

[PatK]

A quick check of layout.xml in C:\Program Files (x86)\Kodi\addons\game.controller.default\resources with a text editor, are you seeing

<category name="haptics">
<motor name="leftmotor"/>
<motor name="rightmotor"/>
</category>

near the end? 17:38:45.431 T:6484 DEBUG: <motor> tag has no "label" attribute

[chiefwigms]

My layout.xml ends just as you posted - only attributes are name

[garbear]

In the log I see:

Code:

17:38:15.933 T:6484    INFO: AddOnLog: Joystick Support: Enabling joystick interface "xinput"
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_4.dll...
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_3.dll...
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load bin\XInput1_3.dll...
17:38:15.933 T:6484   ERROR: AddOnLog: Joystick Support: Failed to load XInput DLL
17:38:15.933 T:6484   ERROR: AddOnLog: Joystick Support: Failed to initialize interface xinput
17:38:15.933 T:6484    INFO: AddOnLog: Joystick Support: Enabling joystick interface "directinput"

Something is wrong with XInput on your computer. On my win7 box, it loads XInput1_3.dll just fine.

DirectInput seems to be working, so try running without SCPToolkit or whatever makes the controller run in DirectInput mode.

[chiefwigms]

A quick check of layout.xml in C:\Program Files (x86)\Kodi\addons\game.controller.default\resources with a text editor, are you seeing

<category name="haptics">
   <motor name="leftmotor"/>
   <motor name="rightmotor"/>
 </category>

near the end? 17:38:45.431 T:6484   DEBUG: <motor> tag has no "label" attribute

In the log I see:

Code:

17:38:15.933 T:6484    INFO: AddOnLog: Joystick Support: Enabling joystick interface "xinput"
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_4.dll...
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_3.dll...
17:38:15.933 T:6484   DEBUG: AddOnLog: Joystick Support: Attempting to load bin\XInput1_3.dll...
17:38:15.933 T:6484   ERROR: AddOnLog: Joystick Support: Failed to load XInput DLL
17:38:15.933 T:6484   ERROR: AddOnLog: Joystick Support: Failed to initialize interface xinput
17:38:15.933 T:6484    INFO: AddOnLog: Joystick Support: Enabling joystick interface "directinput"

Something is wrong with XInput on your computer. On my win7 box, it loads XInput1_3.dll just fine.

DirectInput seems to be working, so try running without SCPToolkit or whatever makes the controller run in DirectInput mode.

Pretty sure in Jarvis, the PS3 controller was XInput - I tried the latest x64 build of retroplayer that you posted, same error on XInput:

Code:

11:56:24.521 T:1716    INFO: AddOnLog: Joystick Support: Enabling joystick interface "xinput"
11:56:24.521 T:1716   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_4.dll...
11:56:24.521 T:1716   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_3.dll...
11:56:24.521 T:1716   DEBUG: AddOnLog: Joystick Support: Attempting to load bin\XInput1_3.dll...
11:56:24.521 T:1716   ERROR: AddOnLog: Joystick Support: Failed to load XInput DLL
11:56:24.521 T:1716   ERROR: AddOnLog: Joystick Support: Failed to initialize interface xinput

In the plugin preferences, I disabled Direct Input as well.  Tried running without SCP toolkit running (not sure if its just a notification monitor or whatnot) and with it running. Is it possible to get more verbose debugging on the dll load?

[chiefwigms]

I did some more digging, and it looks like the only XInput on my system was installed with ScpToolkit at C:\Program Files\ScpToolkit\XInput\{x64/x86} folders.  

I copied the x64 dll to C:\Program Files\Kodi (I'm running the x64 build), and now get:

Code:

15:42:33.591 T:4492    INFO: AddOnLog: Joystick Support: Enabling joystick interface "xinput"
15:42:33.591 T:4492   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_4.dll...
15:42:33.591 T:4492   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_3.dll...
15:42:33.593 T:4492   DEBUG: AddOnLog: Joystick Support: Loaded XInput DLL version 1.3
15:42:33.593 T:4492   ERROR: AddOnLog: Joystick Support: Failed to load one or more symbols (GetState=0000000000000000, GetStateEx=0000000000000000, SetState=000000007248D0BE, GetCaps=000000007248D0CA, GetBatteryInformation=000000007248D0E2, PowerOff=0000000000000000)
15:42:33.593 T:4492   ERROR: AddOnLog: Joystick Support: Failed to initialize interface xinput

Looks like the GetProcAddress call returns 0 to m_getStateEx...

For s&g's, I renamed the dll to XInput1_4.dll to see if the GetProcAddress call for m_getState (not Ex) would return a valid address, and got:

Code:

16:56:29.556 T:3424   DEBUG: AddOnLog: Joystick Support: Attempting to load XInput1_4.dll...
16:56:29.558 T:3424   DEBUG: AddOnLog: Joystick Support: Loaded XInput DLL version 1.4
16:56:29.558 T:3424   DEBUG: AddOnLog: Joystick Support: Loaded XInput symbols (GetState=000000007248D0B2, GetStateEx=0000000000000000, SetState=000000007248D0BE, GetCaps=000000007248D0CA, GetBatteryInformation=000000007248D0E2, PowerOff=0000000000000000)
16:56:29.558 T:3424    INFO: AddOnLog: Joystick Support: Enabling joystick interface "directinput"

but then Kodi crashed.. I'm not familiar with XInput at all though - any ideas?

[chiefwigms]

Went back and installed DXSDK_Jun10.exe - it failed at the end, but put XInput1_3.dll in Windows\system32 - looks like it detects now. Wierd that it worked fine in jarvis with just the drivers that ScpToolkit installs.