-
Notifications
You must be signed in to change notification settings - Fork 5
Allow Digital and SingleAxis input actions for teleport #217
Conversation
…e/721-teleport-input-action
XRTK.SDK/Packages/com.xrtk.sdk/Runtime/Features/UX/Scripts/Pointers/TeleportPointer.cs
Show resolved
Hide resolved
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
First issue. |
Not an issue but to be expected. How is it supposed to work with only a single axis / digital input? |
else | ||
{ | ||
IsTeleportRequestActive = true; | ||
BaseCursor?.SetVisibility(false); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's do a traditional null check on the unity engine object types
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed. I'll change that in another PR as this code was not introduced in this PR and I don't want to trigger another build on this one. Need this to release to continue testing.
Ok, as per discussion, PR is fine as is. Turning is not supported with Digital or Single Axis. This will be addressed in 0.3 with a new Locomotion Feature |
/azp run |
Azure Pipelines successfully started running 1 pipeline(s). |
* Update validator default profile * Get TeleportAction from system in TeleportPointer * Prepare TeleportPointer handling for Digital/SingleAxis * Fix TeleportPointer inspector still reasing obsolete fields * Implement digital teleport action * Remove logs * Implement single axis teleport * Use > instead of >= * FInalize and clean up * Assign default teleport action in SDK * Bump core dependency
XRTK - Mixed Reality Toolkit Pull Request
Overview
Companion PR to XRTK/com.xrtk.core#729