You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Voxelsize has been deprecated inside GVDB library.
Voxelsize size was originally a scalar on voxels inside GVDB. However, this is obsolete since most applications would like to have arbitrary transforms between world and voxels. The gvdb.SetVoxelSize function has been removed. Support for arbitrary transforms from gvdb grid to world coordinates during rendering is now possible with gvdb.SetTransform, which handles the rendering side of things. Applications are now responsible for maintaining their own voxel-to-world transforms and applying these wherever needed (in custom kernels, during SolidVoxelize, or during rendering with SetTransform).
The g3DPrint example has been updated, and shows how a specific application would maintain its own world transforms. g3DPrint now has m_voxel_size itself since this metric is specific to 3D printing (voxel size is in the sample not inside gvdb library). SolidVoxelize takes in a world transform during polygon-to-voxel conversion, which is maintained by the sample itself. The main_3dprint.cpp provides more detailed comments. This also makes the sample more flexible. The interface now allows for on-the-fly modification of the voxel size.
Currently, only the g3DPrint sample has been updated. Other samples may still need to be modified.
Applications will now maintain and use their own arbitrary voxel-to-world transforms.
Note: You must rebuild all of gvdb_library in order to adopt these changes
The text was updated successfully, but these errors were encountered:
… and kernels.
That is, gvdb->vdel[0] is always equal to (1, 1, 1) after the change removing
`voxelsize` (see issue #74).
- The CUDA code's `getNodeAtPoint` now takes four arguments and no longer
returns `vdel` (previously, it always returned `(1, 1, 1)`)
- Removes `pstep` from the `gvdbBrickFunc` signature, as this depends only on `dir`.
- Removes unused functions `rayTricubic`, `rayTrilinear`, and `raySurfaceDepthBrick`.
Voxelsize has been deprecated inside GVDB library.
Voxelsize size was originally a scalar on voxels inside GVDB. However, this is obsolete since most applications would like to have arbitrary transforms between world and voxels. The gvdb.SetVoxelSize function has been removed. Support for arbitrary transforms from gvdb grid to world coordinates during rendering is now possible with gvdb.SetTransform, which handles the rendering side of things. Applications are now responsible for maintaining their own voxel-to-world transforms and applying these wherever needed (in custom kernels, during SolidVoxelize, or during rendering with SetTransform).
The g3DPrint example has been updated, and shows how a specific application would maintain its own world transforms. g3DPrint now has m_voxel_size itself since this metric is specific to 3D printing (voxel size is in the sample not inside gvdb library). SolidVoxelize takes in a world transform during polygon-to-voxel conversion, which is maintained by the sample itself. The main_3dprint.cpp provides more detailed comments. This also makes the sample more flexible. The interface now allows for on-the-fly modification of the voxel size.
Currently, only the g3DPrint sample has been updated.
Other samples may still need to be modified.
Applications will now maintain and use their own arbitrary voxel-to-world transforms.
Note: You must rebuild all of gvdb_library in order to adopt these changes
The text was updated successfully, but these errors were encountered: