Skip to content

Performance

Jared Taylor edited this page Mar 17, 2025 · 7 revisions

Important

ProcHitReact has aggressive optimization out of the box and will disable it's own tick when not required

ProcHitReact implements TRACE_CPUPROFILER_EVENT_SCOPE() where appropriate, so you will get meaningful traces to observe in Unreal Insights

This is the video showing what was traced:

UnrealEditor-Win64-DebugGame_2025-03-14_12-01-59.mp4

Roughly ~60 hit reacts applied simultaneously, all of which modify the blend weights of each bone below the simulated bone ( spine_03 )

The result is ~200μs on the heaviest frames

UnrealInsights_2025-03-14_12-03-04

Note

Typical general use of HitReact is ~150-300μs per tick
However, this cost is entirely removed when no HitReact is currently active

Warning

These tests were performed in editor and not in packaged builds
Packaged builds should incur notably cheaper frame costs

Clone this wiki locally