x360ce: Install, and other stuff related to Directx and C++

[B.G.]

Introduction

Sometimes you just buy a gamepad like a Logitech F310, and for no reason, a game cannot detect your controller. Why?, cause the game is forced to use exclusively a Xbox 360 Controller for PC, and that's all.

Edit: Considering the first comment made below. I feel the need to add more information:
Logitech F310, F510, F710 you know use the xinput mode, so to clarify the intention of this text; I need to add this.

DON'T READ THIS IF:

• You are going to buy a 360 Controller Wired or Wireless for PC or Fx10 series by Logitech: that's the best option so
  
• You don't have the need to connect over 2 or more controllers to play a game

READ THIS ONLY IF:

• you're not going to buy a 360 Wired or Wireless Controller, or the USB receptor.
  
• You had a PS3 controller and Motioninjoy is not enough, or have problems with some games that you play: same to PS4 controllers.
  
• You have an old controller and you want to use it
  
• For some unexplained reason Fx10 series, can't work with a game
  
• You had in past a problem like -r6025.
  
• You need to connect a Direct controller and a xInput controller at the same time, for a game.

Even in other ways, you want to play some games that still have local Multiplayer, and when you connect the controlller, yes, you can't play. Maybe you only have one Xbox 360 Controller, maybe you don't have the original Xbox 360, so naturally you don't have controllers to buy the USB receptor.

x360ce is Xbox 360 Controller Emulator, this helpful but complicated software, is the tool that allows Gamepads to be working as a Xbox 360 controller, just filtering xInput calls.

But as everything in life, this Game Saviour can be a headache while configuring to get it working.

So this is why I'm here, and, provide a Guide to get this working even the on last version on Windows 8.1 (Cause is easier somehow on Windows 7), so let's the game begin:

What do you need?

• Every Visual C++, Updates for 2010, 2012, 2013 (Don't worry at all, I made up to this point uploading all of that in a single File for all of you)
  
• Install Microsoft .NET Framework 3.5 on both Windows 7 and Windows 8.1
  
• The x360ce (as above, another file for you guys)
  
• DirectX End User Runtime
  
• Ccleaner; just for Reg cleaning

What are you going to do?

Before START: Uninstall every C++ you can find on Programs list, and the Driver for your controller, pass Ccleaner over the Windows registry and reboot the system

Whenever the system requiere to reboot, just do it, in order to make this working correctly

1. FIRST: You need to install Net.Framework 3.5 on Windows 8.1, this is need to be the first step, cause when Directx is installed, if the package is not installed until that moment, some libraries are just ignored over the installation.
   
   For this we can use the Microsoft guide[msdn.microsoft.com] is simple and even have a video. If you don't want to check the URL, just go to Turn Windows features on/off and check .NET Framework, or the other way just run x360ce.exe and a pop-up windows will tell you about downloading .NET Framework 3.5 and 2.0.
   
   Reboot if system requires it.
   
   
2. After that we will now need the DirectX End-User Runtime, just go to the page and download[www.microsoft.com]
   
   Note: Make sure .NET Framework was installed before
   
   
3. Install every C++ from 2005 to 2013, for this you can go to this page and download all of them C++[support.microsoft.com], or download the ZIP[drive.google.com] I created for this.
   
   Note: The Microsoft download page seems to have problems with Chrome, so, if you can´t get the file to start downloading, use IE, Opera, Firefox, firstly IE, I'm using Opera
   
   
4. Download the x360ce, we're going to use to different versions the 2.0.2.163 Beta 2[drive.google.com] and 3.0.7.55[drive.google.com] just click over the numbers; those files were uploaded by me. In other way if you need the x64 version you can go to the x360ce Page: https://github.com/x360ce/x360ce, and get the x64 if you run a game on x64 (like Outlast)
   
   
5. Install Driver for your Controller
   
   
6. Reboot, just for security

x360ce

At this point just start the x360ce 2.0.2.163 Beta 2. The program will ask for create the xinput1_3.dll and the xbox360ce, and next the last pop-up window is about a New Device connected, just cancel.

If everything was good you this is what you're going to get: https://drive.google.com/open?id=0B0wLtx5-ZwskVURtUF9JdmlUekE

Just click over every Button and click over the Record; then only press the button on your gamepad refered to the same. For the D-Pad just go for D-Pad/D-Pads, and select.

Test every button until you get all configured correctly and when you press the button, the central 360 Controller image will put a Green Orb over the button emulated. To get something similar to this: https://drive.google.com/open?id=0B0wLtx5-ZwskczhYR2Y3Z0o0WVk

Just close and save changes.

Note: Put every x360 in its own Folder, they use different libraries and INI, so putting them together, is a conflict

If you reached this point. Congratulations!, maybe the next part is not necessary. At this point you can just copy the files: x360ce, xinput1_3.dll and x360ce.ini to the .EXE directory of every game, you want.

Note: Put that files together and, on the same place in where the .EXE is, or, where the BIN Folder (binary) files are. When the game start a BEEP sound is going to confirm that the program is working correctly

The last part is getting the x360 3.0.7.55 working. And why is this another step, is just a problem over how actually Windows 8.1 works.

When you start x360 3.0.7.55 on Windows 8.1 this new version uses the Device Configuration with Windows, this uses a file named joy.cpl; that cause conflicts over the system while configurating. Why this happens?, is just a bad call. And the program can't get the enough rights to check this, and finally you get something like this: https://drive.google.com/open?id=0B0wLtx5-ZwskVlZrZktVMWhlNEk

The "PAD0: Misconfigured device check GUIDs", is only how Windows 8.1 don't let the program itself to get on device configuration so, at this point the program fails cause it can't check if the device is working; so, is misconfigured.

How we can use the updated versions? (that for me works better), just copy the .INI file created with the 2.0.2.163 Beta 2 version to the folder in where the 3.0.7.55 version is. This is going to tell the program that the device is working and start correctly. And you get something like this: https://drive.google.com/open?id=0B0wLtx5-ZwskZl93TWNfeTBMTTQ

When you copy the .INI file and start the x360ce 3.0.7.55 version the program will ask for the xinput1_3.dll.

At this point everything should be working fine and charm.

Games, how to get this thing working

Well, as all, even if we managed to get here and get everything working, there's a bad part: some games needs additional configuration; so you'll be asking what we need to do.

Some games are older, or, they're working using other BIN files, this other files are xinput1_1, xinput1_2 or xinput9_1

Some games, like Eidos games: Hitman Absolution, Tomb Raider (2013), Deus EX: Human Revolution Director's Cut uses xinput1_1.dll, and a different type of hook for the sticks. So we can activate different options on x360ce panel for the 2.0.2.163 go to Options, and click on the file you need, an image for help: https://drive.google.com/open?id=0B0wLtx5-ZwskWjhlUXE0VXlVRDA

For the 3.0.7.55 is some kind of different, go to Game Settings and check Hook Mask as COM, and the files you need came as 32 bits or 64 bits with only 1.1, 1.2 and 9.1, and image for help: https://drive.google.com/open?id=0B0wLtx5-ZwskelNsblZnektBRG8

Note: IMPORTANT, some games are built to use the native xinput1_3.dll with steam, for this games, well, x360ce is not going to work, or at least I'm trying, I don't know how many games are build like this, but for an example: POSTAL2 Complete, seems to work like this, or maybe the .EXE is too old

Games Tested: Skyrim, Deus Ex HMDC, Hitman Absolution, Dirt 3, Grid Autosport, Serious Sam 3, Doom 3 BFG, Portal 2, NFS Undercover, NFS Shift, Shift 2 Unleashed, RE4 HD, RE5, RE6, Castle Crashers (problems, Keyboard still working :c), Bioshock, Bioshock 2, Bioshock Infinite, Just Cause 2, RAGE, State of Decay, Alan Wake, Dead Rising 2, Dead Rising 3, Castlevania Lod, Castlevania Lod 2.

More games were tested, but I forgot some of them.

Final notes and conclussions

• This guide not only allows to x360ce to work properly; actually helps to anyone who is having problems with Directx libraries,and MSVCP libraries too. Cause you install full libraries of DirectX even that ones from DX9, and all the Redistributables from c++.
  
  
• For preventing a major problem that make everyone cry: Make sure to check constantly C++ over the program list. Why?, well, when Steam installs a game, some of them, still installs a version of C++ that might be older; the bad thing is that this can create a problem related as -r6025, when virtual calls fail. This can be solved in two ways: Uninstalling every c++ or installing the O.S. again.
  
  Just check, 2 entries for every version, x64 and x86 only one for both of every c++ version from 2005 to 2013. If other one is there, check the version an uninstall the previous one. You need only the last ones.

Hope this helps.

[Bad 💀 Motha]

Logitech F310 / F710 have a switch on there for Direct vs X input mode; so if a game fails to detect it under one mode, it should detect it on the other mode. However you need to restart the game before switching modes.

There should be no reason for x360ce with those Controllers. If so, you are doing something really wrong.

As for Visual C++, it is a series of Runtime Libraries, so it should in no way be of harm to have multiple versions installed, as that is actually needed. Just like .NET Framework or DirectX.

[Bad 💀 Motha]

Those Logitech ones are fairly solid though since they support both mode types.

But yea, Xbox 360 or One Controllers are very solid as well.

[Mario]

Good Info !

[B.G.]

Once time ago I had that mistake of r6025 consecutive times. Problem: Leaving different versions of the same package:

Having C++ 2005 and C++ 2005 SP1 is not a problem
Having C++ 2005 x86 and x64 is not a problem

Having C++ 2005 x86 (Example) 8000.9001 and 8000.9002 that's a problem. Actually is a problem when some games install the VC Redist on Steam, and force the installation ignoring the upgrade protocol, even this can install the same version twice.

This is a simple Virtual Call malfunction: When the game needs C++ 2005 an uses the example: 8000.9001 this creates an instruction, but if somewhere in Windows uses the 8000.9002 as response to the game, this is exactly when the game and system crashes; directly to -R6025.