Unreal Engine Issues

When editing a Niagara module an error can occur if using non-module functions, even with a correctly set usage bitmask

When editing the module the call to FHlslNiagaraTranslator::HandleDataInterfaceCall has the usage "Module", so it treads the module as if that was its stack context, even though the module's usage b ...

Niagara compile error : Select Position from Array

A similar node, Select Vector From Array, does not have this problem. The difference between the two seems to be whether or not Required is checked in the input node's exposure options. ...

Niagara Fluid is not displayed in the TopView of the Niagara Editor

Normal Particles are displayed. ...

[Crashreport] UnrealEditor-Niagara!FNiagaraSubmixListener::UnregisterFromSubmix() [NiagaraDataInterfaceAudio.cpp:85]

Generated from CrashReporter Crash only occurs when packaged. ...

Exposed Niagara User Parameter Enums are displayed as Integers

(Note: all enums seem to fail when exposed as a user parameter and changing the exposed int does not impact the result of the simulation) Add a rigid mesh collision query di to a scratch module pe ...

Crash when editing category name in the emitter summary

Niagara Geometry Cache Renderer does not update index binding in looping emitter

Some Niagara Fluid systems are not visible in a packaged project

Previously packaging caused a crash with this system. This was fixed, but now the system is no longer visible when packaged. ...

NiagaraSystem is compiled every time when first loaded in the editor

If you are using a large amount of Niagara, you will experience excessive load times in PIE even if nothing is changed. The following code change seems to be effective as an interim response. void ...

A niagara emitter with an empty renderer module does not return a position in the package