Gave it a go tonight because it’s the only option I can find so far for PS4 sticks on KI (can’t use x360ce for UWP games). Everything mapped perfectly, but once in-game it spams the hell out of the directionals and I have to alt+f4 out. Not quite ready for prime time it seems.
It might depend on the stick used or something, but the lag I got in SFV with x360ce was horrendous. I used Xpadder instead because it was just better when it came to that.
I now use a PCB with xinput, but I’d definitely at least try out the program the OP is suggesting if I wasn’t
I will give it a shot, because x360ce randomly stops working for like 10 seconds in my laptop. It’s very rare, but you don’t want to carry this risk on ranked ever.
Between x360ce and X/O
Both: They set up the same, binding your controller to actual 360 binds. This is important as other key binders like joy2key only allow you to bind what is on the keyboard. This can cause a number of issues, and neither of these programs need to worry about that.
x360ce is set up per game, but only once and that’s all you do. This one also has a nice graphic interface for configuration letting you see your configuration easier. It runs in the background automatically each time you start the game, so you don’t have to worry about it. You can set it to give you a notification bing in case you are worried about it not connecting.
X/O is set up once per controller, but you have to run it each time you want to play. The set up is a bit bland, but all of the settings are there. Not only do you need to run it every time you play, but you also have to click start / stop. If you are playing a game full screen this can be an annoyance if you forget to start it first since you have to switch tabs to start it, but I use two screens and can easily fix this in my second window without effecting my game.
x360ce is set up in the files though… For Steam games this isn’t an issue, but for Windows games (Killer Instinct <_<) this is simply not an option. A real killer for this program.
I don’t know if it has more / less lag, or if either of these even create additional lag… but neither are unplayable. I got to 2000+ rank on x360ce, and didn’t magically reach 5000+ lp with X/O haha.
Are you talking about alt-tabbing out? Why do you need to stop the X/O to do that?
You can make a batch file to both launch the game and X/O at the same time, as well as close X/O when the game is shut down. I haven’t tried it in Windows 10 yet, but I used to do this in Windows 7 with Xpadder.
idk if you could make a batch to start x/o - also start the controller - and start your game. You could do a batch to start x/o and your game, but then you’d have to tab out to actually start the controller.
Does anyone else use ds4windows? I think it only works with dualshock 4 but so far I’ve gotten good results with it.
Also you can set up a flag to let you know if the controller goes over x ms of lag, if it does the lightbar changes color so at least you know something is up.
Here’s my annoyance with x360ce. I use both a Hitbox and a madcatz x360 silent TE stick. When I want to use my Hitbox, I put the x360ce files in that folder and everything runs great. If those files are in that folder and I’m trying to use my silent TE, the TE doesn’t work. I have to go back into that folder and remove those files so the TE can work. Then I have to put the files back in the folder next time I use Hitbox.
I need help here. I have only A-B-X-Y buttons (excluded back-home-start). How am I supposed to map the HP and Hk (and the fouth)?
Do you map them in right/left analog/trigger/etc buttons and then you setup correctly in game?
P.s. X360ce had a very bad lag with me and right now I’m using y2keybut I feel like i’m playing with a small delay…
lol. i almost did but remembered that i had 2 controllers plugged in with the one i normally use for SF always registered as 2nd, then i went through the rest of the steps and actually forgot to install. thanks.
Have you assigned the left analog stick? If all you’ve set up is the D-Pad, then it’s gonna wig out like that. I found that out the hard way myself, to be fair. Only learned what the problem actually was when I checked out the Issues page on the github.
To fix that, set “Left Analog X” to “Axis 1”, and “Left Analog Y” to “Axis 2”. Should get you set up nice and proper.
This honestly feels more responsive than joy2key. I’ve been bitching about joy2key ever since I had to start using it for SFV. At times with joy2key I found myself spamming lights for no reason what so ever.
All I need now is a match where there isn’t any teleporting.