Using the same quick test (18.000 blue particles from real flow sim), I noticed that when stoke generates new particles (2.000.000 orange) from real flow sim, it has a pre defined radius to copy particles around, correct? Can we somehow change this radius scale? That would be PERFECT!
I’ve also noticed that using default value of 1.0 in the velocity scale, give’s us around 80% faster particles. So, I wonder if this is something related with real flow settings or with stoke. Here are the two animations with 1.0 scale and .2 so you can compare.
I am very confused. When Stoke creates new particles from existing particles, it is supposed to use the Jitter Radius value, and the default for Jitter Radius is 0.0. So how did you get the distribution you are showing in the screenshot, and why do you believe another Radius is needed? I am sure there is some misunderstanding on my side
When I drive particles with my RealFlow BIN file sequence, a Velocity Scale of 1.0 works perfectly. So a few questions about this too:
*Are you using BIN files directly, or are you using PRT files saved by RealFlow?
*Is the PRT Loader with the RealFlow data scaled (it should not make any difference, but just checking)
*When you display the Velocities in the PRT Loader and move from one frame to another, does it look like the velocities are pointing at the positions of the particles on the next frame, or 5x farther (in other words, are the velocities displayed with an unexpectedly long magnitude)? Can you post a screenshot or MOV of what the RealFlow PRT Loader’s velocities look like?
*Can you send me your MAX file and a few of the RealFlow files to look at?
Sorry for the mess… so, first of all, jittering was what i was looking for O_o - so, the solution already existed in front of me and I didn’t see it! Sorry for that.
About the second part:
1 - I’m using bin files loaded from krakatoaprtloader
2 - It’s not scaled
3 - The velocities are pointing to the same position and if I calculate with scale 1.0 they look similar in terms of magnitude. But when you preview them, they are going much faster.
4 - I’ll send you max file and real flow file so you can take a look.
Cheers
PS: Do you think it can be related somehow on changing geometry scale in realflow (.1) to fit 3dsmax scale?
Turns out the Velocities in the BIN file are indeed 10 times larger than they should be.
If you zoom in at any of the dashes and advance one frame, the particle actually moves 1/10th of the line’s length, which is a clear sign BINs scale only their positions, but not the velocities. Not sure if it is a bug or As Designed on RealFlow’s part, but it is something to keep in mind.
You can either drop a Magma modifier on the PRT Loader and set the flow to InputChannel:Velocity ->Divide (10.0) -> Output:Velocity (which will now display the correct Velocities as lines, and the next particle position will always be at the end of the previous line drawn), or enter 0.1 in the Stoke Velocity Scale as you were almost doing already…
I usually simulate at Geometry Scale 1.0 in RealFlow (it is in Meters by default AFAIK), and then I scale the PRT Loader to match the Max scene scale as needed (for example, the scale factor for Meters to Inches is 39.3701, or 3937.01 % in the Scale Type-in dialog). Same with Naiad PRT files. 3937.01 is engraved in my head.
))
