v2.1.8 Build 39 -Windows 10 1803 bug fix

Bug fix:

Problem: When moving to Windows 10 release 1803 some users found that vJoy driver stopped functioning. This was manifested in cases where vJoy devices were configured with zero buttons.

Fix: This version of vJoy include configuration apps that do not cause such a problem.

Recovery: Before installing this version of vJoy make sure the previous configuration (if causes problems) is removed: Run vJoyConfig -r then install this version of vJoy.

v2.1.8 Build 38 - Spring Effect

Bug fix:
Spring effect was not properly detected by system due to erroneous commenting out of the spring entries in the INF file

v2.1.8 Build 37 - Efficiency Improvement

No functional changes.
Architectural changes yielded impressive Efficiency Improvement.

v2.1.8 Build 36 - Bug fix

Bug description:
Under heavy load vJoy sends arbitrary and momentary data to causing a glitch in the device position.

Status:
Fixed

Additional documentation and downloads
See previous release

vJoy 2.1.8 RC3

Version 2.1.8

This version is designed to be the final version of vJoy. vJoy has been around for about a decade and is ripe now. I will still be around for a while for answering questions and fixing minor bugs.

I recommend all projects to start collaborating with nefarius on his emerging project ViGEm - I believe that his approach is better and more flexible than the one employed by vJoy.

Release Notes for vJoy 2.1.8 build 33

vJoy API file (vGenInterface.dll) added to the installation

Release Notes for vJoy 2.1.8 build 31

• Enhancement: New interface function GetOwnerPid(). This function returns the ID of the process owning a specified vJoy device. You can use this function to:
• Make sure that your process is indeed the owner of a device.
• Get the process that prevents you from acquiring the device and issue an intelligent message to the user.
• Facilitate killing zomby processes that still own a device.
• Enhancement: vJoyList - a utility that lists all vJoy devices and specifies the owner of each device.
  vJoyList is part of the installation.

• Enhancement: Smoother initialization of a vJoy device. A device is initialized when created, configured or requested to from the API. It retains its position when acquired to prevent a glitch.
• Bug Fix: Initializing discrete POVs to non-default values was incorrectly done. It is now possible: Discrete POV registry values are now:
• 0x80: North/Forwards
• 0x81: East/Right
• 0x82: South/Backwards
• 0x83: West/Left
• 0x8F: Neutral Point
• Bug Fix: Too many error messages were written to the event log even on normal installation.

vJoy 2.1.8 RC2

Version 2.1.8

This version is designed to be the final version of vJoy. vJoy has been around for about a decade and is ripe now. I will still be around for a while for answering questions and fixing minor bugs.

I recommend all projects to start collaborating with nefarius on his emerging project ViGEm - I believe that his approach is better and more flexible than the one employed by vJoy.

Release Notes for vJoy 2.1.8 build 31

• Enhancement: New interface function GetOwnerPid(). This function returns the ID of the process owning a specified vJoy device. You can use this function to:
• Make sure that your process is indeed the owner of a device.
• Get the process that prevents you from acquiring the device and issue an intelligent message to the user.
• Facilitate killing zomby processes that still own a device.
• Enhancement: vJoyList - a utility that lists all vJoy devices and specifies the owner of each device.
  vJoyList is part of the installation.

• Enhancement: Smoother initialization of a vJoy device. A device is initialized when created, configured or requested to from the API. It retains its position when acquired to prevent a glitch.
• Bug Fix: Initializing discrete POVs to non-default values was incorrectly done. It is now possible: Discrete POV registry values are now:
• 0x80: North/Forwards
• 0x81: East/Right
• 0x82: South/Backwards
• 0x83: West/Left
• 0x8F: Neutral Point
• Bug Fix: Too many error messages were written to the event log even on normal installation.

vJoy 2.1.8 RC1

Version 2.1.8

This version is designed to be the final version of vJoy. vJoy has been around for about a decade and is ripe now. I will still be around for a while for answering questions and fixing minor bugs.

I recommend all projects to start collaborating with nefarius on his emerging project ViGEm - I believe that his approach is better and more flexible than the one employed by vJoy.

Release Notes for vJoy 2.1.8 build 24

• Enhancement: New interface function GetOwnerPid(). This function returns the ID of the process owning a specified vJoy device. You can use this function to:
• Make sure that your process is indeed the owner of a device.
• Get the process that prevents you from acquiring the device and issue an intelligent message to the user.
• Facilitate killing zomby processes that still own a device.
• Enhancement: vJoyList - a utility that lists all vJoy devices and specifies the owner of each device.
  vJoyList is part of the installation.

• Enhancement: Smoother initialization of a vJoy device. A device is initialized when created, configured or requested to from the API. It retains its position when acquired to prevent a glitch.
• Bug Fix: Initializing discrete POVs to non-default values was incorrectly done. It is now possible: Discrete POV registry values are now:
• 0x80: North/Forwards
• 0x81: East/Right
• 0x82: South/Backwards
• 0x83: West/Left
• 0x8F: Neutral Point
• Bug Fix: Too many error messages were written to the event log even on normal installation.

Bugfix in API

Read Pull Request for more information

v2.1.7 Release Candidate

Version 2.1.7RC1

Including two packages:

• vJoy 2.1.7 installer
• vGenInterface API packages for x86/x64 platforms

Known Issue:

Bug in initializing Discrete POVs - will be fixed in v2.1.8

Preliminary release of 2.1.7

Functional vJoy Interface
Functional vGen interface (To be separated later)

Known Issues:

• Reset POV/Buttons sets incorrect values when first called
• Reported: GetVJDStatus() is very slow