VDB step size changing automatically in rendered view
Posted: Wed Oct 30, 2024 8:34 am
Hello guys,
I am experiencing an issue which is hard to debug. I know VDB volume step size changed in the latest version to a % which is likely something to do with it.
This is on a scene which was only created in the latest version (no compatibility issues).
The issue is without changing the volume medium settings, upon loading the scene, sometimes the rendered result is different for the VDB volume even without changing the volume step percentage in the medium.
I then have to change the volume step % to get it back to what it should look like, but is actually the incorrect percentage. Then, after a load or two it changes appearance again based on the changes I had to make. Then I need to reset values to the original to get correct appearance. Ultimately I end up in an endless cycle of repeating the above.
This happens on VDBs from different sources so not limited to a specific VDB file.
I am using the default octane volume. I am not changing any of the default settings, simply adding a VDB file and a medium node (screenshot attached).
It is as if the medium is incorrectly reading the voxel size of the volume on load?
Just bringing to your attention. As it is quite annoying...
I am experiencing an issue which is hard to debug. I know VDB volume step size changed in the latest version to a % which is likely something to do with it.
This is on a scene which was only created in the latest version (no compatibility issues).
The issue is without changing the volume medium settings, upon loading the scene, sometimes the rendered result is different for the VDB volume even without changing the volume step percentage in the medium.
I then have to change the volume step % to get it back to what it should look like, but is actually the incorrect percentage. Then, after a load or two it changes appearance again based on the changes I had to make. Then I need to reset values to the original to get correct appearance. Ultimately I end up in an endless cycle of repeating the above.
This happens on VDBs from different sources so not limited to a specific VDB file.
I am using the default octane volume. I am not changing any of the default settings, simply adding a VDB file and a medium node (screenshot attached).
It is as if the medium is incorrectly reading the voxel size of the volume on load?
Just bringing to your attention. As it is quite annoying...