Here, the target is only overwritten when the given "Condition" is not fulfilled. Please note that the result with this mode might slightly differ from the original simulation of the source emitter. If you also clear the target emitters with each step, you can avoid these problems. Here, the simulation cache is cleared with each frame and new particles are loaded from the cached file sequence. Using them as source emitters will lead to instabilities, because the particles are not moved, but simply copied. This feature is needed when you work with cached fluids. Here, the target is only overwritten when the given "Condition" is fulfilled. Please note that the result with this mode might slightly differ from the original simulation of the source fluid. Using them as source emitters will lead to instabilities, because the particles are not moved, but simply copied. Here, the simulation cache is cleared with each frame and new particles are loaded from the cached file sequence. Otherwise you might see instabilities and particles explosions. It should only be used with → " Dumb" particles or "Override Target" set to "Yes". This option is suited for the creation of trails, for example. Otherwise the age value of the original particle will be used. When active, the filtered particles' age will be set to 0. Filters the particles outside this box only. The particles inside the daemon's bounding box will be affected ![]() Only available with an activated "Bounded" option: With this option it is possible to restrict the daemon to a certain volume. There is a long → list of keywords that can be used to create a certain condition. RealFlow constantly checks against the given expression  during a simulation and decides whether the condition is fulfilled or not. This field becomes active when “Condition†is set to “Expressionâ€. With “Condition†set to “In Range†or “Out of Rangeâ€, this field becomes unlocked to define a range between “Min Value†and “Max Valueâ€. With “Condition†is set to “In Range†or “Out of Rangeâ€, this field becomes unlocked to define a range between “Min Value†and “Max Valueâ€. Please note that this field is inactive with “Condition†set to “In Rangeâ€, “Out of Range†and “Expressionâ€. This is the trigger value for the condition. "Vorticity" has to be activated in the → fluid container (all fluid types, except "Dumb" have a "Compute Vorticity" option) before the simulation starts, otherwise the condition will never be fulfilled and there won't be any filtered particles.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |