Navigation
BlueprintAPI > BlueprintAPI/Utilities > BlueprintAPI/Utilities/Struct
Adds a node that breaks a 'Pose Search Interaction Availability' into its member fields
Inputs
| Type | Name | Description |
|---|---|---|
| struct | Pose Search Interaction Availability |
Outputs
| Type | Name | Description |
|---|---|---|
| object | Database | Database describing the interaction. It'll contains multi character UMultiAnimAsset and a schema with multiple skeletons with associated roles |
| name | Tag | in case this availability Database is valid (not null), Tag (if IsTagValid()) is used to flag the Database with a specific name. Different availabilities can share the same Tag.in case this availability Database is NOT valid, we use the valid Tag to figure out all the possible databases that can be assigned to this availability from all the published availabilities.The reason behind Tag is, for example, to be able to have NPCs been able to interact with a main character (MC), without the MC having a direct dependency to the database usedfor the interaction allowing those NPCs to be contextually loaded/unloaded, streamed in/out, with the obvious advantages for the the memory managment of the "payload" database.Another reason for Tag, is to facilitate the setup of interactions, where the MC have to publish only one availability with its own assigned Role (in RolesFilter)automatically contextually resolved in multiple different types of possible databases: it could be MC-NPC, MC-Vehicle, MC-Whatever |
| name | Roles Filter | roles the character is willing to take to partecipate in this interaction. If empty ANY of the Database roles can be taken |
| real | Broad Phase Radius | the associated character to this FPoseSearchInteractionAvailability will partecipate in an interaction only if all the necessary roles gest assigned to character within BroadPhaseRadius centimeters |
| real | Broad Phase Radius Increment On Interaction | during interaction the BroadPhaseRadius will be incremented by BroadPhaseRadiusIncrementOnInteraction to creategeometrical histeresys, where it's harder for actors to get into interaction rather than staying in interaction |
| boolean | Disable Collisions | if true, the system will disable collsions between interacting characters |
| integer | Tick Priority | the Actor with the higher TickPriority of any Availability request will be elected as the MainActor of the interaction island (containing all the actors that could interact with each other)the main Actor will tick first and all the other interacting actors will tick after in a concurrently from each other. TickPriority is useful if your setup is already enforcing tick dependencybetween actors, and the motion matching interaction system needs to play nicely with them. |