The MotionController Manager manages all registered motion controllers and loads the right one when needed.
When this repository is complete: https://github.com/immersive-web/webxr-input-profiles/tree/master/packages/assets it should be replaced with auto-loaded controllers.
When using a model try to stay as generic as possible. Eventually there will be no need in any of the controller classes
Register the default fallbacks. This function is called automatically when this file is imported.
Find a fallback profile if the profile was not found. There are a few predefined generic profiles.
the profile to which a fallback needs to be found
an array with corresponding fallback profiles
When acquiring a new xrInput object (usually by the WebXRInput class), match it with the correct profile. The order of search:
1) Iterate the profiles array of the xr input and try finding a corresponding motion controller 2) (If not found) search in the gamepad id and try using it (legacy versions only) 3) search for registered fallbacks (should be redundant, nonetheless it makes sense to check) 4) return the generic trigger controller if none were found
the xrInput to which a new controller is initialized
the scene to which the model will be added
force a certain profile for this controller
the motion controller class for this profile id or the generic standard class if none was found
Register a new controller based on its profile. This function will be called by the controller classes themselves.
If you are missing a profile, make sure it is imported in your source, otherwise it will not register.
the profile type to register
the function to be called when loading this profile
Register a fallback to a specific profile.
the profileId that will receive the fallbacks
A list of fallback profiles
Generated using TypeDoc