Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

After taking a little bit of thought, exporting in that way won't add any optimization to your models, since it'll be identical to the magicavoxel export.

I'll add it into the program as an option, but if you really want to optimize your models, I would recommend using the textured methods.

(+1)

So there isn't a way to optimize the meshes while still being able to just use the color palette? Why so?

Effectively it comes down to how the color palette works. If you store the color data without using UVs, you have to split each polygon based on its color.
Say for example you have a large square that is subdivided into 4 smaller squares in voxels. Using materials, each of those smaller squares have to be independent polygons, leading to 8 polygons. If you use a texture, you can reduce that to 2 polygons. 

There are still some reductions that can be made with a palette texture or materials, however, such as batching/instancing within Unity. 

I'm currently working on a Unity plugin for the program, which will allow you to directly import your vox models through Unity with all the same properties as the standalone program. Might be of interest to you since you can batch materials using it.