Difference between revisions of "Find Character Controller (LogiX node)"
Jump to navigation
Jump to search
(Marked this version for translation) |
|||
Line 18: | Line 18: | ||
** Failing this, it attempts to output the CharacterController associated with its active user's currently selected locomotion module. | ** Failing this, it attempts to output the CharacterController associated with its active user's currently selected locomotion module. | ||
+ | <!--T:6--> | ||
If the User in question here is using a Locomotion Module that lacks a CharacterController such as NoClip this node will output null. | If the User in question here is using a Locomotion Module that lacks a CharacterController such as NoClip this node will output null. | ||
+ | <!--T:7--> | ||
The Default output is ''null''. | The Default output is ''null''. | ||
Revision as of 05:17, 15 February 2022
Find Character Controller | ||
---|---|---|
Inputs | ||
User | Source | |
Outputs | ||
CharacterController | Character |
The Find Character Controller node attempts to find and output a CharacterController (Component) from either the input user or slot.
Usage
This node has two versions which work slightly differently but to the same effect:
- The User variant of this node outputs the CharacterController associated with the input user's currently selected locomotion module.
- The Slot variant of this node attempts to output the closest CharacterController component from the input slot or its parent slots.
- Failing this, it attempts to output the CharacterController associated with its active user's currently selected locomotion module.
If the User in question here is using a Locomotion Module that lacks a CharacterController such as NoClip this node will output null.
The Default output is null.