X360ce Calibration

[Johnette Esteb]

Nowthe horizontal axis of right thumb is off, it consistently registers a force to the right, so in games where right thumb governs camera movement, the camera constantly moves horizontally. As you may imagine this is beyond annoying.

I tried the calibration feature of Windows 10 generic driver but for some reason it doesn't work only on that right thumb calibration (dpad and left thumb calibration works fine). It asked me to move the thumb to both extremes but doing that changes nothing (the thumb is still registering as tilted to the right).

I've been searching extensively for a way to change the sensitivity of my gamepads in Windows.In most games the joystick sensitivity is too high, so unless I very carefully and gently press the joystick, it's always sending a maxed output so my characters will always move at full speed.

Next thing I thought of was to go within the calibration file and manually change values to reduce sensitivity, but all I could find was this reference document in which I tried to see if I could access and change the registry values associated with the calibration, but I can't even find the "GameInput" folder within my registry.

Consider using an emulation software (x360, DS4Windows, etc) which causes your input commands to go through an easy to configure software layer. Such software tend to allow tweaking of sensitivity, deadzones, and other options. See below screenshot of x360ce (right) and DS4Windows (left).

Depending on how a game is coded, it can read joystick input via several ways. Though joystick handling is mostly standardized, with popular standards including XInput, DInput (legacy), Steam Input (if using Steam), or directly as a USB device (not sure how common this but I've seen this).

The Windows built-in joy.cpl calibration tool affects controllers that use XInput/DInput technology, and some games do ignore these settings. Its calibration functionality is rather limited too, so I would recommend the tools mentioned in the short answer above, but it is possible to manually tweak these settings.

Navigate to the registry keys of the respective controller,HKEY_CURRENT_USER\System\CurrentControlSet\Control\MediaProperties\PrivateProperties\DirectInput\VID_&PID_\Calibration\0\Type\Axes\. If you are unable to identify which key corresponds to your controller, I would recommend a tool called "USBDeview" by Nirsoft.

Modify the Calibration key which is mapped to a 12 byte binary value (encoded as ). So for instance, suppose we wanted the y-axis Calibration to be from 30-70 for a defective analog stick, with 45 centered stick. Then we Calibration mapped 12 bytes should be set to

I was having issues with my controller when playing Star Wars Jedi: Fallen Order, and found that the game loads XInput.dll, DInput.dll, HID.dll files. Interestingly, HID.dll is invoked when a PS4 joystick is used, thus the Windows joy.cpl calibration settings are ignored. Using DS4Windows causes the XInput.dll functions to be invoked instead, also fixing calibration issues.

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.

The x360ce (Xbox 360 Controller Emulator) may not need any introduction to many in the gaming community. But we feel it should deserve a noteworthy review and basics as to the hows and why that this software exists. The reason why this software is handy and at times almost essential to play certain games is due to the way they are programmed.

In case you have no-script enabled or for some reason cannot see the title video on this website. We have provided direct links for these videos. For more information about the standards we use on this site click here if you would like to know more.

Common sense will tell developers will go to where the market is. The highest place to sell your game, unless it's crazily complicated, is typically the console environment. Thus as a developer, you begin to program your game to conform to the standards of that environment. But after the game has been released for a while. Developers will branch out to other platforms to sell their games. Microsoft in particular made it very easy to port back and forth between Xbox and PC because everything relied on Direct X.

That's exactly what developers started to do. Instead of using archaic and complicated hooks such as the original xinput.dll which is version 1.0. Devs were using versions 1.1 to 1.3 versions which simply 'assumed' the mapping of each button to that of a classic Xbox 360 joystick. Depending on the gaming engine used this generated a series of problems. One of the biggest ones is that if you didn't have an official Microsoft Controller then the game will not even let you continue past its start screen.

Worse yet some games will completely ignore the fact you have a controller hooked up and only offer keyboard support for your game and that's it. For those who used my tutorial for zero delay controllers, The TigerGame Xbox Blog, or XBCD you will likely face this problem with a lot of PC games. The people who used the Chinese receiver blog will not because even though the receiver is a third-party controller most are hooking into it are still OEM Microsoft controllers.

First, we highly recommend that you download any binaries right from the source creator and not from some third-party blog like ours. Our mission is to try to keep everything as secure as possible but not everyone on the internet shares the same values as we do. So click here to go to the developer of the x360ce's website. The source website gives out the exe files directly with no requirement to extract anything. For those interested in a direct download without ever leaving this blog, we have created a link for you as well. Click here to download from our blog.

If you downloaded the files from the source website above you do not have to do this step. If you downloaded it from this blog then be sure and extract it to the C:\xb360ce\ folder as that will be the folder to which we shall work out.

When you download x360ce it will come in two versions. a 32-bit and 64-bit version. This does not mean what your OS is as much as what your game is. Older games will be 32-bit whereas newer games like GTA5 will be 64-bit. This is why it's a good idea to get both of them set up in case one of them fails for a newer game.

The first thing that it will say is that it cannot find any of the xinput DLL files. This is normal. Let x360ce create DLL files off of your windows folder. It is going to modify them and store it in the directory that you launched the executable out of.

The next window will come up asking you what to do with the new hardware detected. In this case, we are using the TigerGame Xbox drivers with an original Xbox Duke Controller. Click next to automatically search the x360ce database for this. It should find this driver definition real quick since it's still classified as an Original Xbox controller.

Once complete your joystick should come alive. If for some reason this is greyed out there may be a problem with the driver or hardware detection of your original joystick. This screen should be the point where you can pick up your joystick and move it around. See how bad your dead zones are. Verify all of your buttons are working. And see if there are any problems such as buttons and/or D-pad sticking or failure. You can also map buttons around in case you are using a fighting stick to match an Xbox 360 configuration.

Like the XBCD administrative tool, you can fine-tune the dead spots in tabs such as Advanced so that the shoulder button isn't being held down all of the time. And you can repeat these steps in the Left Thumb and Right Thumb tabs. You can then click on the General tab to test your settings quickly.

3a8082e126