Custom Niagara Parameters are not highlited anymore when selected in the Parameters Tab

Development Rendering
, ,
1

Hello support!

I’m taking a chance here since I did not had any reply in this previous post on the other forum: Custom Niagara Parameters are not highlited anymore when selected in the Parameters Tab

Creating a custom Niagara Parameter and selecting it in the Parameters tab won’t highlight it anymore which makes it harder to find in which modules it’s currently referenced. Niagara Native parameters like System.ExecutionStateSource seems to be well working.

Is this something already fixed in the upcoming 5.6 editor by any chance?

Thanks!

2

Steps to Reproduce

  1. In Unreal Version: 5.5.3-39772772+++UE5+Release-5.5, I simply create a new Niagara System using the Fountain template.
  2. Then under the System Update, I create a simple Float parameter.
  3. I’ll assign this Parameters into the Scale Color of my Fountain emitter
  4. Under the Parameters tab, if I select the Parameter, it won’t be highlighted into the emitter
3

Bump. Thanks! :slight_smile:

4

Hello [mention removed]​,

I have tested this in UE 5.5.4 (launcher version) and I notice that the engine does highlight the parameter usage next to the module unlike your attached image.

Let me know if this information helps.

[Image Removed]

Best,

Francisco

5

Hello [mention removed]​ For some reasons, in Version: 5.5.4-40574608+++UE5+Release-5.5, with a blank project, I do not have the same behavior as you currently have. Is it possible that it could be a preference or that the issue is on and off depending on the version?

I made a video showing what is happening on my side and attached it to this post.

6

Hello [mention removed]​, you’re absolutely right.

I’ve re-tested the behavior in UE 5.5.4 (launcher and built from source at CL 40574608) and I can now reproduce the issue. Apologies for the confusion, I realized my earlier test and screenshot were from UE 5.3.

This appears to be a regression introduced in 5.5. However, I’ve also tested in UE 5.6 preview and a recent build from Main (P4 CL 42589677), and I can confirm that the issue is no longer present.

It’s safe to say this will be resolved with the official release of UE 5.6.

Let me know if this information works for you.

Best,

Francisco

7

A fix in 5.6 is perfect for me :ok_hand: . Thanks for the follow up on this. Have a great end of day.