Unreal Engine Issues

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 ...

NiagaraEmitter is saved with the different asset name when renaming with speceficed name

Renaming a NiagaraEmitter to a specific asset name changes it to an unspecified asset name. This happens only with NiagaraEmitter, not with other assets.  ...

ParticlePosition doesn't use Previous values

FHLSLMaterialTranslator::ParticlePosition does not return Previous information when request which can result in bad motion vector calculation. ...

Texture Sample DI does not work on Niagara Parameter Collections

Texture sample DIs no longer work when used with Niagara Parameter Collections. This seems to affect Volume Texture DIs based on customer reports, but I have not confirmed this.  ...

HeterogeneousVolumeComp doesn't render properly using DynamicMaterialInstance created in Construction Script

Niagara persistent debug draw bug

It is not possible to set the RotationNormalizedAngle to a value different from those you get from an input map. For example, you cannot set it to a value from a make float once created inside the m ...

Default Wireframe View within the Niagara Preview Window is Difficult to Visualize

The environment geo is getting in the way and the particle's wireframe outline is the same color as the environment. A current workaround it going to the Preview Scene Settings and turning off the e ...

Attribute Reader + Torus Shape Location module cause NaNs in CPU Niagara systems

It appears using the attribute reader with the shape location module set to torus will cause NaNs. The log mentions Sphere Radius among them, which should not be used with the torus mode. ...

Inaccurate motion vectors when using different position binding in renderer

Even though the particles are not moving, and the velocity is zero, the output motion vectors are non-zero. This seems to only happen if using two sources of particle positions.  ...

Getting Emitter.NumParticles on Niagara's GPU compute sim returns 0

This problem looks like the following parameters are not defined correctly. The correct parameter is Engine_Emitter_NumParticles. Engine_Emitter_NumParticles and PREV_Engine_Emitter_NumParticles .\ ...