"Cloners and Effectors" plugin warning messages on startup

Development Cinematics & Media
, ,
1

Hi

We noticed some niagara startup message log issues in 58. Low prio as I’m not sure what (if any) consequences this has, and we can manually fix these engine assets ourselves. But it would be great if they were fixed at source so we can keep output log issues to minimum.

Kind regards

Luke

[Attachment Removed]

2

Steps to Reproduce

  1. Enable “Cloners and Effectors” plugin in 5.8
  2. Restart and open the output log
  3. Observe lots of niagara issues are printed (log attatched)
  4. Open `/ClonerEffector/Emitters/NE_ClonerBase`
  5. Observe that the node has “unmet dependencies” errors
    [Attachment Removed]
3

Hey there! After discussing this with the engineers it sounds like the bug was that Niagara wasn’t flagging that dependency. CalculateAccurateVelocity specifies SolveForcesAndVelocities as a same script dependency (and, in fact, always has), so even though there’s a SolveForcesAndVelocities in the ParticleUpdate script, there should (according to the engine) also be one in the Solve Particle Collisions sim stage. Whether or not that’s actually the case is still TBD. Since that CalculateAccurateVelocity is set to “Calculate Accurate Velocity On First Frame”, it’s always calculating that based off the particle’s current and previous position, and NM_ClonerSolveParticlePosition updates the particle’s position as well, my gut says you can dismiss the issue because you know what you’re doing and then save the asset. I’m not sure how persistent that dismissal is, though, so you might try throwing another SolveForcesAndVelocities in there, and if you notice any odd behavior please report it ASAP.

[Attachment Removed]

4

Thanks Matt! I’ll let you know if we notice something bad happens as a result

[Attachment Removed]