A Step-by-Step Guide to Make Controllers Work in WINE

x360ce-controller-top

A couple of days ago, I was enquiring with a certain WINE developer the state of controller support in WINE. I was surprised they were actually working on a native solution, yet not shocked to hear that for now, a tool like x360ce.exe was probably one’s best bet. The thing is, there is a lack of a good tutorial out there on how to make things work from A to Z – sure, you can find piece-by-piece info across several sources, but I thought it may be useful to have the whole process detailed for everyone who’s interested to do that. I have replicated with success the same process three times on different machines, all running Ubuntu derivatives (Mint 17.3 and Mint 18) so it should probably work on any Ubuntu-based distro. So here we go.

Part A: Making this %!”# x360ce work in the first place

First, open a terminal and run the following commands to get the latest version of wine-staging. This may not be 100% required, but in my experience older versions of WINE like 1.6 cannot run x360ce properly (crash at startup, even with the required .NET libraries).

sudo add-apt-repository ppa:wine/wine-builds && sudo apt update
sudo apt install wine-staging winehq-staging

We also want to make sure we have a recent version of xboxdrv instead of using the generic xpad driver:

sudo apt-add-repository -y ppa:rael-gc/ubuntu-xboxdrv
sudo apt update
sudo apt install ubuntu-xboxdrv

At this stage xboxdrv should be up and running (automatically). Now plug your Xbox360 dongle in a USB port, and power up your Xbox360 pad. It should be recognized and assigned the first player’s pad.

Now on to the real stuff. The next step is about getting a 32 bits prefix where we will run x360ce.exe in the end.

WINEPREFIX="$HOME/prefix32bits/" WINEARCH=win32 wine wineboot
export WINEPREFIX="$HOME/prefix32bits/"

We are going to install .NET 45 in that particular prefix. This is required as x360ce needs this framework to create its windows and menus. Note that the last command below starting with the “bash” statement takes a long time (probably a good 10 mins) but it has the advantage to be fully automated and does not require any user input (you obviously need to be connected to the Internet). Easy. Just go grab a coffee.

cd $HOME/prefix32bits/
wget https://raw.githubusercontent.com/Winetricks/winetricks/master/src/winetricks
bash winetricks -q dotnet45 corefonts

Now on to getting x360ce and unzipping it:

wget http://www.x360ce.com/Files/x360ce.zip && unzip x360ce.zip

We are almost done!

You just need to run x360ce next:

wine x360ce.exe

If everything went as expected the window should now appear and let you edit the pad settings. It will first ask you for xinput1_3.dll, and kindly create it for you since you don’t have it. Awesome!

dllrequest

Next you may get some internet-based updates, accept them.

internet

Now on to the pad controls: just go ahead and edit each button and axis using the “record” dialog proposed on each menu item – that way you can just click on the button to have it mapped correctly.

x360ce-window

Once you think your mapping is correct, just try moving your analog pads in all directions and clicking the buttons – they should be highlighted on screen when you do so, to confirm everything is working as expected.

Once you are satisfied, hit the “save” button at the bottom. This will create a x360ce.ini file in the very same folder.

If you need to change the configuration again (any fix required for the mappings, for example…) note that in my case having the previous x360ce.ini file in the folder makes it impossible to edit the settings anew:

blankscreen

if this happens to you too, just rename the existing x360ce.ini file to something else or erase it altogether, and this will show the mapping editor again. No Big Deal.

Part B: Using it with WINE-based games

Go back to your prefix32bits folder, and now you just need to copy:

  • xbox360ce.exe
  • xbox360ce.ini
  • xinput1_3.dll

…into any WINE game folder where the game binaries are (the ones triggering the launch of the game). Make sure such games are on a 32 bits WINE prefix though, if not things will crash.

So let me give you an example with the GOG, Windows version of Enter the Gungeon here. Yes I know we have a Linux version of this game, but this is not the point – this is just a proof of concept.  You can use for example PlayOnLinux to install this version, and click on “Configure” – and then click on the “Miscellaneous” tab:

gungeon

As you can see you can directly open the program’s directory there, and this is where you will put the 3 files I mentioned above. Yup, just dump there in that folder.

Now you close that configuration window, launch the game, and lo and behold, the controller is recognized. This is me below playing the Windows client with the controller using x360ce. The framerate is shit because I run the game on my laptop and I recorded the video with OBS on top, so this looks much smoother in reality.

You can see the game recognizes the controller as the control hints use the xinput buttons instead of keyboard shortcuts. And yeah, obviously, there’s no point using this solution for EtG as there is already a perfectly working Linux client, but I wanted a game that my laptop can run correctly for such a demo.

Part C: Profit !? I mean… Enjoy!

Just repeat only the step B for any other game. Even if they are not installed under PlayonLinux. Keep the original prefix only for the times where you’d like to change the settings again. Otherwise you don’t have to worry about it, just copy the three files mentioned every time and you are good to go.

Let me know if this worked just fine for you, especially if you tried on non-Ubuntu-based distros (in that case you can’t use the ppa I refered to, but you may compile such libraries from source or find relevant packages for your distro).

 


BoilingSteam shows no ads whatsoever and we strive to provide you with a clean and pleasing reading experience. If you enjoyed this article and are interested in contributing in some way (guest articles for example), do not hesitate to drop us a message via the contact page. We have also started a Patreon Campaign since February 2017 - please consider donations so that we can increase our activity and cover more topics and more games! In order to follow what we do, we recommend you sign up to our newsletter (No Spam!), or our RSS feed.

Ekianjo

26 Comments

    • Yup, it works as well as long as you specify that your Steam Controller should act like a Xbox360 gamepad.

  1. There was one vital fact missing from these instructions: xinput1_3 needs to be set as “native” in winecfg (I set “xinput8” to native too but I’m not sure if that was necessary).

      • I get this behaviour with 2.0rc2 and rc3. I guess the behaviour must have changed? Though it was the first suggesting from people on IRC once I described my issue fully.

  2. Yes I confirme what Adam written about

    “xinput1_3 needs to be set as “native” in winecfg”

    I used Wine for macOS (through Wineskin’s wrapper) with my 360 controller since various years with the x360ce.ini an xinput1_3.dll but since wine 1.9.23 was released, this method stopped to work…probably due to some change comming with the HID bus support for MacOS as you can read on the changelog: https://www.winehq.org/news/2016111101

    Now thank to Adam and his comment I can run again my 360 controller also with lattest engines…

    PS:
    For MacOS user:
    the procedure for x360ce with wine is the same of this guide but you need to install this driver for macos:
    https://github.com/360Controller/360Controller/releases
    that makes what xboxdrv makes for linux in this guide…

  3. Maybe the trick doesn’t work with all games… I just tried on my macOS wineskin’s wrapper of “Ori And The blind forrest” and gamepad doesn’t run with wine 2.0 (also if I set xinput1_3 as native through winecfg) while it works with previous wine engines and the same game…
    I don’t know if depend that Ori is an Unity game…

  4. new update:
    the trick work again also with “Ori and the blind forrest” with wine 2.1 for developers… So it’s possible my previous faillure was determinated by wine-staging 2.0. I used to test xinput1_3 as native for Windows..

  5. I’ve also have some issues based on whether or not I use xboxdrv, or the steamos-modified builds of xpad (for Arch users available in the AUR). Specifically, x360ce’s config tool happily detects a wireless 360 controller in all cases, but the resulting DLL/INI only actually worked when using xboxdrv (which makes no sense to me, as for other applications, using steamos-xpad looks exactly the same as with xboxdrv –mimic-xpad). Maybe I’ll investigate it later.

      • Not yet, I’m afraid. I’ve been, and am going to be, busy for a few weeks with studies and work, so I’ll probably not be following up anything bug-fix-y or troubleshoot-y unless it pertains to productivity. I’ll come back as and when I do have the chance, though!

  6. Using Wine Staging 2.1 and I’ve tried this guide and the games don’t see to see the xinput1_3.dll file. Nothing I configure in x360ce is showing up in games. I can configure it just fine but the games see what Wine sees. T

    • Did you try following the advice of other commenters at the end of the article ? They apparently recommend to set xinput 1.3 as native into WINE settings for it to work in newer versions.

      • I did that. I needed to cause if I didn’t the x360ce program wouldn’t see the controllers. Instead of the green boxes I saw grey. Then I would place the files in the directory of the game and run the game. But as far as I can tell, the game sees what Wine sees. Like something with a js at the end.

  7. There is a native GTK3 app that I’ve used for 6+ months; I actually prefer it to the Steam UI config. It works for both running in Wine, Steam (without having to use the overlay), and I’ve also used it for Dolphin Emu.
    https://github.com/kozec/sc-controller
    I haven’t tested on anything other than Arch Linux, but there are packages from the OpenSUSE Build Service for other distros.
    Also, general PSA: (1) This specific site is listed with a warning on the Arch wiki https://wiki.archlinux.org/index.php/Gamepad#Steam_Controller (also good tips on SC in general) (2) Piping some HTTP blob to unzip is probably not the best idea, at best. Worst case.. well.. : /
    Thanks for the great articles, I’ve been enjoying the overall great content! : )

  8. Ok I’ve tried and tried to get this to work on Mint 18.1, and I finally got it to work, but for only 1 game and that’s DuckTales Remastered. I’m also using Wine Staging 2.2.

    This doesn’t work on Rayman Legends or Origins. Doesn’t work on Sonic Generations, and doesn’t work for ICEY. I’ve tried copying and renaming the xinput1_3.dll to xinput1_1.dll, xinput1_2.dll, and xinput9_1_0.dll. I don’t get why I’ve only gotten one game to work?

    • The first two things I’d ask would be
      * Are you sure that these games support xinput?
      * Did you make sure that you set the appropriate DLL override rules in winecfg (check all the other comments)?

      • I really don’t know about xinput. I thought this was universal for all games? I Google’d to see if there’s any guides for the Rayman games with X360CE and they do exist. ICEY is a relatively new game so nothing there. Sonic Generations does have guides for x360ce as well. Here’s a link to someone who’s playing Rayman on Wine and having issues with x360ce.

        https://github.com/x360ce/x360ce/issues/479

        I did do the xinput1_3.dll as native in winecfg. Not sure if there’s anything else to add? I also tested Dark Souls and Dark Souls 2. Dark Souls 1 doesn’t seem to work, but there’s a bunch of stuff to fix PC keyboard controls that might interfere with this. Dark Souls 2 though, does work just fine with x360ce in Wine.

      • Did a little testing and I think some games are just going straight to the system32 folder for xinput1_3.dll, or whatever xinput version they use. BTW anyone tested Rayman Legends & Origins to see if their xinput 1_3.dll works?

Leave a Reply

Your email address will not be published. Required fields are marked *