thread 'main' panicked at 'Unrecognised material type 4291624755 with weight NaN', C:\Users\xxx\.cargo\registry\src\github.com-1ecc6299db9ec823\dot_vox-1.0.0\src\material\material_type.rs:24:18 about dot_vox HOT 4 CLOSED

Hi again!

Have pushed a short-term fix as dot_vox 1.0.1, which should remove the panic, replacing the mis-parsed material with an Unknown material for the moment.

This doesn't fix the underlying problem, which appears to be that the palette parsing is starting one block too early >.< Will continue to investigate the cause of this one and update when there's a fix.

Thanks again for the bug report - and love the model :)

from dot_vox.

Eek!

Thanks for the thorough bug report and sample file - I shall take a look as soon as I'm able to (most likely Wednesday & Thursday this week).

from dot_vox.

Hi again!

Have spent a bit of time rebuilding the parser, building up a tree of chunks and then mapping that into the DotVoxData. That seems to have resolved the issue around the data overflowing between chunks, which is a bit of an improvement ;) I've released this as 2.0.0 of the crate.

I've tried to parse your example character again, and in the process discovered a fairly big rewrite of the Material chunk format over in MagicaVoxel - which means that currently the material data in the file isn't being loaded. I'll spend some more time clearing that up and make another minor release before closing this issue off.

from dot_vox.

Hi again!

Have finished rebuilding the Material parsing. Unfortunately, as the underlying format had changed quite substantially, I've ended up having to change the content of the Material chunks to match, meaning there's another major release (3.0.0) and some API changes.

There's still some chunks left in the file that aren't parsed, which seem to be around a scene graph. I'll have a go at implementing these at some point in the future, unless a PR gets there first ;)

All the best!

from dot_vox.