Tweet
I've come across a couple of issues when rendering PhoenixFD containers in Mesh mode.
1) This isn't a bug as much as it's a workflow issue: when rendering mode is set to 'Mesh', the 'Volumetric Options...' button becomes greyed out. But there are many reasons why a person would need to open those settings, even when in Mesh mode (for example, to change smoke/fire color when a PhoenixFDTexmap map is applied to the mesh). It would be nice if that button was never greyed, so that we don't have to switch back to volumetric mode to open those settings.
2) When rendering is set to Mesh, and I use a PhoenixFDTexmap map on the mesh to set its color (with channel set to 'Rendering Smoke Color' and the smoke color itself derived from grid channel 'Speed') , the map does not evaluate properly when network rendering, but evaluates properly during local renders. A solution I found was to duplicate my phoenix container, set the duplicate's rendering mode to Volumetric and then point my PhoenixFDTexmap to that container instead of the container set to "Mesh". So it seems like volumetric channel data is not loaded properly while in "Mesh" mode, during a network render.
1) This isn't a bug as much as it's a workflow issue: when rendering mode is set to 'Mesh', the 'Volumetric Options...' button becomes greyed out. But there are many reasons why a person would need to open those settings, even when in Mesh mode (for example, to change smoke/fire color when a PhoenixFDTexmap map is applied to the mesh). It would be nice if that button was never greyed, so that we don't have to switch back to volumetric mode to open those settings.
2) When rendering is set to Mesh, and I use a PhoenixFDTexmap map on the mesh to set its color (with channel set to 'Rendering Smoke Color' and the smoke color itself derived from grid channel 'Speed') , the map does not evaluate properly when network rendering, but evaluates properly during local renders. A solution I found was to duplicate my phoenix container, set the duplicate's rendering mode to Volumetric and then point my PhoenixFDTexmap to that container instead of the container set to "Mesh". So it seems like volumetric channel data is not loaded properly while in "Mesh" mode, during a network render.
Comment