Several semi-major bug fixes, added experimental modes, etc.

The new modes are partially untested, but they allow you to communicate back and forth between clients and a server. This may be used for multi-instance setups for games. Assuming you get it working, there's no guarantee the games will remain synchronized. In addition, IOSync does not currently time the applications. This means you're bound to get problems. This is more of a proof of concept; further functionality coming soon. On the bright side, the existing functionality should be in working order. A ton of bug fixes were made, so you shouldn't have any problems.

As usual, you'll need to download the proper redistributable(s). Use this software at your own risk.

For information on using IOSync, click here.

Additional Configuration Options (AppData support), Dynamic-Linking Tweaks

IOSync now supports automatically saving to a dedicated application-data folder. This is optional, and local configurations take priority. To be more specific, IOSync saves to your "roaming" application-data folder when requested. In addition to this, IOSync now asks if you want to load your configuration, before automatically loading it. When using a "redirection" configuration-file, the local directory will be used, then, if a file was not found, your application-data will be checked.

IOSync now only links with dynamic libraries if they are available, and it may actually need to use them. This means servers don't need to link with XInput automatically. Only modes which enable detection will try to link with XInput. This goes for hosts/servers as well; IOSync will only link with vJoy (Dynamically; depends on configuration, official builds do this dynamically) if it will be simulating input, and vJoy support is enabled.

Other than that, there were some minor bug fixes.

DirectInput support using vJoy, minor fixes, etc.

This release provides support for vJoy. Basically, this may be used to map a gamepad state (XInput) sent from a client into a DirectInput state. This means controller support without the need for XInput injection. XInput injection is still ideal, however. Using the 'processes' property should be a lot easier now, so you shouldn't have any problems using XInput. That being said, a number of games and emulators use DirectInput, so the new vJoy functionality should cover it.

vJoy devices can be offset by using the 'vjoy_offset' property (Under the 'devices' section).

Older releases can be found here. Please download the proper Visual C++ 2013 redistributable(s).

Stability fixes, cross-architecture injection, etc.

I found a semi-major bug with XInput injection, and this should fix it. This should also fix a potential problem with reading the home/guide buttons on gamepads.

For details on using IOSync, please read the original release-page.
EDIT: Updated to V1.0.2: Configuration improvements; custom files , etc.

Stability fixes, cross-architecture injection, etc.

Please view the V1.0.2 release notes.

Initial release (Use at your own risk)

This is the first release of IOSync. Technically, I'm marking this as a pre-release, due to the nature of this program. As the title says, use this version at your own risk. Binaries will only be supplied when a version is deemed stable, or semi-stable. Do not expect this to be a perfect version of IOSync.

Functionality has been tested a decent bit, so there shouldn't be any major problems with these builds.

Binaries were built using Visual C++ 2013 (Community), please download the appropriate redistributable(s) before using this software. Builds are current provided for both the x86 and x64 architectures. Long-term support for x86 is not guaranteed, but I have no intention of dropping x64 in the long-term. XInput support should work on just about any system.

Testing has only been done on Windows 7 and Windows 8.1, stability is not explicitly guaranteed. That being said, these should work on any system that is supported by the 2013 redistributable(s).

For more information on using IOSync, please read the 'README' file, as well as the page(s) on the wiki.

If you find any bugs, feel free to report them.