the generated blocks are very few and voxel is very tiny • SOLVED
See original GitHub issuehello @Zarbuz ,
i am on macOs 10.15.7, and used the lastest release of FileToVox with this command:
./FileToVox --i /Users/sylvainfiloni/Downloads/rainbow\ 2.ply --o testvox3
I wonder why the vox file generated is very small, with a very low value for blocks. Here is the console output with the “rainbow 2.ply” file
[INFO] FileToVox v1.14.0.0
[INFO] Author: @Zarbuz. Contact : https://twitter.com/Zarbuz
[INFO] Specified input path: /Users/sylvainfiloni/Downloads/rainbow 2.ply
[INFO] Specified output path: testvox3
[INFO] Specified output path: /Users/sylvainfiloni/Downloads/FileToVox-v1.14-osx/testvox3
[INFO] Start reading PLY data...
[INFO] Done.
[INFO] Max X: 9,7875805, Y: 7,557913, 6,8279366
[INFO] Min X: 3,1533642, Y: 5,5825043, 0
[INFO] Size X: 6,6342163, Y: 1,9754086, 6,8279366
[INFO] Started to voxelize data...
[INFO] Done.
[INFO] Started quantization of all colors ...
System.TypeInitializationException: The type initializer for 'Gdip' threw an exception.
---> System.PlatformNotSupportedException: System.Drawing.Common is not supported on non-Windows platforms. See https://aka.ms/systemdrawingnonwindows for more information.
at System.Drawing.LibraryResolver.EnsureRegistered()
at System.Drawing.SafeNativeMethods.Gdip.PlatformInitialize()
at System.Drawing.SafeNativeMethods.Gdip..cctor()
--- End of inner exception stack trace ---
at System.Drawing.SafeNativeMethods.Gdip.GdipCreateBitmapFromScan0(Int32 width, Int32 height, Int32 stride, Int32 format, IntPtr scan0, IntPtr& bitmap)
at System.Drawing.Bitmap..ctor(Int32 width, Int32 height, PixelFormat format)
at FileToVox.Extensions.Quantization.CreateBitmapFromColors(List`1 blocks)
at FileToVox.Extensions.Quantization.ApplyQuantization(List`1 blocks, Int32 colorLimit)
[INFO] Vox Width: 11
[INFO] Vox Length: 11
[INFO] Vox Height: 4
[INFO] Total blocks: 104
[INFO] Started to write chunks ...
[INFO] Done.
[INFO] Check total blocks after conversion: 104
[INFO] Done.
What did i do wrong ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Bug - (Voxel game) Only part of the mesh is generated
So I'm working on a procedurally generated voxel game, and it worked fine using cubes, but that was way too laggy, so I...
Read more >Method to compress chunks for voxel engine?
Hey! What would a good method be to compress chunks for a voxel engine (basically minecraft clone)? I'm doing it in scratch, so...
Read more >How to efficiently cluster voxel space into the fewest ...
Here are the approaches I have tried and the problems I find with them. The block counts reported are for filling a 256^3...
Read more >Voxel instancer · Issue #223 · Zylann/godot_voxel
Currently, digging under an instance makes it disappear. The algorithm to detect instances is quite naive, but performance is ok for small ......
Read more >Smooth Voxel Mapping: a Technical Deep Dive on Real-time ...
Every voxel in my game is stored in a std::vec::Vec . And I have a nice wrapper object that lets you index using...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

You must specify the grid-size :
--gs 256for exampleThanks Nicolas, i close this thread, as you solved the initial issue, and will open a new one if i can’t handle the color related one 😉