-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lossy MagicaVoxel Import: Missing Layers, Objects Discarded #401
Comments
Tried perusing the codebase for a |
Alrighty, after finagling scon, I got it to compile with
😂 |
It's probably a mix of problems. One issue with importing magical voxel files is that goxel doesn't support palette based materials, so it just discards the information on import. In theory there is no limit to the number of layer goxel supports, but it's very possible that there is a bug there, since I never tested it on complex files like that. I'll try to have a look, see if at least I can add some logs in case of errors. |
The attached file 'high-rise-magicavoxel' seems to be empty. Did you upload the wrong file? |
@guillaumechereau That's ... odd! I'm not sure what happened. This one should work: |
Thanks. I can confirm the issue. Not sure what the problem is yet. |
Glad to hear I wasn't going crazy 😅 haha. I've heard a lot of great things about Goxel, so I'm excited to start porting things over to it and trying it out in my workflow whenever this gets fixed 🎉 |
Parse the _name attribute of magica voxel transform node and apply them to the layers. Related to issue #401.
I committed a change to at least try to get the proper layer names in goxel. I am still not sure why some parts are missing at the moment. |
Info
master
branchDetails
I tried to import a somewhat complex object I designed in Magicavoxel, and it seems some crucial pieces got left behind.
The file leverages several of Magicavoxel's features, including:
It seems like Goxel:
and gave up half way through 😅
The objects that it chose to omit almost seem like they reached an Object Ref Clone limit of some sort in Goxel. But, given that I'm not sure how Goxel works, that's purely speculation. Some clones made it in, but the majority of them didn't.
It also could be that the overall object count was too high for Goxel, and it gave up after it reached its limit.
That being said, it could have also just been an error that occurred while it was importing and it skipped the rest of the
.vox
file. 🤔All I got when I ran goxel from the console was this:
Here's what I ended up with in Goxel:
And here's what it looks like Magicavoxel:
The text was updated successfully, but these errors were encountered: