I'm really interested in the volumetric stuff. Can that be done in the Daz plug in?
Not currently. If there is a DAZStudio voxel plugin, or DAZStudio is enabled to allow loading of VDB files, then it could be added to the plugin. Until then, you need to export to OCS/ORBX and add the Volume (VDB file) node in Octane Standalone.
Paul
Why is it important for Daz to be involved with this? The actual vdb fill 'boxes', and we can create boxes in Daz. Once it hits Octane, its just a question of defining what to put in the geometry.
----------------- Intel i7-4790K, Asus Z97-A, Corsair 32GB DDR3 1866MHz CL9, 2XAsus STRIX GTX980 DirectCU II OC 4GB, 4XSamsung 840 EVO Raid 10, Win 7 x64 Pro.
Why is it important for Daz to be involved with this? The actual vdb fill 'boxes', and we can create boxes in Daz. Once it hits Octane, its just a question of defining what to put in the geometry.
Doing it this way is very hard to implement, because a) the plugin needs to somehow provide a way to provide a means for the user to define "what to put in the geometry", and b) even once you have the Octane Volume geometry, the volume material (which is a Medium) then needs to be defined and editable.
Will submit a feature request at DAZ3D to provide the velocity speed for each vertex in the SDK.
They are probably aware of the issue but maybe they can share some information if some work in that direction is scheduled or not.
Thanks - I will be interested to hear the outcome. Even if the SDK provides vertex velocities, it is still a complex enhancement, since the velocities will most probably be in local space coordinates, and when you do a final render which flattens all the scene geometry into a single Octane node, the plugin will need to convert the local space velocities into world space. Also, if the velocities are in local space, then the transform velocity will also be needed (since the world space velocity = local space vertex velocity x object transform velocity). So not only would the DAZStudio SDK need to provide vertex velocities, it also needs to provide the transform velocity.....and then I need to do a lot of coding to implement it. So the probability of all this happening is low....so it is vastly easier to use the current export to Standalone function to achieve the same outcome.
Paul
Did not receive any specific information if there are plans for Vertex Motion Blur for DAZ Studio. In any case based on the "standard" reply the feature request is added to the bug tracker.
I'm submitting your ticket to our bug tracker as a feature request. We will let you know if we have any further questions regarding your request.
Please note, this does not guarantee the request will be fulfilled.
Once it hits Octane, its just a question of defining what to put in the geometry.
