You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Interactables (Hinge, Slider, Joystick) need 3D Gizmos to assist in alignment and configuration; however the design of the interactables currently hinders this.
The current interactable nodes move within the confines/transform of their parent "Origin" Node3D; and so visualizing the extents of motion want to be with regards to that "Origin" Node3D; however the 3D Gizmos mechanism attaches visualizations and aids to the target node.
As such a secondary set of scripts HingeOrigin, SliderOrigin, JoystickOrigin would be needed to define the extents, and the 3D Gizmos would be attached to these origin nodes.
The text was updated successfully, but these errors were encountered:
This PR resolves request GodotVR#584 by adding gizmos to align interactable hinges, sliders, and joysticks. This does cause minor breakage in that:
- New origin nodes have been introduced where the ranges are visualized
- Testing showed Y-Axis inversion on the slider and joystick
This PR resolves request GodotVR#584 by adding gizmos to align interactable hinges, sliders, and joysticks. This does cause minor breakage in that:
- New origin nodes have been introduced where the ranges are visualized
- Testing showed Y-Axis inversion on the slider and joystick
Malcolmnixon
added a commit
to Malcolmnixon/godot-xr-tools
that referenced
this issue
Dec 11, 2023
This PR resolves request GodotVR#584 by adding gizmos to align interactable hinges, sliders, and joysticks. This does cause minor breakage in that:
- New origin nodes have been introduced where the ranges are visualized
- Testing showed Y-Axis inversion on the slider and joystick
The Interactables (Hinge, Slider, Joystick) need 3D Gizmos to assist in alignment and configuration; however the design of the interactables currently hinders this.
The current interactable nodes move within the confines/transform of their parent "Origin" Node3D; and so visualizing the extents of motion want to be with regards to that "Origin" Node3D; however the 3D Gizmos mechanism attaches visualizations and aids to the target node.
As such a secondary set of scripts HingeOrigin, SliderOrigin, JoystickOrigin would be needed to define the extents, and the 3D Gizmos would be attached to these origin nodes.
The text was updated successfully, but these errors were encountered: