¶ Character Component — Runtime Motion Handler
The BFSFoleySystemComponent is the runtime system that connects your characters to the BFS Foley System.
It handles movement detection, bone tracing, footstep classification, and sound triggering — all fully automatic once added to your Blueprint.
¶ How to Use
Just add the BFSFoleySystemComponent to any Character Blueprint where you want footsteps or cloth sounds.
🎮 It is compatible with any ACharacter-derived Blueprint and supports multiple characters with unique BoneTraces and Wardrobe configs.
⚠️ For non ACharacter-derived, call theSetSkeletalMeshComponentfunction exposed to blueprints.
¶ Outfit System
The only editable variable is the Default Outfit — a Gameplay Tag such as:
Outfit.Sneakers
Outfit.Stealth
Outfit.Heavy
This tag defines which Wardrobe config to use.
You can override or retrieve the outfit at runtime:
Blueprint Functions: SetOutfit and GetOutfit
This allows you to change clothing mid-game, and automatically swap sounds.
¶ Speed Detection
The component tracks two types of motion:
Walking Speed— horizontal velocityFalling Speed— vertical movement
Both are automatically measured each tick and used to assign appropriate Speed Categories.
You can override either value manually:
Blueprint Functions: OverrideWalkingSpeed and OverrideFallingSpeed
This is useful for animation-driven movement or custom logic.
¶ Foot & Limb Tracing
The component uses the BoneTraces asset to determine:
- Which foot is touching the ground (heel/toe)
- Which limbs are moving enough to trigger cloth sounds
It samples the bone positions and rotations each tick to determine:
- Trace contact (ground hit)
- Angular speed (motion amplitude)
All this is done internally — you don’t need to call any manual updates.
¶ Real-Time Sound Triggering
Once motion is detected:
- Footsteps are matched against the Data Table
- Matching MetaSound is triggered using the Meta Library
- Cloth sounds (if active) are looped and modulated by angular speed
¶ Summary
- Add the
BFSFoleySystemComponentto any character - Set a default
Outfittag - The rest happens automatically using the data system
- Optional overrides allow fine-tuning for gameplay scenarios
¶ Footstep Fallback Logic
If the system cannot find a footstep row that matches a given speed tag (e.g., Walk, Run), it will fallback to a row of the same type and metadata, but with no SpeedCategory set.
✅ You can use this as a default catch-all row when no specific velocity tag is matched.
This allows you to define simplified or fallback entries for edge cases or generic footsteps.