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
There are numerous almost-identical routines to find player resource nodes:
Find the ARVROrigin from a node under the player
Find the ARVRCamera from a node under the player
Find the PlayerBody from a node under the player
MovementProvider.gd has some of these functions, but they only work if the caller is a MovementProvider. Instead it would be better if these find routines were available to any node under the player - for example by making them static functions of a helper script.
The text was updated successfully, but these errors were encountered:
It would indeed be nice to have a number of these functions in an autoload script, my main worry here is that this requires a setup action and I want as much as possible to remain automatic.
I added a pull request showing an example of what I'm thinking of. It lets a node located anywhere under the ARVROrigin do:
var origin := ARVRHelpers.get_arvr_origin(self)
var camera := ARVRHelpers.get_arvr_camera(self)
var left_controller := ARVRHelpers.get_left_controller(self)
var right_controller := ARVRHelpers.get_right_controller(self)
Yeah 100% agree with what it does, just thinking of how we can have the helper node there or auto loaded so the user of the plugin doesn't need to be instructed to do so before starting to use the plugin.
There are numerous almost-identical routines to find player resource nodes:
MovementProvider.gd has some of these functions, but they only work if the caller is a MovementProvider. Instead it would be better if these find routines were available to any node under the player - for example by making them static functions of a helper script.
The text was updated successfully, but these errors were encountered: