While the X-Arcade controllers work as a keyboard with the default PC connection, there are ways to make it act like a gamepad instead for games that don't offer great keyboard-based controller support. The original way for an input device to work as a gamepad was through the DirectInput protocol, which still works on the vast majority of gamepad-enabled games. But some newer games, such as Killer Instinct, Mortal Kombat X, Street Fighter IV & V, and Steam, require the newer Xinput protocol that was introduced with the Xbox 360 gamepads (and now Xbox One). Xinput works with both Xinput games and most DirectInput games, so we recommend it. Below we show you how to make your X-Arcade controller work as an Xinput device or DirectInput device on PC.
Method 1: With Hardware
The easiest way is to use our new Tri-mode PCB, but you can also use our Xbox 360 adapter kit or Xbox One adapter kit (both requires either a PS2 adapter or 5in1 adapter) to connect your X-Arcade to a PC via USB. These options allow you to change modes just like on a console and works with any DirectInput or Xinput games.
You can also use our 2in1 adapter or PS4 adapters, but this will require using a special driver and software such as DS4Windows, InputMapper, or MotioninJoy(we can't offer support for any of these). An interesting history lesson on these here.
Using Windows 7? Try these: 64-bit / 32-bit v1.8.154. It’s never been faster or easier to take a Speedtest. Download the free Speedtest desktop app for Windows to check your internet speeds at the touch of a button. Get a real-time check of your ISP’s performance and detect trends over time with data on: Available in 17 languages.
Download World of Joysticks XInput Emulator - Emulate an XInput gamepad using any DirectInput device and play games that only offer support for Xbox controllers, with this easy-to-use tool. WorldBench 6 Test Results. Overall, Windows 7's performance improvement over Windows Vista is slight-but the important thing is that there is an improvement at all. For a breakdown of some of the.
To test it on PC see Windows Gamepad testing.
Method 2: X-Arcade Xinput(Recommended Software Emulation Solution, huge thanks to Mike Wyatt!)
Some games now require an Xinput controller (such as Xbox 360 or Xbox One) to work, and Xinput will work with most DirectInput games as well. 'X-Arcade Xinput' is a software solution to make the X-Arcade work as an Xinput gamepad. It also supports a dualstick mode as well along with D-Pad and Analog modes.
- Download X-Arcade Xinput package (xarcade-xinput.zip), create a new folder somewhere and unzip the contents to it.
- Run the 'Install Driver.exe. You only have to do this step once.
- Run the 'XArcade XInput.exe', this will open up the interface in your web browser for disabling/enabling it and changing to the modes available. You will need to run this each time you want to play.
- You can download Xinput Test to test that it is working, or you can also see it working in Windows Gamepad testing or this web-based HTML5 Gamepad Tester.
Usage:
- Make sure your X-Arcade controller is in mode 1.
- In the interface, you can disable it to get keyboard functionality back. Enable to play.
- Choose the mode you want to play in by clicking the 3 dots next to each option below and choosing 'Make Active':
'X-Arcade 1 player Analog DualStick' is for 1 player with Joy 1 in analog mode, 2nd joystick works as analog 2.
'X-Arcade 1 player D-Pad DualStick' is for 1 player with Joy 1 in D-Pad mode, 2nd joystick works as analog 2.
'X-Arcade 2 Player Analog' is for 2 players with Joy 1 on both sides acting as analog sticks.
'X-Arcade 2 player D-Pad' is for 2 players with Joy 1 on both sides acting as D-Pads. - Simply close the Command Prompt window when you want to close it.
- More information such as remapping the controllers can be found on the official X-Arcade Xinput page.
- If you get an error message when trying to install, open Device Manager and remove any 'Uknown Device' you see under 'Other devices' and 'System devices', reboot and try again.
- If you ever need to uninstall the driver for some reason, just go into the 'Scp Driver Installer' folder and run the 'ScpDriverInstaller.exe' and choose Uninstall.
Windows 10 bubbles screensaver.
DirectInput Joystick Emulation:
VJoy Virtual Joystick Driver can create virtual joysticks in Windows and comes with a tool which allows you to map keystrokes to the virtual joysticks axis and buttons. Our custom ini will map the X-Arcade to the same buttons layout as an Xbox 360 controller in Windows. This means that any game you play that has an Xbox 360 controller option will work with no additional setup needed.
- Download VJoy and install it. Windows will warn you that it's an unsigned driver, choose continue anyway.
- Download X-Arcade.ini (right-click and choose 'save as', IE users may need to rename the .htm to .ini) and place it in the directory C:Program Files (x86)VJoy
- Open VJoy and click 'Open Ini' and choose the X-Arcade.ini file.
- You can test your settings in the standard Windows Game Controller test. Note that the Player 1 joystick can change between analog mode and D-Pad mode using the Numlock key, numkey on is D-Pad, off is Analog.
You test if is it working in Windows Gamepad testing or this web-based HTML5 Gamepad Tester.
DirectInput to Xinput Option1:
XOutput can take the Virtual Joys from VJoy above and emulate them to Xinput controllers.
Xinput Windows 10 Download
- Setup VJoy above first.
- Download XOutput and extract it wherever you want it.
- Run the included ScpDriver.exe and install it.
- Download our custom ini file(right-click and choose 'save as', IE users may need to rename the .htm to .ini) and replace/overwrite the one in the XOutput folder
- Run XOutput.exe, press 'Start' and play!
- Setup Method 2 above first.
- Download TocaEdit and follow the instructions for setting it up for your game.
- Download our custom ini file(right-click and choose 'save as', IE users may need to rename the .htm to .ini) and replace/overwrite the one created by TocaEdit in your game directory.
You can download Xinput Test to test that it is working, or you can also see it working in Windows Gamepad testing or this web-based HTML5 Gamepad Tester.
TROUBLESHOOTING:
Using the Xinput Test or HTML5 Gamepad Tester you can see if your controllers are assigned to the proper players, typically you would want them as players 1 and 2 (if you don't also have any other gamepads connected to the PC). Changing the controller player assignments is unfortunately not easy to do manually, so if yours are set incorrectly you will want to do one of the following:
Method 1:
- With the peripherals/adapters/controllers connected, click the Windows Start button and click on the Gear (settings) icon, then click the 'Devices' icon
- Under 'Bluetooth & other devices' scroll down to 'Other devices' click on each 'Xbox 360 Controller for Windows' listed and click 'Remove device'.
- Unplug the peripherals/adapters/controllers and plug them back in again.
Windows 7
Method 2:
Beta Test Windows 7
- With the peripherals/adapters/controllers connected, right-click on the Windows Start button and choose 'Device Manager' (or press Ctrl+Alt+Del and open it there).
- Click the arrow next to 'Xbox 360 Peripherals' and right-click on each 'Xbox 360 Controller for Windows' and choose Disable device', it will ask you to restart but you can just click 'No'.
- Unplug the peripherals/adapters/controllers from the PC, then plug them back in. Next just re-enable the devices.
Xinput Test Windows 7 download free. full
- Found PCGamingWiki useful? Please consider making a Donation or visiting our Patreon.
Similar Content
- By Volcano_MasterComplete DirectInput Force Feedback Driver for XInput - Masahiko Morii MSI pack including all versions ever released!
Very rare to find nowadays.
List of filesxi.win7.x64.en.msi > Windows 7 x64/64bit Englishxi.win7.x86.en.msi > Windows 7 x86/32bit Englishxi.wlh.x64.en.msi > Windows Vista x64/64bit Englishxi.wlh.x86.en.msi > Windows Vista x86/32bit Englishxi.wnet.x64.en.msi > Windows XP x64/64bit Englishxi.wxp.x86.en.msi > Windows XP x86/32bit Englishxi.win7.x64.ja.msi > Windows 7 x64/64bit Japanesexi.win7.x86.ja.msi > Windows 7 x86/32bit Japanesexi.wlh.x64.ja.msi > Windows Vista x64/64bit Japanesexi.wlh.x86.ja.msi > Windows Vista x86/32bit Japanesexi.wnet.x64.ja.msi > Windows XP x64/64bit Japanesexi.wxp.x86.ja.msi > Windows XP x86/32bit Japanese - By Hman360This is an AntiMicro profile for the Spider-Man 2002 movie PC game for mapping the inputs that the game won't register in an XInput controller to the keyboard & mouse controls.
You can import it into AntiMicro and set it to autorun with the SpiderMan.exe file in AntiMicro's settings.
Specifically, the mappings are as defined below:
Right Stick -> Mouse (default - camera)
LT -> Shift (default - web action & recenter camera)
RT -> Numpad 5 (default - web swing)
The other inputs should be configurable in the game's gamepad settings, except the Left Stick which automatically is set to movement. - By MethanhydratIMPORTANT
Since game version v1.09 this fix is no longer needed, because the game received an official option to enable XInput support.
If you are interested in using PS4 button prompts, you can find a corresponding option in the most recent version of the PRIC mod.
---
TL;DR
This fix resolves controller issues in Prey that were introduced with patch v1.05, by forcing the game to use XInput instead of the Steam Controller API by Valve.
Quick start guide:
Open the archive and choose the button prompts you want to use by opening the corresponding folder
Extract the file dinput8.dll to the release sub-folder of Prey. For example: 'C:Program Files (x86)SteamsteamappscommonPreyBinariesDaniellex64Release'
Start the game like you would normally, for example directly through Steam or Big Picture mode
Important: If the fix does not work, make sure that you have turned off the usage of the Steam Controller API (see below)
Features
While Prey originally offered good controller support, patch v1.05 introduced various issues. Instead of choosing either XInput or the Steam Controller API based on the user settings, the game always uses the latter. This results in problems with the movement as well as certain controller settings or the controller not working at all if the user has disabled the usage of the Steam Controller API in game's properties in Steam.
This fix re-enables XInput support and forces the game to use it, regardless of the settings.
Instructions
Supported Versions
This fix is designed for the latest, fully patched version of Prey and the Mooncrash DLC and might not work when used with older or otherwise modified executables.
Steam v1.08
Note that the fix currently does not work with the demo version of the game.
Install
The fix does not make any permanent changes to the game or to Windows and can easily be removed.
Important: When using a non-XInput controller such as the DS4, you will need a XInput emulator like DS4Windows for this fix to work
Open the archive and choose the button prompts you want to use by opening the corresponding folder
Extract the file dinput8.dll to the release sub-folder of Prey. For example: 'C:Program Files (x86)SteamsteamappscommonPreyBinariesDaniellex64Release'
Start the game like you would normally, for example directly through Steam or Big Picture mode
Important: If the fix does not work, make sure that you have turned off the usage of the Steam Controller API (see below)
Although the fix forces the game to use XInput, it is necessary to disable the usage of the Steam Controller API in the game's settings.
The safest way to do this is the following:
In the Steam client go to the menu Steam -> Settings -> Controller -> General Controller Settings
Make sure PS4/XBox Configuration Support is checked
Go to Big Picture mode and find Prey in you library
Click Mange Game -> Controller Options and uncheck Use Steam Configuration for Non-Steam Controllers
Uncheck the setting from step 1 again, depending on whether it was checked in the first place
Uninstall
Remove or rename the dinput8.dll from the folder of the game.
Known Issues
There are currently no known issues with using the fix.
Additional Information
Antivirus Software
Since this fix consists of an executable DLL file that uses 'hacking techniques' such as injection and hooking, it could be classified as malicious by antivirus software. In that case, it might be necessary to add an exception rule to the scanner.
If you lack the trust in random people on the internet -- and I would not blame you -- feel free to use a meta online virus scanner like VirusTotal to verify the file.
Loading Other Fixes/Mods/Injectors
To increase the compatibility with other mods or injectors that are using a wrapper DLL, this fix offers two methods for remote loading of additional files. Note that there might still be compatibility issues between the different fixes, mods or injectors that have nothing to do with the loading process.
File method:
The fix will load another dinput8.dll automatically if it has the name dinput8_Remote.dll. Just rename the DLL you want to load accordingly. Using this method will lead to an error if the renamed DLL is not itself a dinput8.dll.
Folder method:
The fix will also automatically load all DLLs regardless of their names in a dinput8_Remote sub-directory. Just create a corresponding folder in the install directory of the fix. This is the only way to load multiple (conflicting) files.
Contact And Support
If you like this fix and want to support the development or show your appreciation with a donation, you can find more information on my website. There you can also find out more about other mods that I have done and means to contact me if you have a question, want to provide feedback, bug reports and suggestions.
Version History
v1.1:
Fixed launch issues for users that do not own the Mooncrash DLC
v1.0:
Upgraded the fix to game version v1.08
v0.6:
Added support for Mooncrash DLC
v0.5:
Upgraded the fix to game version v1.06
v0.4:
Controller movement no longer gets stuck on interactive items when using PS4 prompts
v0.3:
Added a separate version that shows button prompts of the PS4 instead of the XBox controller
Added more detailed instructions to the readme file
v0.2:
Added support for demo version of Prey
Added measures to make the fix more robust to updates of the game
v0.1:
Initial release - By MethanhydratTL;DR
The DirectInputFpxFix fixes an input related FPS drop/slowdown problem that occurs in FEAR, its expansions, Condemned: Criminal Origins and other games. It is easy to install and does not require manual disabling of HID devices.
Quick start guide:
Extract the file dinput8.dll to the folder containing the executable of the game. For example: 'C:Program Files (x86)SteamsteamappscommonFEAR Ultimate Shooter Edition'
Start the game like you would normally, for example directly through Steam or GOG Galaxy.
Features
The DirectInputFpsFix fixes a bug that causes the FPS to severely drop after a few minutes of play. This problem is probably most widely known in regards to the game FEAR and often occurs in conjunction with the usage of Logitech devices.
However, the problem also crops up in other games using the same engine, such as the FEAR expansions or Condemned: Criminal Origins and with non-Logitech hardware configurations. A similar problem has also been reported to occur in other titles, like Prototype.
Although this issue can often be fixed by disabling most/all HID-Devices in the device manager, it is bothersome to do so and lately some people reported that that solution does not even work at all anymore, especially on machines running Windows 10.
Instructions
Supported Games
The fix is agnostic towards the game that uses it and should therefore work with all versions of a supported game, including the Steam, GOG and retail versions.
Confirmed:FEAR and its expansions
Condemned: Criminal Origins
[*]Supposedly:
Prototype
Kane & Lynch: Dead Men
Feel free to provide feedback if the DLL works on other games as well.
Install
The fix does not make any permanent changes to the game or to Windows and can easily be removed.
Extract the file dinput8.dll to the folder containing the executable of the game. For example: 'C:Program Files (x86)SteamsteamappscommonFEAR Ultimate Shooter Edition'*
Start the game like you would normally, for example directly through Steam or GOG Galaxy.
*Note that for the FEAR expansions the fix also has to be installed into the corresponding sub-folder of the game
Uninstall
Rename or remove the dinput8.dll from the folder of the game.
Known Issues
There are currently no known issues with the fix.
Additional Information
Antivirus Software
Since this mod consists of an executable DLL file that uses 'hacking techniques' such as injection and hooking, it could be classified as malicious by antivirus software. In that case, it might be necessary to add an exception rule to the scanner.
If you lack the trust in random people on the internet -- and I would not blame you -- feel free to use a meta online virus scanner like VirusTotal to verify the file.
Loading Other Fixes/Mods/Injectors
To increase the compatibility with other mods or injectors that are using a wrapper DLL, this fix offers two methods for remote loading of additional files. Note that there might still be compatibility issues between the different fixes, mods or injectors that have nothing to do with the loading process.
File method:
The mod will load another dinput8.dll automatically if it has the name dinput8.dll. Just rename the DLL you want to load accordingly. Using this method will lead to an error if the renamed DLL is not itself a dinput8.dll.
Folder method:
The mod will also automatically load all DLLs regardless of their names in a dinput8 sub-directory. Just create a corresponding folder in the install directory of the mod. This is the only way to load multiple (conflicting) files.
How This Works
The fix is implemented using a common technique known as DLL hooking.
User input in games like FEAR can be realized via DirectInput, an API by Microsoft for interacting with HID-Devices. The library is ancient and should no longer be used today, because there are other ways to get mouse and keyboard input, especially for games.
The FPS drops happen because the thread that runs DirectInput massively slows down after a while (as can be seen in tools like ProcessExplorer).
If an application uses a library like DirectInput, it needs a so-called DLL (dynamic-link library) where the functionality of the library is stored. In many cases, especially for libraries provided by Microsoft, these DLLs usually reside in the Windows folder.
However, there is an order of how an application searches for the DLLs it needs. Since the DLL of the fix gets copied into the main folder of the application and has the same name of a DLL needed by the game (the one of DirectInput), it gets loaded instead of the one in the Windows folder.
This means that all calls to DirectInput go through the Hook-DLL and can either be directed to the original DLL in the Windows folder or changed as necessary. This also allows some insight in how exactly the library is used by the game.
It turned out that some games not only unnecessarily register all HID-devices, they also call several functions every frame that usually only should be called once during initialization. The latter seems to apply only to devices that are not keyboards or mice. This eventually leads to circumstances where a lot of time is spent opening and closing device connections.
The fix changes the DirectInput initialization in such a way that only keyboard and pointer devices get registered.
Contact And Support
If you like this mod and want to support the development or show your appreciation with a donation, you can find more information on my website. There you can also find out more about other mods that I have done and means to contact me if you have a question, want to provide feedback, bug reports and suggestions.
Who's Online 1 Member, 0 Anonymous, 240 Guests(See full list)
Recently Browsing 0 members
No registered users viewing this page.
Member Statistics
3,870
Most Online