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 ...
Renaming a NiagaraEmitter to a specific asset name changes it to an unspecified asset name. This happens only with NiagaraEmitter, not with other assets. ...
FHLSLMaterialTranslator::ParticlePosition does not return Previous information when request which can result in bad motion vector calculation. ...
Adding a module which has Required Dependencies (such as "Add Velocity") to event handler stage causes ensureMsg. > > In system /Game/NewNiagaraSystem.NewNiagaraSystem, module AddVelocity (NiagaraN ...
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. ...
Even after manually Deactivating a Niagara component, this Niagara component may be revived under certain conditions. This issue occurs when the following conditions are met before the Deactivated N ...
Error on some Niagara emitters using the WindForce module: LogNiagaraEditor: Error: Invalid input type found while attempting initialize new rapid iteration parameters. Function Node: /Game/FX/Expl ...
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 ...
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 ...