QORPOHow to test Niagara culling without losing combat cues
Use Niagara Effect Types to group effects with similar scalability needs, then test what actually disappears when culling kicks in. A distant ambient effect and a warning tied to an enemy attack can need different rules. Make one change at a time and compare both performance and the player's ability to read the encounter in a packaged build.
Start with the signal the player needs
Walk an encounter before tuning any settings. Mark which effects communicate a timing window, damage area or impact and which supply atmosphere. Decide what the player must be able to see at the point where they can act. The lower quality setting can simplify an effect if the remaining cue still does its job.
Imagine a model arena with floating dust, an attack wind-up and a burst when the blow lands. Reducing dust can be easy to evaluate because it belongs to the environment. Removing the wind-up ring has a larger consequence if players rely on it to know when to leave the area. A shorter trail or simpler material could save work and preserve the timing, depending on where the measured cost comes from.
Put the policy where it can be reviewed
Epic's Niagara scalability documentation describes reusable Effect Types and settings at several levels of an effect. Start by checking the assigned Effect Type and any overrides on the system. A local override can explain why two effects that appear to belong to the same category behave differently in the same scene.
Give the reviewer a small scope. For example, adjust the distance rule for ambient dust, leave the wind-up alone and run a near view, a distance boundary and a busy view. Record the scalability tier, camera path and gameplay conditions. The QORPO guide to effective Unreal console variable values covers how to check that the build is using the expected settings.
Check the view near the boundary
Start outside the chosen distance and move into the encounter. Then walk out as the effect is running. Pay attention to what happens during the transition. A clean reduction can be less distracting than an effect popping in and out every time the camera moves near a threshold.
If the effect disappears while it ought to be visible, review its bounds and visibility rules as well as distance. Epic's Effect Type budgeting guide describes limits such as instance counts and distance. Record which rule you changed before interpreting the result. Multiple limits can be relevant in the same encounter.
Make the busy case reproducible
An empty arena is useful for establishing how one effect behaves. Add a consistent encounter with several effects active to see how the policy works when the camera is under pressure. Repeat the same path, quality settings and action timing. Capture frame time and, where possible, Niagara diagnostics for each pass. A screenshot of the quality setting plus a short clip of the wind-up can help someone else repeat the comparison.
Check the cue across at least one view where the player can act on it. A warning visible from a spectator angle can be lost from the real combat camera. If a change improves the frame capture but obscures the wind-up in that camera, preserve the readable cue and use the capture to decide which part of the effect to simplify next. See how QORPO tests render resolution changes for another example of keeping comparison conditions consistent.
What should go in the review note?
Record the hardware, packaged build, effect or group, tier, route and single setting change. Give the frame-time result with its conditions. Then report what the player could see, especially at the distance boundary and in the busy case. If you changed fixed bounds, capture a view where the effect reaches its full intended extent so a reviewer can spot a clipped result.
Avoid deriving a universal culling distance from one arena. Range depends on the effect, camera and gameplay use. A useful approval says exactly which class of effect changed and what was observed on the test route. The QORPO development blog has more workflows for connecting a performance capture to a visible change in play.