Tracer Settings
Last updated
Last updated
This section will explain purpose of each setting found under Mnh Tracer with exception of Trace Source, which is explained in detail in Trace Sources page.
WARNING -> Tracers system is replaced by Tracer Configs system and is kept only for easy transitions for old customers. API is exactly the same as Tracers system but underlying framework is very different. Please make sure to use Tracer Configs as Tracers property is no longer functional
Used for identification of the Tracer, each Tracer may only have one tag associated with it. Avoid assigning identical tags to tracers within the same actor, as only the first tracer will operate in such cases.
These perfectly match traditional Trace parameters found in Unreal Engine. For which you can refer to the official documentation.
https://docs.unrealengine.com/5.3/en-US/traces-in-unreal-engine---overview/
Default behavior, labeled "Match Game Tick," executes hit trace operations at every game tick. While effective, this approach can be excessive for certain games, prompting the need for optimization. The system offers two alternative options to streamline the number of trace operations performed.
In Fixed Rate Tick, the objective is to sustain a consistent tick count. For instance, if configured at 30 ticks but the game is running at 60 fps, it will intelligently skip one tick every two frames. Conversely, if the game operates at 15 fps, substep interpolation is applied to emulate 30fps-like hit traces. This adaptive mechanism ensures stability across varying frame rates.
Tick by Distance Traveled initiates hit traces based on the distance covered by the trace source. For example, if configured at 50 and the Trace Source moves by 10 units each tick, it will conduct a hit trace once every 5 ticks. Conversely, if set at 50 but the Trace Source moves by 100 units every tick, the system applies substep interpolation to ensure accurate hit traces in the given conditions.
Filter Type: Controls the behaviour of Hit filtering system. The "FilterSameActorAcrossAllTracers" option prevents any Tracer from hitting the actor if any Tracer has previously registered a hit. In contrast, "FilterSameActorPerTracer" filters hits only for the same Tracer, enabling other Tracers to register hits on the actor. The "None" option disables the hit filtering system, allowing all traces to register hits without any filtering.
In the background, when an Actor passes the filter check, it gets stored in the "Hit Cache." The Hit Cache serves as the system's record of previously hit Actors. If manual intervention is needed to clear the Hit Cache, the "Reset Hit Cache" function on the Mnh Tracer Component can be invoked. This function allows for the deliberate clearing of the stored hit information.
