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).