Well, I guess I dont fully understand your fluid box implementation.. Usually (Mooootzooooid hehe) you define a area where the simulation take place.. But for PhysX it doesnt seem to matter how small or big the Fluid box is, it seems to simulate anyway?

Another thing.. Substeps only seem to impact CPU rendering.. When doing higher substep simulation on the GPU, the simulation takes longer time but its always looking the same (And the substep seems to correspond to a high CPU number, because its always very stable on the CPU).. So doing GPU substep 0, goes super fast, and looks super nice! Great project Mr. Core!

Ooh and another thing.. Is there anyway to define the collision distance for collision objects? My collision seems to happen quite far away from the actual polynormal...

>>Usually (Mooootzooooid hehe) you define a area where the simulation take place..
Here is different approach, like Lagoa - physx doesnt require any containers. Honestly saying, in GPU mode ( due to memory restrictions on videocards ) there is invisible container defined by Approximate Fluid BBox Length parameter , I cant say in which way it is centered because I cant see px sources but you could consider something like boxcenter = first emit position. There is relation ship between bbox length and sim speed, less length = higher speed, but once particle will reach border of box - it will be dropped ( looks as fall down through all objects in the scene )

>>Is there anyway to define the collision distance for collision objects?
Try to manually change these parameters inside of the central compound:
http://clip2net.com/s/1LFrP

Thanks a bunch for the explanation!! Im very very excited about your fluid simulation!

Thanks, but its not mine, its physx

Well, you know what I mean I wil play with this baby for two-three weeks now. And post test meanwhile

Uhm.. Im doing different water scenes. So I created one model, which each contains some objects and a point cloud. Now I get a error message trying to run more than one pointcloud ice simulation, which is fine. But usually hiding the "inactive" pointclouds is enough (or disable the ICEtree) to stop them running, but I still get a "not more than one instance is allowed" error message... Now I solved this by deleting the inactive models, run the one I want active once, and then hit undo and hide the other icesimulations... Would it be possible to fix, so just hiding the "unused" ones would be enough?

I love it by the way.. First test http://www.highendcams.se/Forsrannan.mov

cool, its for some 2.5d game?

No not a game, but some tests for a amusement park layout

Stumbled onto a problem with one test setup.. The particles seems to get stuck on the emitters when I use more than two emitters :/ I tried to get rid of them with a delete by volume node but it didnt seem to want to play.. Any ideas mr Core?

http://www.highendcams.se/Niagara.mov

Ok, tested some dynamic collision.. Get some funky movement, that I dont seem to be able to get rid of.. Will test more soon.. http://www.highendcams.se/The_Racer.mov

mr Core said something about this in an earlier post -



The sticking to geometry I can get rid of by lowering friction and restitution on obstacles to 0.005 and setting friction on fluid properties also to 0.005. possibly has drawbacks to use low values like that though...

By the way, thanks mr Core for that vorticity scene. It works but in my scene it gives me a lot of jittering/noise with particles changing values each frame apparently. I fixed it by hooking up a 'smooth color' compound and now it looks great.