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
I'm experiencing difficulty loading a 3D-Tiles binary voxel (.voxel) file. While the file is successfully requested, it fails to load properly without any error messages in the console. However, when using the corresponding .json+.bin format, the file loads correctly. How can this issue be resolved?
The given data set does not seem to contain the .subtree files. (Also, it could be interesting to know how you created the binary files, but maybe that will be resolved or obsolete when we can test the data)
The property is called aa in the metadata schema that is defined in the tileset.json. But in the JSON part of the voxel file, the property is called a:
When you change the name to a in the tileset.json (which might be easier than editing the binary file), then it should work.
The Voxel functionality is still pretty new, and some tooling and support are still in development. Eventually, voxels might be supported by the 3D Tiles Validator, which then could point out inconsistencies like these. (No promise and no timeline for that)
I'm experiencing difficulty loading a 3D-Tiles binary voxel (.voxel) file. While the file is successfully requested, it fails to load properly without any error messages in the console. However, when using the corresponding .json+.bin format, the file loads correctly. How can this issue be resolved?
Below is my test dataset.
Dataset_testBinaryVoxel.zip
The text was updated successfully, but these errors were encountered: