Works in Unreal Engine 5.0 to 5.8. Updated November 2026.
Quick answer: the effect is either not cooked or turned off by scalability.
- In the editor, set Settings > Engine Scalability Settings to the quality your packaged game uses (often lower than Epic) and check the effect still shows.
- If it disappears, open each emitter’s Emitter Properties and tick all quality levels under Platforms.
- If the effect is spawned by a path or name string, add its folder to Project Settings > Packaging > Additional Asset Directories to Cook.
Cause 1: Scalability turns the emitter off
Niagara emitters can be limited to certain Effects Quality levels. The editor usually runs at Epic quality, while a packaged game may pick a lower level on its first run, or the player may lower it.
- Open the Niagara System and select an emitter.
- In Emitter Properties, find Platforms (or Scalability).
- Make sure the quality levels you want (Low, Medium, High, Epic, Cinematic) are enabled.
Also check the system’s Effect Type asset, if it has one. Its scalability settings can cull effects by distance or by the number already playing.
Cause 2: The asset isn’t cooked
The cooker packages assets your levels reference. An effect loaded only by a soft reference or a text path, for example a name you build at runtime, isn’t referenced, so it may be left out.
- Reference the system directly in a Blueprint variable or component, or
- Add its folder to Additional Asset Directories to Cook in Project Settings > Packaging.
The packaged game’s log then shows no Failed to load warnings for the effect. The log is in <PackagedFolder>\Windows\<ProjectName>\Saved\Logs\ for Development builds.
Cause 3: Bounds cull the effect
Unreal hides objects when their bounds are off screen. GPU emitters rely on fixed bounds, and if those are smaller than the effect, it vanishes when you look slightly away, or never shows at all.
- Open the system and use Bounds > Set Fixed Bounds in the toolbar while the preview plays, or
- Set Fixed Bounds by hand in System Properties (and on GPU emitters).
This happens in the editor too, but different camera angles in the game make it more obvious.
Cause 4: It never activates
| Check | Where |
|---|---|
| Auto Activate is on | The Niagara component’s Activation settings |
| Spawn node gets a valid location | Spawn System at Location with a real location, not 0,0,0 |
| The spawning actor exists in the packaged level | Actors placed in a sub-level that isn’t loaded never spawn anything |
| Spawn Rate isn’t driven by a parameter that’s 0 | User parameters on the component |
Test with Play > Standalone Game first. It’s closer to the packaged game, and quicker than packaging each time.
FAQ
Only GPU effects are missing on some PCs. Older graphics cards or drivers may not support every GPU feature. Try a CPU emitter, or update drivers.
Effects are missing only on mobile. Check the Platforms settings for mobile, and that the emitter uses features mobile supports. GPU emitters need a capable device.
Does Fix Up Redirectors help? If you moved the effect’s folder recently, yes. Right-click Content and choose Fix Up Redirectors.