Many To One (technically many to many) Virtual Joystick Feeder. Maps one or more physical joysticks to one (or more) virtual joystick.
A few scenarios where this might be useful:
- Combine input from two controllers into one virtual controller such as a flight stick and throttle. Allowing each controller to feed information to a different set of buttons/axis.
- Combine input from two or more controllers into one virtual controller where each controller is mean to be used exclusively of the others (one at a time). This is good for a setup where the user has the option to select from multiple joysticks but you don't want to rempa the application each time a differnt controller is used.
- An application doesn't recognize a controller but will recognize a vJoy controller. In this case the virtual controller is just being used as a pass through for the physical controller.
- Multiple players for a single player game where several people have their own controller and can either take turns controlling the game or have specific tasks (input controls) they are responsible for.
- Heads up/on on one games can be converted to multi player team games. An example would be with a fighting game such as Street Fighter II, each character could be mapped to a virtual joystick being feed by a team of one or more players. The players would then need to coorindate their movement to control the character.
This application runs on Windows and is based on vJoy by Shauleiz and ScpVbus by Benjamin Höglinger (@nefarius). It requires one or both of these to be installed and working (depending on what type of controller you want to emulate). vJoy does not emulate Xbox devices, if you need a virtual Xbox device (vXbox) use ScpVbus.
- https://github.com/jshafer817/vJoy/releases (jshafer817 released this on Jul 14, 2019)
- https://github.com/shauleiz/vJoy/releases (Shauleiz released this on May 27, 2018)
- http:https://vjoystick.sourceforge.net/site/index.php/download-a-install/download (Older versions)
- http:https://vjoystick.sourceforge.net/site/index.php/vxbox (download with instructions)
- https://github.com/nefarius/ScpVBus
The feeder sends the last data it received from a given controller to the virtual joystick. The simplest way to use this is when only one controller will be used at a time, or when only two or more joysticks are used in tandom but not utilizing overlapping controls. For example, using the X and Y axis from one joystick and the Z axis from a second joystick.
The most confusing way to utilize controller mapping is when you want to use two or more controllers at the same time to control the same action in the aplication as in the Heads up example from above. This can be very entertaining. For example, if two controllers (Joystick1 and Joystick2) are connected to one virtual joystick (vJoy1), the following scenarios will play out when input is received...
- Joystick1 presses and holds Button1 - vJoy1 presses and holds Button1
- Joystick2 presses and holds Button1 - no change
- Joystick2 releases Button1 - vJoy1 releases Button1
- Joystick 1 releases Button1 - no change
In the above scenario Joystick2 usurped the button press of Joystick1.
- Joystick1 moves left 50% and holds - vJoy1 moves left 50% and holds
- Joystick2 moves left 100% and the recenters - vJoy1 moves left 100% (from 50%) and then ceneters
- Joystick1 moves left 100% (from 50%) and then recenters - vJoy1 moves left 100% (from center) and then recneters
In the above scenario left movement might appear erratic as the two joysticks change their positions.
You first need to install either vJoy or ScpVbus. ScpVbus emulated controllers are supported by mroe modern Windows programs than vJoy. It emulates a traditional xBox controller. Next download and install MTOvJoyFeeder. I recommend running the console application from the command line. Click on the Windows Key, type CMD and hit enter, then change directories (cd) to where you installed MTOvJoyFeeder. Entering MTOvJoyFeeder and hitting enter will run the application. Hitting Ctrl-c will exit the application. When you run MTOvJoyFeeder for the first time it will scan for all of your connected controllers and automatially generate a file called MTOvJoyFeeder.json in the installed directory. This file will be created anytime it does not exist. You can specify the name and location of this file in the MTOvJoyFeeder.exe.config file or on the command line when the application is run (enter MTOvJoyFeeder.exe --help for help with command line options).
The automatically generated MTOvJoyFeeder.json file will map every physical controller to the first virtual vJoy controller and the first virtual vXbox controller, regardless if they exist. You will need to modify the MTOvJoyFeeder.json in your favorite text editor and change the numbers between the brackets for Map_To_vJoyDevice_Ids and Map_To_xBox_Ids to the ids of the virtual controllers you want the physical controller mapped to. You can delete any controllers from the file that you do not want to map or simply delete the numbers between the brackets to exclude mapping the physical controller to either a vJoy or vXbox device. Multiple Ids may be added seperated by commas to map a single physical device to multiple virtual devices.
Example:
"Map_To_vJoyDevice_Ids": [ 2, 3 ],
"Map_To_xBox_Ids": [ 4 ],
- Move some properties from JoystickInfo to JoystickConfig, currently there are some repeated elements that just get copied from JoystickConfig to JoystickInfo
- Determine current support for Force Feedback in vJoy/vXbox/SharpDX
- Add timer to detect controllers when they are added
- Create Windows Service
- Create Launchbox plugin
- Improved documentation/installation instructions
- Need to load state for PointOfViewControllers1 - PointOfViewControllers3
- Investigate implementing oJoystickInfo.oJoystick.SetNotification()
- Clean up some calls to WriteToEventLog that are using String.Format
- Wire up Guide button when SharpDX supports it - sharpdx/SharpDX#1074
- Support ViGEm Bus Driver - https://github.com/ViGEm/ViGEmBus
- Loads all joystick data and virtual joystick data
- Loop that directs all input from acquired joysticks to first virtual stick
- Adding support for a configuration file
- Added configuration name/location settings to app.config
- Accepts configuration location from command line
- Added mappings for joysticks from config
- Added If DEBUG directive around Polling logging
- Added handling of removed controller
- Added WriteToEventLog to replace all Console.Write calls
- Added better configuration/command line handling.
- Added support for multiple virtual controls associated with physical controllers
- Added config support for SleepTime
- Realised vJoy doesn't emulate xBox controllers!
- Converted using vJoyInterface to vGenInterface to get both vJoy and xBox controller support
- Found out plugining in xBox controllers in vGenInterface is buggy and didn't work
- Added vXboxInderface.dll support using vXboxInterfaceWrap.cs, kept vGen interface for vJoy
- In process of wiring up vitual controls to xBox
- Added an onExit routine to release vXBox joysticks
- Normalized and wired up Z Axis
- Wired up Diagonals on DPad for XBox Controller
- Validated All XBox inputs - Guide Button is the only one left to wire up
- Upgraded packages
- Added shell for Windows Service
- Moved console application to its own directory
- Cleaned up debug code
- Added output for release mode
- Improved vxBox ReleasevXboxJoysticks method
- Fixed max value for in vXboxInterfaceWrap as it was 1 higher than it should have been causing the number to go negative on conversion to a Short
- Added inversion option to physical joysticks an support in NormalizeRange(), normally the Y Axis will be inverted for XBox controllers
- Added Ranges For X, Y, Z, RX, RY for controllers and virtual controllers for use by NormalizeRange()
- Tested NormalizeRange()
- Added formatting to JSON output to remove extra newlines and spaces before integers in arrays
- Fixed issue with not dynamically setting size of oNewJoystickInfo.Map_Buttons array by using JoystickConfig.Map_Buttons instead
- Added an Assets folder to hold references and copy out required files from
- Made vXbox Y and RY inverted by default so directions match with vJoy
- Added to this documentation
- Fixed CommandLineParser's (https://github.com/commandlineparser/commandline) help display as it wasn't working due to the placement of a private variable between the [Option] and the public property definition.
- No longer monitors physical controllers that are not mapped to a virtual controller
- General messaging cleanup
- Added Fody.Costura (https://github.com/Fody/Costura) to consolidate all resources into the executable
- Changed the config file from using MTOvJoyFeeder.EXE.config to using MTOvJoyFeeder.config
- MTOvJoyFeeder.config file is not deployed with the application but generated from defaults when first run
- Added auto update routines with support for "updates" and "PreviousVersion" directories
- You can now exit the application by hitting the [Esc] or [Backspace] keys while the command window has focus