Controller stopped functioning.

[CarloCGC]

I know controller issues usually get ignored but here goes...

 

My Xbox 360 wireless pad has stopped functioning after a recent windows 10 update (not upgrade) it seems as if the controller was migrated during the update whatever that entails as it says this in the driver settings. Since the update the controller has no function in hyperspin yet works fine everywhere else (Steam games, emulators etc)

 

I doubt anyone has a fix but are there any steps people usually take with controller issues? remapping it does not work.

 

For the record all has been well for years with my current setup (until windows 10).

 

Thanks

 

I have uploaded a pic of the message about migration from the driver settings if it helps anyone.

 

 

[Guest]

I know controller issues usually get ignored but here goes...

My Xbox 360 wireless pad has stopped functioning after a recent windows 10 update (not upgrade) it seems as if the controller was migrated during the update whatever that entails as it says this in the driver settings. Since the update the controller has no function in hyperspin yet works fine everywhere else (Steam games, emulators etc)

I doubt anyone has a fix but are there any steps people usually take with controller issues? remapping it does not work.

For the record all has been well for years with my current setup (until windows 10).

Thanks

I have uploaded a pic of the message about migration from the driver settings if it helps anyone.

Capture.PNG

The fact that it's migrated isn't going to make any difference here - that's just showing where the driver has come from. If the issue is only in HS then the issue is with HyperSpin.

Few things to try,

- Uninstall driver by right clicking on the listing in device manager. Restart.

- Connect controller / wireless adapter in different port.

- Remap the controls in HyperHQ

If that fails, just map the controller to key presses using joy2key. This is actually the preferred solution given that HyperSpin has pretty weak native joypad support.

The likely cause of this issue, is that the api calls required to work with the controller has changed and HS hasn't been updated to fix this. If the key map route is taken, this issue won't arise again.

Sent from my iPhone using Tapatalk

[CarloCGC]

thanks for the tips i will try them tonight  

[CarloCGC]

 

 

- Uninstall driver by right clicking on the listing in device manager. Restart.

- Connect controller / wireless adapter in different port. 

- Remap the controls in HyperHQ

If that fails, just map the controller to key presses using joy2key. This is actually the preferred solution given that HyperSpin has pretty weak native joypad support.

 

Having issues with joy2Key when starting a game RL throws an error and no other solutions you suggested work.

 

looks like Win10 killed controller support on hyperspin for me I would suggest people using using win10 do not update the OS if they are using hyperspin native controller support.  

[Guest]

Having issues with joy2Key when starting a game RL throws an error and no other solutions you suggested work.

 

looks like Win10 killed controller support on hyperspin for me I would suggest people using using win10 do not update the OS if they are using hyperspin native controller support.

 

 

That's not true - it works fine.

 

What error is RL giving you - if you give the specific details we can help get you sorted.

[ninja2bceen]

Ya or u can use joytokey or xpadder to

[CarloCGC]

 

 

What error is RL giving you - if you give the specific details we can help get you sorted.

 

Thanks for the help! RL isn't throwing an error now (That happened only the first time) Instead Joy2Key seems to close itself on emulator exit which is mapped to back + start on the 360 pad. 

 

Any reason joy2key would close? and how can you get joy2key to start with hyperspin or on windows startup?

 

Thanks again.