VrayVolumeGrid Motion Blur problem

[Svetlin.Nikolov]

Oh, the motion blur issue with more than 10 Simulators in Volumetric mode is at least solved in the latest Phoenix 4 nightlies (I believe it was not part of the latest 4.41 release) and also in Phoenix 5. Maybe you could use Phoenix Simulators instead of VRayVolumeGrids to work around it?

[tdugard]

Yeah i know but the downside of using phoenixFD node is that you need a sim licence to modify shading or parameters so it isn't convenient for artist that need to tweak the look if needed

[Svetlin.Nikolov]

Hmmm, true. Now that we have the separate Voxel Shader node, we need just a new Cache Loader node to work around this... Right now a Simulator would also work for that purpose - it could load the data and if you don't need any changes to the Input rollout or preview settings, you wouldn't need a license. And the Voxel Shader will not ask for a Phoenix license, so you can change the render settings. It's getting complicated though, but just a setup I though of in case it's helpful.

[tdugard]

That Voxel shader is a great idea but its too bad that the preview setting needs a licence, when i'm set dressing a shot, i need to preview the volume to place it correctly and then switch of the preview for faster viewport performances. The licence should be only for simulation purpose

[Svetlin.Nikolov]

Yess, this will happen eventually, I hope to be able to break the Simulator up into separate nodes for simulating, writing caches, reading caches, previewing, meshing, converting from grid to particles, particles to grid, etc... the separate Voxel Shader was the fist step in this direction. This would allow the licenses to be engaged in the proper circumstances.

[Joelaff]

That will be awesome!

[Svetlin.Nikolov]

Indeed!

Need to add more symbols because it would not allow me to post otherwise
Need to add more symbols because it would not allow me to post otherwise
Need to add more symbols because it would not allow me to post otherwise