The specification was created in a way to be expandable with new data without breaking compatibility.As such, you can already add morph targets / shapekeys data to models if you use lower case chunk names (like or ), but if you're willing to design a minimalistic data structure for it, I'd gladly add it to the official specification with an upper case chunk name. (Sadly I'm very busy with other pr
Not sure if its out of scope to add new things to the file specification, but would morph targets / shapekeys possibly be added?
Thank you very much for your feedback!Thank you and you're welcome!To decide, you can use . It can dump the contents of a M3D model (, , , etc. flags), or you can convert it into an (a textual variant, similar to Wavefront OBJ files). If there's a problem in the Blender exporter, then a quick fix is to edit the A3D in a text editor and then convert it back to M3D with .m3dconv-d-dd-dddm3dconvA3DAs
One side of the model has the texture applied correctly, but the other side looks strange. I'm not sure why, but the vertices are different in the original model. I'm not a professional in this area, just an enthusiast.Originally, the model only has 420 vertices. I'm not sure if it was an export problem in Blender or in M3D.I found this M3D format sensational, but the only problem I'm having is th
When I try to export a fbx mixamo model, "The Boss" for example, from blender. The model only has the diffuse and normal maps.
Wow, you already fixed it! thanks twice. And thanks for delivering us this amazing format.
Oooops, mea culpa, you're absolutely right! Fixed!
I'm using custom allocation functions for the library, but in some parts, it keeps using malloc, realloc and free. In my case it causes crashes because I am using odin lang allocators.https://gitlab.com/bztsrc/model3d/-/blob/master/m3d.h#L6340https://gitlab.com/bztsrc/model3d/-/blob/master/m3d.h#L4919https://gitlab.com/bztsrc/model3d/-/blob/master/m3d.h#L4310https://gitlab.com/bztsrc/model3d/-/blo
bzt(eb64b03e) at 03 Mar 13:24 Use proper memory macros, fix issue #39
Really appreciate the quick response and fix! I'm travelling today and will revisit this in the morning. I think you are right that the name of the assimp lib might have cause the issue. I'll get back with feedback on that and the NOASSIMP
I know this isn't a solution just an ugly workaround, but I've added commit 2ac71565This allows compiling without assimp entirely, just pass to CLang, or usem3dconv-DNOASSIMP=1Cheers, bztNOASSIMP=1 make
bzt(2ac71565) at 19 Dec 18:45 Add NOASSIMP compile option to m3dconv
Oh, maybe try copying as ? Maybe it's not the folder but the file name (do not rename, because run-time linking will still look for , not sure if you can statically link assimp in the first place. I had a conversation on github with kimkulling and he said static linking isn't supported in assimp, but that was years ago).assimp-vc143-mtd.libassimp.libassimp-vc143-mtd.dll
I am trying to build m3dconv on Windows 11 and am running into linker errors against assimp. I believe I have included all of the necessary libraries, so I am not sure where I am going wrong. From what I could find online, these references require irrxml so I built and used the static libs from the latest assimp with irrxml included (5.0.1).In my libs folder is assimp-vc143-mtd.lib, IrrXMLd.lib, z
I am trying to build m3dconv on Windows 11 and am running into linker errors against assimp.I believe I have included all of the necessary librariesFrom what I could find online, these references require irrxml so I built and used the static libs from the latest assimp with irrxml included (5.0.1).No wonder, assimp isn't the greatest software at least to say. There's a good reason why I'm trying t