Again recently there was a time when it was nearly two weeks with no twitter activity, and on ephtracy's return activity has been limited to retweeting and favouriting. There was a time recently when ephtracy didn't tweet for quite a while and when I asked about it, concerned, it turned out it was due to illness. On top of that we don't know how much spare time ephtracy has to devote to the program. It never feels right to ask ephtracy for fixes though, even politely, mainly because magicavoxel is in most ways a very excellent piece of software, offering some features that qubicle does not (marching cube render and export, perspective camera and ambient occlusion in the modeling view, massively suprerior renderer, easy palette setting etc.) All this while being free compared to qubicle's not inconsiderable price! qb export as well though surely means that yes it needs fixing. I suppose it would be more a problem with the documentation of the format rather than the data. Also the colours are coming out wrong even using the default palette in magicavoxel. Models imported from magicavoxel are coming out the wrong way round in qubicle which you may not notice until you have a model with writing on it. As for the code itself, its really simple: we just import the loader library, instantiate it and pass it the name of the. vox I would argue that maybe it isn't a bug since the program writes it and the program reads it the right way. BUG: Magicavoxel vox import mirrored and wrong colour. So the error is with magicavoxel? If it was just that way in the magicavoxel. Whether *.VOX or *.QB MagicaVoxel is going to flip that X coordinate data. Originally posted by Mighty_Borlaug:The Staxel Community has been trying to PM the MV Dev and see if he can fix the "X-Flip" bug for ages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |