A special case for controls with emulated headsets #8
Conversation
This file contains 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
…ion behind local font declaration
|
Thanks for that! I'll update the documentation too. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Closes #7
It works by taking in optional arguments into the input function (a bool for whether or not a headset is emulated and then position and orientation). If none of the arguments are provided, the behavior is the same as before. When only the bool is present, it captures data from the emulated headset directly. The last case is there for when the render pass has a different transform than the headset (as is the case in the FPS example).
I also removed some duplicate data and fixed what I presume was a declaration of a table.