Unreal Engine Issues

TakeRecorder cannot record Auto Activate and Destroy of Niagara effect

When Niagara FX of a recording actor is spawned during taking a record, that FX behavior must be recorded and able to be playbacked. However, Niagara Component Auto Activation by BP node is not reco ...

Niagara using a Volume and Mesh renderer with a shared base material does not renderer correctly

Using a shared base material with both a Volume and Mesh renderer causes the emitter to render as a glowing box at the scale of the bounding box. ...

When an active Niagara Component is moved and reset+reactivated in the same frame, "Interpolated Spawning" causes "Spawn Burst Instantaneous" to spawn particles in the previous frame's outdated location

Consider a Niagara System with an Emitter in "Global Space" that has "Interpolated Spawning" active and a "Spawn Burst Instantaneous" module with a "Spawn Time" of 0.0 (for example, the built-in Con ...

Certain Niagara particles can disappear after switching to the debug cam

GPU particles disabled on Quest

GPU particles were disabled on Quest 1 due to a compute issue. We need to validate / fix issues for Quest 2 / Quest 3. Reported in [Link Removed] ...

Having two Play Persistent Audio modules in Niagara will only play the first sound

Only one Play Persistent Audio module will work at a time in a Niagara emitter. ...

Opening a Niagara asset that references a disabled plugin (Chaos Niagara) can crash the editor

Opening a module with references to a disabled plugin can crash the editor.  ...

Fixing Issue in Niagara stack across particle and system stages crashes the editor.

The Update Persistent Audio module has a dependency on a Play Persistent Audio module. When there are two modules in different overview nodes, the automatic fix up can put the Play Persistent Audio ...

View Distance sorting of Niagara sprites is incorrect when far from the origin

This problem seems to occur on both CPU and GPU Sims. ...

Arithmetic assignment operators (e.g. +=, *=) in Niagara inputs are applied twice .

Arithmetic assignment operators seem to be applied twice when committed in the Niagara stack.  This occurs when entering *= 2.0 for example into a float input. This may be the result of the SNiagar ...