Skip to main content

On Sale: GamesAssetsToolsTabletopComics
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

Thanks for the comment!

I know I had some issues with drag and drop files in the past - But I'll have another look to see if I can figure it out.

Regarding the palette material, I don't know why I hadn't thought of this already.
Using one palette texture for all models will certainly be a good idea, so I'll add it near the top of my to-do list.

For now, I would recommend you use the material export, and import your meshes with 'Location: Use External Materials' in the materials tab.

Thanks again for letting me know!

Thanks for listening to our issues. By 'use external materials' in unity, do you mean the legacy option? I tried that, but I couldn't get it to work either.

If I understand correctly, you will add an option to allow us to export a .obj from this software, import the model to Unity, and allow a material like this to be used with it? Then we can just assign the material to it like this.

If this can be added in the next few weeks, I don't mind waiting. We really need this program for when we start to playtest on mobile, but it would be nice to start optimizing our models sooner than later so we don't have to go back and do so many.

Thanks again for the help!

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.