Closed non-void closed 4 years ago
Since the generated files loaded fine in viewvox, I presumed my binvox output was fine.
This puts the model back in it's original position, I guess? I'll look into adding this, looks like an easy fix. Though I think it is optional in the .binvox spec, but I'd have to check.
@non-void
I added this in commit 476c980daf5dd27a24dc4576af29c70bc0be034c to the dev branch.
I'm working on some other features this week (CPU version of solid voxelize, update timings, ...), after that I'll merge dev into master for a new release.
Thanks for the suggestion, I looked up the binvox spec, and the translate
and scale
header entries don't seem to be optional, but the tool I was using to verify my .binvox files (viewvox) also works if they're not there.
Anyhow, cuda_voxelizer should now spit out .binvox file that work in that python lib you mentioned.
Already released it today on 0.4.7 - thanks! https://github.com/Forceflow/cuda_voxelizer/releases/tag/v0.4.7
I used cuda_voxelizer to generate binvox files and intended to read the file using binvox_rw_py
However, the file generated lacks translate and scale in its ASCII header, I have to manually add following lines to the function write_binvox:
I guess it is right, because I checked that all vertices falls in to voxel using the following coordinate translation function:
Do you have any support for this feature?