No i first thought we should use Krakatoa and Fume FX.
And try todo get it it done in in max and XSI.
But i wanted todo use mainly XSI. When i started the research.
How we could do the fluid Stuff, there was no bien todo do it in.
Xsi, y played a Little bit with the Maya fluidos and remembered.
That i started todo code an importer for Maya fluid caches some.
Time ago.
After a bit of digging i had a Prototype in Python which was working, todo use the caches as flowfield, but in the second wek of research.
The nice emfluid was ported todo ice and we gave it a go.
Quite easy todo use and as a node in ice quite powerfull.
You could enhance the resolution of the simulation with simple.
Turbulence nodes, for example using the velocity as a multiplier.
For the turb or the turb size.
Rendering was an other thing, first we wanted todo stay away from.
Selfshadowing and do something in comp, but After i set up the first.
Shot with shadows, just for fun, it was not that problematic.
As i thought, everything on 64 bit because of the massive data amount.
Some shots with over 50 mío particles – Mental Ray was quite nice todo us.
It was a bit painfull, because we had todo tune the shader settings of every shot seperately, there was no bien todo use settings from other shots, the volume shader worked quite well but its hard todo tune.
We found one limit with the Mental volume thing – You could not.
Allocate more than 4 gig.
The other nice thing is – Youre not used todo produce such an large amount.
Of data with caché files. We had around 1 terra of caché files.
Only with the pointposition because of the file size, then we loaded it bak in ice and calculated the size, velocity etc on the flow.
Otherwise it would have killed our server.
3 months of hard work in the production submarine, but tim and me had.
A nice time.