Support for Device gyro instead of controller gyro via CoreMotion #664
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
…Motion. As this requires CMAcceleration and CMRotation instead of GCAcceleration and GCRotation, this makes the setMotionEventState function a little bit longer. Also, this adds a UI Switch to change the new motionMode variable for player 0/1: *Auto uses device motion as a fallback if controller motion is not available *Device Motion always uses device motion sensors (this possibillity is needed, as some controller grips send useless dummy motion data to the iPhone. In this case, the user can manually select to use the device's motion data instead.) *Controller Motion always uses the controller's motion data. If the controller doesn't offer motion data, the device is *not* used as a fallback. (cherry picked from commit d0e8866447bd52c244e1f3b8ffd8e4d8e1471aeb) (cherry picked from commit e1de4b8)
Default behaviour: use controller motion if available, use phone motion if controller motion not available
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.
This PR lets the user choose if they want to use Controller Motion or Device Motion (so you can play with motion without controller/with a non-motion-enabled controller)
As this requires CMAcceleration and CMRotation instead of GCAcceleration and GCRotation, this makes the setMotionEventState function a little bit longer.
Also, this adds a UI Switch to change the new motionMode variable for player 0/1: