Xidi v4.3.1

Changes and improvements this release:

• When using the WinMM wrapper, write to all button positions, even those that have space available for them but are not technically supposed to be present per the documented API (#70).
• Improved logging and enforce XInput device hiding so applications cannot bind directly to XInput devices and bypass Xidi, while at the same time making Xidi look like it is not aware that the device supports XInput (#71).
• Resolves compatibility issues with some games that ask for specific axes when setting up their DirectInput data format (#78).

Xidi v4.3.0

This is a long-overdue update that adds some requested features and customizations.

New features in this release:

• Force feedback effect strength adjustment, controlled by the new ForceFeedbackEffectStrengthPercent configuration setting in the Properties section (#67, #80)
• Circle-to-square correction for analog sticks, with a configurable amount, controlled by the new CircleToSquarePercentStickLeft and CircleToSquarePercentStickRight configuration settings in the Properties section (#69)
• Short virtual controller names as a workaround for applications that cannot display the long-form "Xidi Virtual Controller #" names, controlled by the new UseShortVirtualControllerNames configuration setting in the Workarounds section (#85)

Xidi v4.2.0

Important notes:

• As part of improving compatibility and correctness, the internal identifiers (GUIDs) that Xidi uses to identify virtual controllers to applications and distinguish between them have changed. Some applications that have been previously configured to use a Xidi virtual controller may need to be reconfigured.
• Starting with this release, and as long as certificates continue to be reasonably available, all binaries that are part of official releases will be digitally signed.

New features and improvements in this release:

• Many more customization options are now available, particularly surrounding deadzone and saturation (#30) but also mouse axis emulation. It is not generally necessary to use them because applications will often set these via DirectInput, but they are available for those applications that cannot (or simply do not) avail themselves of this functionality.
• Compatibility has been increased. Xidi can work with Windows for ARM (#49, #52), and several issues have been resolved with virtual controller enumeration and especially force feedback (#48, #51).

Xidi v4.1.1

Improves DirectInput API compatibility with certain applications (#45) and adds additional workarounds that can be enabled in the configuration if necessary (#36, #42).

Xidi v4.1.0

New features in this release:

• Mouse emulation support (#15). Controller elements can now be mapped to mouse motion and button presses.

Other changes:

• XInput is now linked dynamically at run-time, meaning that various older versions of the XInput library are also supported. This can improve out-of-box compatibility with versions of Windows earlier than 10 (such as Vista, 7, and 8) but there is no guarantee Xidi will work properly on these versions.

Xidi v4.0.3

Changes and improvements this release:

• Resolved a controller identification issue with the WinMM form that prevented some XInput-compatible controllers from being recognized as such.
• Improved force feedback compatibility by adding some flexibility in how certain invalid force feedback effect parameters are handled (#35).

Xidi v4.0.2

Resolved some API compatibility issues with certain games and added support for workarounds for handling incorrectly-coded applications.

Xidi v4.0.1

Fixed a bug affecting initial controller state. Sometimes applications would get spurious controller input before the user actually provides a physical input on a game controller handled by Xidi.

Xidi v4.0.0

New features in this release:

• Force feedback/controller vibration support.

Other changes:

• Various fixes and compatibility improvements.
• Logging improvements to aid with debugging.

Xidi v3.1.0

New features in this release:

• Introduced two new types of element mappers
  • Compound: routes input from a single XInput controller element to multiple element mappers simultaneously
  • Invert: inverts input from a single XInput controller element and then forwards it to another element mapper
• Added more detailed error messages in the event of failure to parse an element mapper from a configuration file