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

perform a find actors fn 

expose the tracechannel input as a module input

expose the input as a user variable 

notice that it's an enum at the user level within Niagara 

place the emitter in the world

go to the details panel 

notice that it's represented as an int there and not as an enum

It's unclear as to what number is associated with which options in that case and it could lead to bugs in the future

[Image Removed]

[Image Removed]

[Image Removed]

fyi [Link Removed]

Add an enum to user parameters in a Niagara system

See if its displayed properly as an enum with a combo box selector instead of an integer in both the user parameters tab & the details panel when placed in the level.