Fix the usage pages for simulation usages. #30
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Getting the usage pages right is important, because DirectInput will make determinations about "device type" by looking at the usage-page/usage combination (which is not the only way to influence what "device type" DirectInput thinks we are, but is the easiest way for the time being). Some applications care about the device type.
|
Creating a draft pull request, I will test it in a few games and get back to you. |
…axes. As an aside, I can't find source code for the monitor app that actually ships with vJoy
|
Also attaching an image that shows the "ideal" configuration for "driving 2 pedals" game controller type. |
|
Tried it in a few games and it's working as expected: the Criterion games NFW MW, HP, Burnout, as well as Crew 2, which all detect vJoy as a "wheel" now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Getting the usage pages right is important, because DirectInput will make determinations about "device type" by looking at the usage-page/usage combination (which is not the only way to influence what "device type" DirectInput thinks we are, but is the easiest way for the time being). Some applications care about the device type.