I have problems with a cascade of simulators. Basically, a simulator of liquid filling another simulator.
I would use such system for complex liquid path, allowing simulating a first part, then adjusting a second or third part without having to re simulate entire path. Looking at wine bottle scene I’ve set a simple test scene like that, but I always end up with a very visible transition between the twos.
Here is the simple scene, if anyone can provide some advices ?
Ph_SimCascade.zip (45 KB)
ok, we will look into your scene, but did you see the wine tutorial?
Yes my simple test is directly inspired from this tutorial and scene
Here is the same scene but with much better transition between both simulators:
A few things might help in order to get a smooth blending.
1.Smaller Cell Size
2.Higher SPF value
3.Rotate the bottom simulator to match the fluid-angle from the first one.
4.Tweak isosurface-level
http://ftp.chaosgroup.com/support/scenes/Ph\_SimCascadeTS\_1.max
http://ftp.chaosgroup.com/support/scenes/Ph\_SimCascadeTS\_2.max
Please note that the top-simulator should have Solid Object activated during its simulation and the same option(top-simulator) should be OFF when simulating the bottom one.
i should say that the waves visible on the surface of the lower simulator are caused by the low spf value, the liquid becomes faster with the time and this leads to them. you will have them even if the simulation is in a single box, it’s not related to the cascade connection.
but all these details are just for polishing, in your case the most important fix is apparently the solid mode option of the first simulator. as svetlozar said, it must be off when you proceed the second simulator, otherwise it works as solid object and releases the liquid on the surface, instead in the entire covered volume. beside this, the solid mode gives initial speed of the liquid toward the normals, that leads to changes in the stream behavior, it looks inflated.
it’s very important to understand that the cascade connection is NOT a special phoenix feature, it’s just an user level technique, that we have “discovered” by chance, that’s why it requires certain sequence of actions instead just simple to point the cascade partner and push start. in the future we will make it like this, but for now you have to follow all these weird steps.
Wow, many thanks both, for nice explanations. Will try all this when back at work.