Xbox 360 wireless controller not working

[beenq]

Hi , i know i dont post much as i like to try and resolve issues myself ,but , im struggling with this one. had the hyperspin not starting issue and got the dll file to sort that one , but windows 10 pro updated the other day and since then my 360 wirless controller (via official microsoft adapter) only lets me click past the intro video after that i cant scroll through the wheels etc etc , has nayone experienced this ? can anyone help please ? , its driving me nuts. i did uninstall device adapter and reinstall but im, at a bit of a loss. thnks to anyoine who can help , really dont wanna loose my setup to this stupid gitch

[gigapig]

This glitch has been in Hyperspin forever. The way to get over it is to use the Startup script of a keymapper like JoyToKey.

[Spawk]

What are you using for HS navigation? There are basically 3 options:

1. HQ: Most people avoid using this. The wheel tends to spin uncontrollably and/or locks HS up. Maybe the analog deadzone can be adjusted to help this? Maybe it's fine for you? If you start to notice weird things happening in the wheel, this is probably the culprit.
2. Startup Script: This is an easy method of avoiding the above issues. It has a section to specify menu controls and is also useful for starting other programs you may need to launch when HS starts.
3. Keymappers (JoyToKey/Xpadder): Advanced mappers that can  be configured in RLUI that let you easily manage per system or even per game profiles. These are useful for invoking a variety of things from a gamepad like exiting emulators, bringing up RL's pause feature, load/save savestates... anything that emulators don't allow you to map directly to gamepad in their own UI.

One issue that I've seen before is "focus". HS looks like it's in the foreground but the window isn't the "selected" window so no input response. A simple mouse click will bring it to "focus". This usually only happens if starting other programs at same time as HS or possibly when exiting an emu but RL has options for that.

Aside from your issue, I generally advise against using wireless gamepads. They have a habit of turning themselves off after x amount of time. This may render them un-see-able by HS until it's re-started. Or in the very least, re-arrange their windows ID's. People use them so it's "doable". Just something to be aware of.

[beenq]

Appreciate the replys guys , crazy thing is I used to use the startup script then hyperspin got updated (I think version 1.4) and it incorporated everything and I've not had a problem for years. If you think the easiest way round it is back to the startup script that's easy enough to sort , just really confused as to what's happened all of a sudden and what actually caused it to break. 

Spawk,  I'm just wondering if anything within rocketlauncher has changed recently (don't remember it updating) I will take a look at that also

Will drive me nuts not knowing what broke it though lol

[ci2own]

This glitch has been in Hyperspin forever. The way to get over it is to use the Startup script of a keymapper like JoyToKey.

I guess the best script to solve that, is LaunchBox [emoji18]


Enviado desde mi iPhone utilizando Tapatalk Pro

[beenq]

I have launchbox also but find it very laggy compared to hyperspin 

[beenq]

I have launchbox also but find it very laggy compared to hyperspin 

[beenq]

Went back to the startup script,  all working again , if anyone does read this , remember you have to set the script up as a startup program in hyper hq for it to work (I'd forgotten for around 10mins lol)

[smb2176]

I am having same problem with an Xbox 360 wired controller. I'm kind of a noob with Hyperspin, can anyone direct me to a step by step to change fix ?