X360ce File
Sabina Kehler
Has anyone had any success getting x360ce to run lately? I can't recall exactly when, but some months ago it seemed to simply stop loading when I run the launcher. Game runs fine, but the x360ce emulator doesn't seem to pop up and my controller is non-responsive (or, rather, the game doesn't respond to my controller).
It's not a huge deal, I've just been playing with an old Dual Action logitech controller that uses DirectInput and I don't have a spare wired xbox remote.
Update: see details below. Issue has been resolved.
If that doesn't work either, maybe migrate to XOutput. It's a bit of a hassle to config (particularly if hiding your device isn't done by default and the xoutput virtual controller and yours overlap), but you only have to do it once (rather than copying dlls to each folder, you just have the program start with windows and that's that) and then it works across all games that support x360 controllers.
If you need the 64-bit dlls, download the 64-bit executable from the official site and put it in a separate folder (the dlls have the same name, so if you make them in the same folder, the 32-bit ones will be overwritten), then do the same thing:
I know this thread is a bit old, but just wanted to pop in to say thanks for the answer, because I got a Logitech G13 (Gaming Keypad with an Analog Joystick) yet it's Dinput not Xinput, so no walking for me which was driving me nuts at times, so Much appreciated for this :)
I'm going to necro this again, since other threads didn't give a satisfactory answer, and sadly neither di my ticket to support. So you guys use 360ce and warframe is okay wiht it? no suspensions and bans? I want to fulfil my dream of flying my railjack with my thrustmaster 16000x and throttle combo and 360 is the only thing that would possibly work. Maybe i get lucky and someone sees this and gives me an answer
IMPORTANT: Please download and run digitally signed files only! If someone asks to disable antivirus or exclude X360CE app from anti-virus - DON'T! Report any suspicion in Issues and we will try to resolve any false positive with anti-virus developers.
Purpose of HIDGuardian is to hide original controllers from games, so that only virtual controllers are visible. Install HIDGuardian only if original controller prevents virtual controller functioning properly in the game.
DO NOT attempt to remove HIDGuardian by simply deleting it from Windows OS Device Manager. This can result in loosing access to your Mouse and Keyboard and you will be forced to follow Manual Uninstall Instructions below.
The x360ce.exe application version 3.x is just a GUI for editing x360ce.ini and testing your controller. The x360ce.exe (3.x) application can be closed before launching the game. The game doesn't need it and it uses your computer's resources.
v4.16.8.0 (2020-10-25)
- Fixed: Controller image scaling issue.
- Fixed: Crash when User Device list updating.
- Fixed: Issue detector sometimes do not start after app starts.
- Fixed: Issue detector was reporting missing HID Guardian when not needed.
- Fixed: Interface freezing during error report.
- Fixed: HID Guardian was not always applying settings.
- Fixed: Do not request XInput states when program is minimized to save CPU resources.
- Update: Configure Hid Guardian Automatically option is set to OFF by default now.
- Update: Application no longer requires elevated privileges when starting.
- Update: Make missing HID Guardian a moderate (optional) issue, which won't prevent UI to load.
- Update: Redirect HID Guardian [Install] issue button to dedicated install form.
- Update: Information on [Help] tab updated.
- New: Add HID Guardian warnings and manual uninstall instructions to [HID Guardian] tab.
v4.12.18.0 (2020-08-05)
- Updated: Version of .NET Framework increased to 4.7.2
- Updated: Debug files are now embedded.
- Updated: No need for separate debug version. Exception reports will contain exact code line.
- New: [Copy Preset] to clipboard and [Paste Preset] from clipboard buttons.
I've been trying to set up the Xbox 360 controller, usb connected, under wine with x360ce as shown here so I can play with it. Have been few days now and after hitting the head against the wall few times, decided to give up a bit and ask in case someone can shed some light to the matter.
So, I'm running Debian stretch 64 bits and my version of wine is 2.0-rc3. xboxdrv is installed and working fine on native linux games. There is a Steam Controller connected to the machine too and the real tone cable from Rocksmith too (this one works fine out of the box as well)
The installation goes well, then I proceed to download x360ce file, unzip it and execute it. I create the dll (xinput1_3.dll) I can then re-map the buttons and hit save, which originates a x360ce.ini file. As I can do the mappings just fine I supposed wine was then able to see my controller...
I have tried to override dll direction's in both prefixes via winecfg installing Directx9 independently, also tried to run the games, without steam for windows open, as a launcher from steam for linux and that didn't work either. I have also tried to install the script from Kokutoru, here, but not avail.
What I did to solve the issue, after proceeding creating the prefixes for the games as stated above, was deleteing the prefix for x360ce and using dumxinput from kozec instead. In order to make the Steam Controller work under Wine I also installed sc-controller. To add the repository and install it I did:
I finally got Killer Instinct (Steam Version) working with my arcade controls using an app called x360ce. (An app for mapping an input device as an xbox 360 controller) I set LB to use the .exe file and imported it as a windows game rather than importing it as a steam game if that matters to assist in providing a solution (although I don't imagine it will but you never know...)
So when I launch Killer Instinct, x360ce automatically opens without any manual intervention (I don't have to set it up as an additional app or anything in LB) but when I quit Killer Instinct x360ce remains open and messes with the order of my joysticks for games that use retroarch.
All my products and services are free.All my costs are met by donations I receive from my users.If you enjoy using any of my products, please donate to support me.Thank you for your support.Tom Speirs
Likely the problem is a problem with X360ce and not PinballX proper if you are able to run Pinball Fx3 and not Pinball FX2. Of course, attaching copies of your pinballx,ini and log,txt files to your issue thread may give additional clues.
not sure if it's needed or being used but did you set run as administrator on the xbox360 ce binaries in pinballfx2 directory ? I'm not too familiar with xbox 360ce but i was under the impression one had to copy the files from xbox 360ce in the folder of the executable of the game. The only thing i'm doubting about is if xbox360ce binary is actually ran when you run the game my guess its only using the (wrapper) xinput dll it creates then but not sure.
Anyway what i'm trying to say is if you got run as administor enabled on pinballx frontend you might need to do it on xbox 360ce as well or if you have it enable on some executable pinball x runs you might have to enable it on pinball x executeable. I know some things like sending WM Messages around between apps where one app is ran elevated and ther other not that they can't communicate with each other (not receive the WM_MESSAGES) due to difference in (elevated) rights.
But i'm not certain it's applicable to xbox 360 ce in this case as dlls don't require elevated rights set, it takes as the binary that loads the module / dll has it set.
Just an idea though something you could try ... like test if it makes a difference if you set pinballx to run as administrator / elevated or verify the xbox 360 ce programs if you got multiple one in each game folder.
Another thing might perhaps be that the working directory is not correctly set when running pinball fx 2 and it can't find the dll's although usually they (windows) look for dll's in the directory of the executable as well
XBox360CE runs, because when you open the table, you hear the noise it makes when starting, but afterwards, it's as if PinballX had priority over XBox360CE or over FX2 and my controls no longer perform as XBox.
i had the same problem with Wizards of oz but i don't consider it a pinball x (frontend) problem and indeed i also added a launch after script to kill any leftover programs still running like dmdext or some parts of b2s server that fixes it with me as well and never had a problem doing this.
i can test this weekend to see if i got the same problem with pinball fx 2 and xbox 360 ce, i did not use pinball fx2 because all the tables i own there are also in pinball fx3 (i don't own every table in pfx2) but i'm willing to test it and see if i got the same problem.
@Outhere
The inverse is also possible they don't function if you do not let them run as administrator but it's usually outdated programs (from xp) or the program doing things that requires elevated rights (or the scripts used in vp) But you are correct in saying that when you start with one running with elevated rights that all others possible need it as well. I've seen it with our programs at work as well and we had to do modifcations one of the things we came across were the WM_MESSAGES stuff but theres many more things sometimes you don't have a choise and must set run as administrator to make a(n older) program work. It was just an idea to see if it was related or if it might fix it.