Page History
...
Div | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Emit Mode | ifnotsolid – Specifies the way the objects in the Emitter Nodes emit fluid. Surface Force – The surface of the emitters will eject the selected fluid channels along the geometry normals. In this mode, the discharge is named Outgoing Velocity and it specifies the speed of the emitted fluid in units/sec. The displayed units will change accordingly if the scene units change. This mode can work with both Solid and non-Solid emitters. If you use a Mask for the discharge in Surface Force mode, white areas of the emitter's surface will eject fast fluid, while darker ones would emit more slowly. Black areas will not emit at all. Volume Brush – The fluid inside the volume of the emitters will gradually change towards the selected channel values. When this mode is selected, the discharge is named Brush Effect (%) and it specifies the rate at which the transition takes place. When Brush Effect is 100%, the fluid will immediately reach the selected channel values, and if Brush Effect is less, it specifies how close the fluid values will get to the values from the Source over 1 second. E.g. if the Temperature inside an emitter's volume is 1000 and the Source emits Temperature 2000 with Brush Effect of 80%, then after 1 second the temperature will have risen to 1800. This mode is useful for creating standing volumes of fluid with a high Brush Effect, or alternatively - to slowly convert the fluid inside the volume of the emitters to the values selected below over a period of time. Note that you can both increase or decrease the values of the fluid channels in Volume Brush mode. When Brush Effect (%) is 0, then the Source has no effect. This mode requires that all selected emitters are set into non-Solid mode from their Per-Node Properties. If you use a Mask for the discharge in Volume Brush mode, white zones in the volume will have the Brush Effect you have specified, while darker zones will use a smaller Brush Effect. Completely back zones in the mask would not be affected at all by this Source. Volume Inject – The volume of the emitters will discharge the selected fluid channels with added pressure. When this mode is selected, the discharge is named Inject Power and it specifies the added volume of the injected fluid per second. This mode is useful for getting explosive discharge. Inject Power can be negative, in which case the Source will suck in and delete the fluid. This mode requires that all selected emitters are set into non-Solid mode from their Per-Node Properties. If you use a Mask for the discharge in Volume Inject mode, white zones in the volume will have the Inject Power you have specified, while darker zones will use a smaller Inject Power. Completely back zones in the mask would not be affected at all by this Source.
|
...
Noise | noise – Varies the Outgoing Velocity, Inject Power and Brush Effect (%) across the surface or the volume of the emitting geometry or particle. The variation also changes over time. This is a shorthand for using an animated noise in the Mask slot.
Emitted Channels
...
Div | ||||
---|---|---|---|---|
| ||||
Temperature | temperature, uset – Specifies the temperature of the emitted fluid, in Kelvin. A value of 0 is absolute zero, and a value of 300 denotes room temperature. Temperature above 300 makes the fluid rise up, while temperature below 300 makes it fall down. You can find out more about Phoenix Grid Channel Ranges here. If the Temperature channel is not enabled in the Output rollout of the Simulator, this parameter will be ignored. Modifiers | dmodt – Discharge Modifiers can be attached here in order to affect the Temperature parameter. Mask | tmap, usetmap – Allows you to vary the channel over the surface or the volume of the emitters. If this is not used, the Source will emit equal temperature over the entire surface or volume of the emitters. |
...
Div | |||||||
---|---|---|---|---|---|---|---|
| |||||||
RGB | uvw, useuvw – If the RGB Map is not enabled, the emitted fluid's RGB channel will contain the specified color. If the RGB Map is enabled, the RGB values from the texture map will be used instead of the color swatch. If the RGB channel is not enabled in the Output rollout of the Simulator, this parameter will be ignored. Also, note that if Emit Mode is set to Volume Brush or Volume Inject and the Map uses Explicit Map Channel or Vertex Color Channel mapping, then the Map will be applied on the whole volume, based on the closest geometry surface. Modifiers | dmodrgb – Discharge Modifiers can be attached here in order to affect the RGB parameter. Map | uvwmap, useuvwmap – Allows you to vary the RGB over the surface or the volume of the emitters. If this is not used, the Source will emit equal RGB over the entire surface or volume of the emitters. None – The RGB channel will not vary.
|
...
Div | |||||||
---|---|---|---|---|---|---|---|
| |||||||
Output Drag Particle Channels - Drag particles are created as separate particle systems per each Source that creates them, using the name of the emitting geometry. This is why the particle channels written to the simulation cache files are chosen from the Source, unlike the channels of other particle types which are set through a Simulator's Output rollout. Note that writing more channels to the cache files takes more time and will add up to the simulation time, so if you know in advance that you will not be needing a certain channel for rendering, then it would help the simulation times if you turn it off. Velocity | prtexportvel – When enabled and the particle Type is set to Drag, this parameter exports the Velocity channel to the cache files, so that you can use it for rendering with motion blur or coloring of particles based on their speed using the Particle Texture. ID | prtexportid – When enabled and the particle Type is set to Drag, this parameter exports the ID channel to the cache files. Age | prtexportage – When enabled and the particle Type is set to Drag, this parameter exports the Age channel to the cache files. RGB | prtexportrgb – When enabled and the particle Type is set to Drag, this parameter exports the RGB channel to the cache files.
|
...
Anchor | ||||
---|---|---|---|---|
|
UI Text Box | |||
---|---|---|---|
| |||
|
...
Anchor | ||||
---|---|---|---|---|
|
Texture UVW
...
UI Text Box | ||||
---|---|---|---|---|
| ||||
The main purpose of Texture UVW is to provide dynamic UVW coordinates for texture mapping that follow the simulation. If such simulated texture coordinates are not present for mapping, textures assigned to your simulation will appear static, with the simulated content moving through the image. This undesired behavior is often referred to as 'texture swimming'. In Phoenix such textures can be used for mapping the fire or smoke color and opacity of volumetrics, as well as the color and opacity of meshes. Texture can be also used for displacing volumetrics and meshes. UVW coordinates are generated by simulating an additional Texture UVW Grid Channel which has to be enabled under the Output rollout for the settings below to have any effect. For additional information on the Texture UVW feature, please check the Dynamics rollout documentation. |
...
Sphere, 1 voxel – Each particle will be the size of one grid cell. Particle sizes and shapes will be ignored.
Sphere, use size – The particle sizes will be used, but the shape will always be spherical.
Sphere, custom size – The particle shape will be spherical and the size will be taken from the Custom Prt Size field.
Use particle shape – The particle shapes will be used as they are provided. This might slow the simulation down if there are a large number of particles.
UI Text Box | size | medium|
---|---|---|
| ||
When a source emits from non-solid particles in any of the Sphere modes, the simulator traces each moving sphere and emits continuously throughout its trajectory, no matter how fast the particle is moving and how many steps the simulation uses. In a contrary way, in Use particle shape mode, the particles are getting evaluated the same way as regular mesh geometries, so in motion they are sampled only at the simulation steps without filling the trajectory in between the particle positions in time. In such case, if a particle moves very quickly and the simulator has low Steps per Frame, the trajectory of the particle would get interrupted and you should increase the simulation steps in order to keep it continuous. |
...