Description

Consider a Niagara Function Script containing a Static Switch node with the "Expose as Pin" option disabled for its selector variable.

Now consider another Niagara Function Script or Module Script that calls into that internal function. The "Selected Details" panel of the function call node will show a "Propagated Static Switch Values" category, which allows those internal static switches to be propagated or not (to callers of the external function or to usages of the external module by an emitter), and to change the name of their selector variable when propagating it.

Any changes made to settings on that "Propagated Static Switch Values" category do not cause the "Apply" button to become enabled on the script editor, even though clicking it would be necessary to make the effect of those changes visible elsewhere.

Repros in mainline CL 41413293
No public tracker found
Not regression (repros in 5.0 onwards)

Steps to Reproduce

1. Create and edit a new Niagara Function "NF_Internal" (Content Browser – FX – Script – Niagara Function Script)
1.1. On the "Script Details" tab, change "Library Visibility" to "Exposed"
1.2. Change the input name to "A" and add a new input "B"
1.3. Add a "Static Switch" node
1.3.1. Connect its output pin to the function output
1.3.2. Connect each input pin to one of the two function inputs
1.3.3. On the "Selected Details" tab, change the "Input parameter name" to "InternalParameter"
1.4. Compile, apply, save

2. Create and edit a new Niagara Function "NF_External"
2.1. On the "Script Details" tab, change "Library Visibility" to "Exposed"
2.2. Add a call to "NF Internal" between the input and output.
2.2.1. Connect its input pins to two function inputs "A" and "B", and its output to the function output
2.2.2. Connect its output pin to the function output
2.3. Compile, apply, save
2.4. On the "Selected Details" tab for the "NF Internal" call node, under category "Propagated Static Switch Values":
2.4.1. Check/uncheck the flag for "InternalParameter" --> The "Apply" button does not become enabled
2.4.2. Change the "Override name" --> The "Apply" button does not become enabled

3. Create and edit a new Niagara Function Script
3.1. Add a call to "NF External" --> The boolean input is on the last state when "Apply" was clicked for "NF_External"

4. Create and edit a new Niagara Module Script
4.1. Add a call to "NF External" --> The boolean input is on the last state when "Apply" was clicked for "NF_External"

5. Repeat step 2 but with a Niagara Module Script. The same bad behavior of the "Apply" button can be observed.

Have Comments or More Details?

There's no existing public thread on this issue, so head over to Questions & Answers just mention UE-267341 in the post.

0
Login to Vote

Backlogged
ComponentUE - Niagara
Affects Versions5.5.4
CreatedApr 7, 2025
UpdatedOct 14, 2025
View Jira Issue