James Charles

Hey,

So I frequently make otls where I change what is being displayed based on what folder the user is looking at. I object merge different sections of the otl into a switch that has an output sop set to the 0th output underneath (since the display flag on the otl always shows the 0th output). A callback on the folder parm sets the input parameter of the switch, so as you change folders to edit different parameters, what is being displayed is changed. Then I use a second output sop to be the proper output of the otl, the finished product. I would love to be able to do this with only one output for my otl though. I think it would be nice to have an option on the output sop that doesn't just say ‘this node is output 0, this one is output 1’. It would be really handy if you could setup one output node that is the otls ‘display’ output, and a second that is the otls ‘output’ output if you will. I'm wondering if there is already a way to do this that I don't know about perhaps? Thanks!

James C

Hey all,

So I spent a long time trying to use collision volumes to act as a container but I wasn't able to have the fluid source node create an accurate enough volume representation to behave the way I needed it to. A friend of mine helped me get this working though and as usual in my experience, it turned out to be a simple drop down. In the fluid solver in the volume motion > collisions tab the velocity type needed to be point instead of rigid. This allowed me to use rbd's for the collision type which was faster than the velocity volume method, and still have the fluids hold their separation. Here is a sample file of how I have it working now.

Right so I have been using the object merge method but instead of “into specified object” I have had it set to “into this object”. After changing that though the dop net still doesn't seem to see this as an obj level transformation. Sorry if I am missing something fairly obvious here. :?