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. MagicaVoxel cannot export to any formats that support animation, and in any case the type of animation it uses isn't a fit for typical formats that do support animation (via keyframes, morph targets, and skinning). 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. vox I would argue that maybe it isn't a bug since the program writes it and the program reads it the right way. 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.
Magicavoxel import code#
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. Copilot Packages Security Code review Issues Integrations GitHub Sponsors Customer stories Team Enterprise Explore Explore GitHub Learn and contribute Topics Collections Trending Skills GitHub Sponsors Open source guides Connect with others The ReadME Project Events Community forum GitHub Education.
0 kommentar(er)
