You've already forked UnrealEngineUWP
mirror of
https://github.com/izzy2lost/UnrealEngineUWP.git
synced 2026-03-26 18:15:20 -07:00
1d8fb466f9
------------------- New "Object" parameter type for Niagara. These allow you to pass in Raw UObject pointers for use in data interfaces or renderers. Current use case is to pass in Skeletal Mesh references from the outside. This avoids having to create a whole new data interface when passing in external object references. Other use cases could be passing in; - material overrides - Static mesh references to override the mesh a renderer uses. - Basically any UObject a DI or renderer may use. These are weakly typed, meaning that they have to be UObjects but beyond that, they can be anything. So in theory you could pass in a Material to these Skeletal mesh references. It's on the using code to validate and act appropriately. This weak typing does allow a gread deal of flexibility though. E.g. you can now pass in a Skeletal Mesh Actor OR a SkeletalMeshComponent to Niagara via the same parameter and the DI will interpret it accordingly. The ability to pass in direct sub component refs is something cascade could never do. Deterministic Randoms for Data Interfaces ------------------------------------------- To support functional tests for the object parameters, this CL also includes deterministic randoms for DIs. Random seeds for deterministic randoms are now packaged up into a NiagaraRandomInfo that can be passed to DI functions. There is a helper class that will handle the parameter and let you generate randoms that are deterministic or not based on the passed NiagaraRandomInfo. Non deterministic is indicated using a special case value of 0xFFFFFFFF for Seed3. Misc ------------- Some utility additions to int vector class. Slight refactor of mesh helper for the skel mesh DI. Fixed issue with incorrect delta time on first tick of skel mesh DI. Work Needed ------------------------ UI customization for these parameters in the stack and the component override panel. As these are typeless probably the best thing here is to have the stack UI be an asset picker and the component UI be an actor picker? Is there such a thing as a combined asset/actor picker? IDK. Deterministic Randoms need to be utilized in other DIs/Functions. #rb Frank.Fella, Shaun.Kime #ROBOMERGE-OWNER: ben.marsh #ROBOMERGE-AUTHOR: simon.tovey #ROBOMERGE-SOURCE: CL 7288634 via CL 7301760 via CL 7302160 #ROBOMERGE-BOT: BUILD (Main -> Dev-Build) (v371-7306989) [CL 7357530 by simon tovey in Dev-Build branch]