Vjoy Installer

[Marieta Reeks]

Themain problem is that vJoy is not developed actively anymore and as it is a driver, it needs to be signed to allow installation.

Microsoft has made driver signing significantly more complicated and cumbersome than it was two years ago.

We are looking into the possibility of (maybe!) continuing development of vJoy ourselves.

In the meantime we will modify CLS2Sim to allow choosing which vJoy version to use.

Hello there, I just opened a ticket

I was able to install new vjoy driver BUT I lost 80% of my joystick buttons that are recognized in cls2sim v5.5 but no longer in msfs2020

I immediately return back to previous version until the problem will not be fixed.

Do you think my issue may be related to this? I only updated as I wanted to try the new Direct X implementation, but am currently unable to try this as when I run the USB config tool, I am getting an error ( see different thread)

Secondly, I have zero FFB effects in DCS, even though its connected and communicating, I have X & Y axis bound within DCS to both the Vjoy column and the CLSE joystick column in DCS controls options.

It have always annoyed me that I could not map the "off-positions" of the 2- and 3-way buttons on my Thrustmaster throttle. A two-way button will generate a "button-press" when toggled to one position, however when you toggle it to another position that "button-press" will simply go off, and it will not generate another button-press (hence nothing to map/bind). Likewise a 3-way button will only generate a "button press" in the up-position and another "button press" in its down-position, however it will not generate any "button-press" when put in its middle-position (e.g. the pinky-switch forward/aft will generate button-press 13/14, however nothing in its middle-position). I know you can handle this via Thrustmasters Target-software, however as your Target-profile boils down to a single virtual device (hence a finite/limited number of axis and buttons), I've always found it to be "too simple" for my taste (in this aspect the software for CH-products is much better). Also you can do it via various other 3rd party software, such as VoiceAttack or JoyToKey. However these are more complicated to setup, as you often have to create/use a specific profile for a specific aircraft, since they need to "send" specific key-combinations.

So back in 2019 I decided to write a small program that lets me do so via vJoy (that is a driver for up to 16 virtual joysticks, each with multiple axis and up to 128 buttons). Joy2vJoy is hard-coded to ONLY work with the Thrustmaster throttle and the vJoy driver is a requirement (vJoy is not bundled, but download links are listed below). I initially had plans to expand this program with support for additional devices and add scripting. At one point I had a development versions with LUA-scripting support, however it was not running reliable, so I scraped it. In its current form I have used this program with DCS since 2019 myself, and have never had any issues. The program is written to be light on CPU-usage, so your frame-rate in DCS is not affected, but I suggest you only enable "Update checkboxes" when testing how the software is working.

If you haven't done so already you need to install vJoy (links below) and create a single virtual Joystick with at least 21 buttons (I simply made one with 128 buttons). In the enclosed manual (PDF-file) I show how this device is created, and how you can test it is working, using the programs installed with the vJoy driver (you only have to do this once). From that point you simply need to run Joy2vJoy prior to starting DCS (or whichever sim/game you want to use it with). The way it works you map your physical buttons to actions in DCS using the physical Thrustmaster throttle (as per usual). However to map-up the "off-positions" of the various 2/3-way buttons you in stead need to map up "button-presses" on the jVoy device to the action you want to perform when a physical button goes off. E.g. for the DCS AH64 I use the 3-way pinky switch on the throttle to control NVS-OFF (aft), NVS-NORM (middle/off) and NVS-FIXED (forward). The Pinky-switch forward/aft generates button press 13 and 14 on the phycial throttle, so I use theese buttons on the physical device to map-up NVS-FIXED/OFF. However I then use button 13 on my virtual vJoy device to map to NVS-NORM. It is a coincidence that it is also button 13 on the virtual device, so either use the table in the PDF-manual too see which virtual button-presses are linked to which physical-buttons, or simply check "Update checkboxes" in Joy2vJoy and see what happens when you press the physical buttons on your Thrustmaster throttle (which check-boxes are checked/un-checked). In the screen-shot above (both "Activated" and with "Update checkboxes" are enabled), the check-boxes in the left side of the screen represent the physical buttons on your Thrustmaster throttle, and the check-boxes in the right side represent the virtual buttons of the 1st vJoy device.

Beside using vJoy for the Joy2vJoy software I also have begun using vJoy with my Stream Deck (SD). I started to use Joy2vJoy when I got the DCS F18, and for the F18 I made an SD-profile for the F18 simply sending key-combinations from SD to DCS. However it was a drag finding out which keyboad-combinations that were in use in DCS, which I needed to define/use both in DCS and SD (given many keyboard combinations that DCS will acccept, cannot be generated by SD). So for my AH64 SD-profile I instead decided to use a plug-in for SD that lets my SD button-presses generate vJoy button presses. So as of now I have no less that 5 vJoy-devices (virtual Joysticks) defined. The first vJoy device is only used with Joy2vJoy (can't be shared with the SD plug-in). However the other 4 vJoy-devices (each with 128 buttons) are only used with the SD plug-in. Hence via this plug-in I have no less than 512 virtual buttons in total, that I can map between SD and DCS. Even though you define devices with 128 buttons, there might be programs/games that are only able to see/use the first 32 buttons (however DCS can see/use all 128 buttons on each device). Another bennefit of using this vJoy plug-in for SD over generating key-presses is that you can use multiple buttons at the same time. E.g. pressing two SD-buttons (or more) at the same time, I can both increase the lights for SIGNAL and PRIMARY in the AH64 at the same time. Had I used traditional key-combinations, I would first have to increase one, and then the other. Here below is a link for that plug-in for SD, and a link for a package I made with nearly 300 (button) graphic-files to use if you want to build an AH64 SD profile. In the zip-file for the latter you also get a full list of which actions you could choose to map to actions for the virtual devices 2-5 (4 devices each with 128 buttons):

-vJoy

No there are no programming available, hence nothing to setup. I simply gives access to-/makes it possible to assign actions to the "off-positions" of the Thrustmaster throttle-buttons, so in DCS can assign actions to all 2/3-positions of your 2/3-way buttons.

First of all I expect that you unzipped all files bundled with the Joy2vJoy program to the same folder (it's own folder). Did you create vJoy device #1 with 128 buttons? Did you test that this device is working using vJoy Feeder/Monitor?

@Jokletox In next version I've added a program-argument (you can add to the short-cut) which will suppress this message. The message is displayed if there is a mismatch between the version of vJoy driver and the version of the vJoy dll.

Hi, Joy2vjoy is a great job, congratulations!

I have seen the video several times and carefully followed all the instructions, but DCS does not assign commands to virtual keys on the Vjoy device by clicking them in warthog, while clicking on the "Key / Button" drop-down menu the 128 keys are listed.If I assign the right virtual button from there (looking at the correct number on Juy2Vjoy), it assigns it, but then it doesn't work in game.

1 - I installed Vjoy V.2.2.0 (2.2.1 freezes at the end of the installation). I have assigned 128 keys to a virtal device and disabled the Force feedback effects and the configuration looks exactly like in the explanations.

2 -I tested Vjoy with feeder and monitor, and closed the programs before starting Joy2Vjoy (all Joy2Vjoy files are in the same folder as recommended). I also get the error (Warning v.joy Dll 536 and Driver version 544 doesn`t match) but everything starts perfectly.

Everything looks the same as the video tutorial, but in the DCS options the Vjoy peripheral does not feels the virtual keys, even if the x, y, z and rz virtual axes were assigned by default and I had to eliminate in the DCS axis assign folder because ingame they interfered with the joystick.

3a8082e126