General

It is now possible to feed Virtual Xbox devices (vXbox) in a similar way you used to feed vJoy devices. This preliminary release is intended for users and developers alike - this release will enable the user to use existing feeders with vBox devices and to write new feeders.

Limitations

• No feedback (FFB, LEDs) support yet.
• Need manual installation and removal

Installation

Virtual Bus

vXbox devices are plugged-in into a Virtual Bus (ScpVbus). First, you need to install the bus. If an older version is installed, remove it. (Sometimes the removal takes effect only after reboot - to be fixed)

1. Download file ScpVBus_x64.zip or ScpVBus_x86.zip (attached) and open it in a folder (e.g. C:\TEMP)
2. Start a Command-line (DOS) window as Administrator.
3. CD to the folder containing the files (e.g. C:\TEMP\ScpVBus-x64)
4. Type the following command: devcon.exe install ScpVBus.inf root\ScpVBus This will Install the bus.
5. Later, if you wish to uninstall the bus, type: devcon.exe remove root\ScpVBus

Redirect Feeder

Your current feeder uses file vJoyInterface.dll located with the feeder. You should replace it with the attached files, as follows:

1. Rename the original file to Orig_vJoyInterface.dll for future use.
2. If your computer is a 32-bit machine - Copy file vJoyInterface-x86.dll (attached) and rename it to vJoyInterface.dll
3. If your computer is a 64-bit machine - Copy file vJoyInterface-x64.dll (attached) and rename it to vJoyInterface.dll. If the feeder fails to start - try using the other file.

New API

Although I did not get down to write a proper document, you will find what you need in the header file.

Values

The min/max values for Xbox are: For Axes: -32768 to 32767 For Triggers: 0 to 255

Status

Call function isVBusExists() to make sure the Virtual Bus was installed. Call functions isControllerExists() and isControllerOwned to get the status of a given vXbox device:

• Exists means it is plugged-in either by this process or by another process.
• Owned means it is plugged-in by this process

You must plug in a device before you can feed it. If already plugged in you can either unplug it or start feeding it.

Acknowledgments

Most of the work was done my the mysterious Scarlett.Crush. The project is currently maintained by the resourceful nefarius that collaborates with me with plenty of good will.

General

It is now possible to feed Virtual Xbox devices (vXbox) in a similar way you used to feed vJoy devices. This preliminary release is intended for users and developers alike - this release will enable the user to use existing feeders with vBox devices and to write new feeders.

Limitations

• No feedback (FFB, LEDs) support yet.
• Need manual installation and removal

Installation

Virtual Bus

vXbox devices are plugged-in into a Virtual Bus (ScpVbus). First, you need to install the bus. If an older version is installed, remove it. (Sometimes the removal takes effect only after reboot - to be fixed)

1. Download file ScpVBus_x64.zip or ScpVBus_x86.zip (attached) and open it in a folder (e.g. C:\TEMP)
2. Start a Command-line (DOS) window as Administrator.
3. CD to the folder containing the files (e.g. C:\TEMP\ScpVBus-x64)
4. Type the following command: devcon.exe install ScpVBus.inf root\ScpVBus This will Install the bus.
5. Later, if you wish to uninstall the bus, type: devcon.exe remove root\ScpVBus

Redirect Feeder

Your current feeder uses file vJoyInterface.dll located with the feeder. You should replace it with the attached files, as follows:

1. Rename the original file to Orig_vJoyInterface.dll for future use.
2. If your computer is a 32-bit machine - Copy file vJoyInterface-x86.dll (attached) and rename it to vJoyInterface.dll
3. If your computer is a 64-bit machine - Copy file vJoyInterface-x64.dll (attached) and rename it to vJoyInterface.dll. If the feeder fails to start - try using the other file.

New API

Although I did not get down to write a proper document, you will find what you need in the header file.

Values

The min/max values for Xbox are: For Axes: -32768 to 32767 For Triggers: 0 to 255

Status

Call function isVBusExists() to make sure the Virtual Bus was installed. Call functions isControllerExists() and isControllerOwned to get the status of a given vXbox device:

• Exists means it is plugged-in either by this process or by another process.
• Owned means it is plugged-in by this process

You must plug in a device before you can feed it. If already plugged in you can either unplug it or start feeding it.

Acknowledgments

Most of the work was done my the mysterious Scarlett.Crush. The project is currently maintained by the resourceful nefarius that collaborates with me with plenty of good will.

General

It is now possible to feed Virtual Xbox devices (vXbox) in a similar way you used to feed vJoy devices. This preliminary release is intended for users - this release will enable the user to use existing feeders with vBox devices. Designers of feeders will please wait for the release of a new API (soon). The new API will enable the writing of efficient and robust vXbox feeders.

Limitations

• No feedback (FFB, LEDs) support yet.
• Unreliable detection of vXbox devices
• Need manual installation and removal

Installation

Virtual Bus

vXbox devices are plugged-in into a Virtual Bus (ScpVbus). First, you need to install the bus.

1. Download file ScpVBus.zip (attached) and open it in a folder (e.g. C:\TEMP)
2. You will need only one of the contained folders, according to your computer (64/32 bit)
3. Start a Command-line (DOS) window as Administrator.
4. CD to the folder containing the files (e.g. C:\TEMP\ScpVBus-x64)
5. Type the following command: devcon.exe install ScpVBus.inf root\ScpVBus This will Install the bus.
6. Later, if you wish to uninstall the bus, type: devcon.exe remove root\ScpVBus

Redirect Feeder

Your current feeder uses file vJoyInterface.dll located with the feeder. You should replace it with the attached files, as follows:

1. Rename the original file to Orig_vJoyInterface.dll for future use.
2. If your computer is a 32-bit machine - Copy file vJoyInterface-x86.dll (attached) and rename it to vJoyInterface.dll
3. If your computer is a 64-bit machine - Copy file vJoyInterface-x64.dll (attached) and rename it to vJoyInterface.dll. If the feeder fails to start - try using the other file.

Acknowledgments

Most of the work was done my the mysterious Scarlett.Crush. The project is currently maintained by the resourceful nefarius that collaborates with me with plenty of good will.

This is a minor release that:

• Fixes bugs in the Kernel - should improve driver stability
• Fix bug in the C# wrapper DLL (Thank you Thierry) - Button 128 was interpreted as button 63.
• Fix bug in uninstaller - removing vJoy sometimes left Ghost devices on the system.
• Fix bug in installer - In rare cases, the installed would indicate failed after a successful installation

For Information and Downloads refer to the home site.

This is a minor release that fixes minor problems and also:

• Improved JoyMonitor included
• Better file versioning.
• Tested for Windows 10 (Fixing a few bugs)
• Solves some of the cases where the installer just waits forever
• Installation on Vista may now require rebooting
• Installer supports flag VERYSILENT

Note: If you are happy with the currently installed vJoy - no need to install this minor release

Maintenance Release - No new features Driver was migrated to a VS2015 solution (vJoy.sln) Applications were migrated to VS2013 solution (vJoyApps.sln) One batch file does it all - Compiles, signs and packs for installation

Known Issues:

1. SDK not included yet
2. .NET 4.0.3 only (Need to move to 2.0)
3. Installer hangs on Vista