Cascade > Shared Seeded module not sharing correct seed

tested in 4.11 to 4.15

The video explains it rather well. You would expect (in this case) that if you share seeds of innitial rotation, that each seed has the same value between emitters. sadly this is not the case, and the bane of my existence at this moment :p

Hey Luos,

What you have suggested should be possible with the engine currently.

Have you tried what I did in this video? It isn’t perfectly random but the player shouldn’t know the difference and the two particle systems should stay together.

An alternative is to set the particle rotation using a particle param and blueprints. If I am missing something or you are still having issues let me know!

Cheers,

Ed

Hey Ed! for that, will try it out after dinner.

Hey Ed, for some reason I am not getting the same result in 4.11 all the way to 4.15 latest preview.

Any idea what I might be doing wrong, or whats going on?

You aren’t doing anything wrong. The Seed workaround is more like a sequence of rotations that will always execute in that sequence (in the video I am not restarting the level). If you want a particle system that is random every time it spawns you will have to do particle param workflow listed below.

  • Use Init Mesh Rotation with a vector param (I named it Rot) and share, (see screen)

  • Make a blueprint and set the rotation every time a particle is spawned. In this case I could use a simple delay since I’m only spawning 1 particle per second. I have it in begin play to the system gets initialized with a random value. Keep in mind this is just a quick proof of concept you will need to adjust this workflow to meed your needs.

  • Using this method I got both shared emitters to have the same rotation and it was random every time it spawned. (this is what you are looking for probably but it is a bit more annoying to work with).

Sadly you can’t preview the particle system’s randomness in cascade and have to play in editor to test. I know this workaround isn’t ideal but it gets the job done.

Hey Ed, for the explanation, sadly due to the nature of this (marketplace) package I dont want to use any blueprints.

Nonetheless I will bookmark this page if I ever need a setup like this personally :slight_smile:
I guess for now I’ll just merge the meshes & materials and use a few masking techniques.