notshane
Novice
Joined: October 2015
Posts: 47
Location:
|
Post by notshane on Feb 11, 2016 14:16:39 GMT
Hi I think I'm having a similar problem, I recently installed an xbox one controller driver for my windows 10 desktop and this started happening, it remains blank and doesn't respond to either keyboard input or controller, have to shut down via task manager. Any idea if there is correlation to topic creator's problem? Ha, yup, we are in the same boat, my friend. I am not surprised that this thread is the only one you found, given I am the first to experience this problem. But, when you closed out of "Redefine Keys," did it say my error when you clicked it a second time? That's how I get it on mine. It has that blank box at first, then I close that box and it will then give me the error message after I click "Redefine" a second time.
|
|
|
Post by zyrobs on Feb 11, 2016 21:24:39 GMT
SSF uses DirectInput, the XBone pad uses XInput with a bogus DirectInput mapping that cannot be configured.
The problem is that on Windows 10, the analog triggers of the Xbone pad are set up as either a Z-axis and a Z-rotation, which should be centered to allow for a range from -127 to 128. But instead the driver sets them up non-centered, for 0-255. This causes many apps to see the trigger at a permanent -127 value.
When confronted with this, SSF just freezes the button input screen like that. I can confirm that since I use a x360 pad with a driver that can reconfigure all buttons. With Z axis/rotation set to 0-255, SSF freezes up for me, but with the values centered from -127 to 128, SSF reads them fine.
The default XInput drivers never got the triggers right for DirectInput based games (eg. anything published before 2006). Previously they mapped the triggers to the SAME axis, which was even stupider. The main reason I'm not bothering with the Xbone pad (other than the price) is the lack of reconfigurable drivers like what the X360 pad has.
|
|
PassingBreeze
Saturn Gamer
Joined: November 2015
Posts: 128
Location:
|
Post by PassingBreeze on Feb 11, 2016 23:18:27 GMT
So was it the Xbone pad all along? lol! I'm sure someone suggested to try another controller. Stupid Xbone.
|
|
notshane
Novice
Joined: October 2015
Posts: 47
Location:
|
Post by notshane on Feb 18, 2016 21:54:39 GMT
SSF uses DirectInput, the XBone pad uses XInput with a bogus DirectInput mapping that cannot be configured. The problem is that on Windows 10, the analog triggers of the Xbone pad are set up as either a Z-axis and a Z-rotation, which should be centered to allow for a range from -127 to 128. But instead the driver sets them up non-centered, for 0-255. This causes many apps to see the trigger at a permanent -127 value. When confronted with this, SSF just freezes the button input screen like that. I can confirm that since I use a x360 pad with a driver that can reconfigure all buttons. With Z axis/rotation set to 0-255, SSF freezes up for me, but with the values centered from -127 to 128, SSF reads them fine. The default XInput drivers never got the triggers right for DirectInput based games (eg. anything published before 2006). Previously they mapped the triggers to the SAME axis, which was even stupider. The main reason I'm not bothering with the Xbone pad (other than the price) is the lack of reconfigurable drivers like what the X360 pad has. I use an X360 pad on my computer. What kind of thing do you have that fixes this "rotation" problem that apparently resolves the controller input issue?
|
|
|
Post by zyrobs on Feb 18, 2016 22:29:22 GMT
I use an X360 pad on my computer. What kind of thing do you have that fixes this "rotation" problem that apparently resolves the controller input issue? lavendy.net/special/driver/x360c/index.htmlI use the Windows 7 64bit (English) driver from there. It allows you to remap every button to a corresponding DirectInput solution (once you install it, run joy.cpl to set it up). I use the thumbsticks as X/Y Axis and Rotation, the triggers as Z Axis and Rotation, everything else as buttons. Sometimes I map the d-pad as X/Y Axis to match the left thumbstick, since many games only allow directions to be set as that. Also, under "Advanced" set up the z axis/rotation to be based on a center value, and I use the compatibility mode with POV 2-, Button 17- disabled (I recall there was at least one game where it helped). Do note that this driver only uses DirectInput, so the pad will then become incompatible with all XInput games. For those, you can use X360CE to emulate a virtual xinput device, that is if you can stomach the irony of emulating a x360 pad with an x360 pad.
|
|
notshane
Novice
Joined: October 2015
Posts: 47
Location:
|
Post by notshane on Feb 18, 2016 23:46:42 GMT
lavendy.net/special/driver/x360c/index.htmlI use the Windows 7 64bit (English) driver from there. It allows you to remap every button to a corresponding DirectInput solution (once you install it, run joy.cpl to set it up). I use the thumbsticks as X/Y Axis and Rotation, the triggers as Z Axis and Rotation, everything else as buttons. Sometimes I map the d-pad as X/Y Axis to match the left thumbstick, since many games only allow directions to be set as that. Also, under "Advanced" set up the z axis/rotation to be based on a center value, and I use the compatibility mode with POV 2-, Button 17- disabled (I recall there was at least one game where it helped). Do note that this driver only uses DirectInput, so the pad will then become incompatible with all XInput games. For those, you can use X360CE to emulate a virtual xinput device, that is if you can stomach the irony of emulating a x360 pad with an x360 pad. Uh...
|
|
|
Post by buckoa51 on Feb 18, 2016 23:51:22 GMT
I noticed the trigger problem in Trackmania. Do you know any pads that do have completely reconfigurable drivers?
Seems not, since he's got a 360 pad and that should work fine.
Yeah seeing that here too.
Edit - Definitely seeing incorrect behaviour with the Xbox One controller, but works fine with the 360 controller, Windows 10 x64, standard Microsoft drivers.
|
|
|
Post by zyrobs on Feb 19, 2016 0:26:05 GMT
False positive, and google sucks: www.virustotal.com/en-gb/url/a8b438c4765211d8bd7cbb6f4a1b74923846e4246605cebe2c63c4a39a88c2ad/analysis/I've been using those drivers for almost a decade, and so do plenty of others. They contain no malware. If you don't like it, there's also the XBCD driver that has X360 software, but I've never used it, so I can't say much about it. Seems not, since he's got a 360 pad and that should work fine. X360 pad maps the triggers to +/- values on the same axis. Which is practically useless. You can technically define them in emulators, but they'll cancel each other out if you press both, so you can only really use the one with the + value. Xbone pad had its drivers updated at some point to map the triggers to z-axis and z-rotation, but they used noncentered values. There's a LOT of hate for those since both of those setups are idiotic, but Microsoft doesn't give a damn since as far as they are concerned, DirectInput is dead and dusted and why are you not using XInput instead? Hence why two alternate drivers exist. Unfortunately, no such drivers exist for the Xbone pad yet, which is the main reason I'm not bothering buying one.
|
|
notshane
Novice
Joined: October 2015
Posts: 47
Location:
|
Post by notshane on Feb 19, 2016 1:00:02 GMT
Well, I opened the program ("x360csai.exe"), but all it did was update the time stamp of "Date modified" and it did nothing.
|
|
|
Post by zyrobs on Feb 19, 2016 1:10:31 GMT
It's a device driver. Not an installable archive. You have to go to the device manager and manually install it for the xbox360 controller. In the device manager search for your x360 pad, right click -> update driver, select "browse computer for my driver", then select "let me pick...", and there pick "Have disk" and point it to the driver.
Then once installed, run joy.cpl (from the run prompt, winkey+r, or just type it to the start menu), and configure it.
|
|
notshane
Novice
Joined: October 2015
Posts: 47
Location:
|
Post by notshane on Feb 19, 2016 2:24:48 GMT
It's a device driver. Not an installable archive. You have to go to the device manager and manually install it for the xbox360 controller. In the device manager search for your x360 pad, right click -> update driver, select "browse computer for my driver", then select "let me pick...", and there pick "Have disk" and point it to the driver. Then once installed, run joy.cpl (from the run prompt, winkey+r, or just type it to the start menu), and configure it. I tried that, and it eventually led to this: I got to it through here: The file was "x360c.inf" was that the right one? I tried both the x64 and x86 versions, but both of them failed.
|
|
|
Post by zyrobs on Feb 19, 2016 2:44:37 GMT
That's the driver for the wireless pad, not the wired one.
|
|
|
Post by buckoa51 on Feb 19, 2016 10:07:18 GMT
Definitely not seeing that behaviour here. The triggers are on the same axis but I can press both together without a problem. Usually what I do is just redefine them in Xpadder for the handful of games that don't work properly. You then lose all analogue control, of course, and they become entirely digital. This works on the Xbone pad too, for the record.
It's nice they sort of fixed it with the Xbone controller but a shame they couldn't get it completely right, though you do have to wonder if they had done -127 to 128 that wouldn't break a different set of games. It's a shame they can't just put a toggle in. At least it works with more games now (only really found Trackmania that won't let me redefine the controls correctly).
But yeah, no problems with Xbox 360 controller and SSF here. Certainly no weird error message.
|
|
|
Post by zyrobs on Feb 19, 2016 14:23:28 GMT
Wait, you can use Xpadder as an Xinput -> DirectInput wrapper? I thought it was only for mapping keyboard to directinput.
|
|
|
Post by buckoa51 on Feb 19, 2016 15:04:08 GMT
Yeah that's what I'm doing. In Xpadder, assign, say, up arrow to RT and down arrow to LT, then in game assign those keyboard commands to accelerate and brake or whatever. Works, but kills analogue input and makes it entirely digital.
I do not have any issues pressing both triggers at once in this configuration.
|
|