VDB import position
Moderators: ChrisHekman, aoktar
- adriendupagne
- Posts: 58
- Joined: Thu Mar 05, 2015 8:28 pm
VDBs are not importing in correct locations. Never have. When will this be fixed?
There's nothing to fix. You should apply correct procedures to export and import.adriendupagne wrote:VDBs are not importing in correct locations. Never have. When will this be fixed?
Please shares original scene and exported VDB. So will help you to show correct approach.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- adriendupagne
- Posts: 58
- Joined: Thu Mar 05, 2015 8:28 pm
please provide documentation or guide to show proof of work.
Many users reported this issue.
Many users reported this issue.
I cannot help in this way. Please consider to do my request for getting some help. It's just a container for voxels, proper way should be done.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
- jayroth2020
- Posts: 488
- Joined: Mon May 04, 2020 7:30 pm
There is a known issue with X Particles not matching Cinema coordinates when writing out a VDB file. By any chance, did you create your VDB with X particles?
Puget Systems / Intel Core Z790 ATX / RTX 4090 / Cinema 4D