RealFlow Official Forum

It is already great, but man Filter would be incredible if it were a nodal network of test conditions and rules. Pflow for RealFlow!

Even just adding a stack to the filter so that we can have multiple tests in one daemon, such as "if a particle from emitter01, emitter02, or emitter03 is colliding, move to container01" We can do this now with multiple Filters, but it gets redundant and unnecessarily complex.

But definitely consider the nodal thing

I second that, plusy having something similar to the for- each node in Houdini was very nice.

Yea...very nice ideas. Actually It would also help a lot, if one could use the same conditions and rules as scripting offers. It would make things even more comfortable and fast. For example checking for surface particles and so on...Having that in a filter deamon would be awesome. Scripting should be done for the most complex stuff which does not fit into any deamon or is meaningless in a deamon...but such simple functions where you only need a single threshold value or two, could be very powerful to have right there in the filter.

Hi,

the most complex case of the current Filter Daemon is when the user sets a custom expression. It is evaluated using the same engine as curve editor expressions.

It sounds very interesting the ability to use an underlying layer of Python scripts. We will give it a try, but we are afraid we won't will be able to use it in a multithreaded context like with expressions.

If it is not the case, we could add equivalent conditions to the existing ones.

Thank you very much for the tip.

Cool, thanks