would allow for example pre-rendered ego-motion combination of 2D footage and 3D objects.Īnd more generally, 3D is uber-kewl but may also require usefull libraries, like physics for instance, that are not likely to be developped anytime soon for QC i guess. Providing a way to load up keyframed camera data. Access to vertices in a way (think sound deforming meshes)īut the most important thing to me is the fact that QC doesn't allow to handle the CAMERA -which is the most important thing to me when dealing with 3D. MAX is obvious, then of course Collada and. Personnaly, i would love to use 3d meshes in QC, provided the tools allow this: If it's totally useless, no matter, it's already done :)
3dm, but that' a bridge I'll cross when I get to it). If a model happens to be provided (like your sample one above) in NURBs only format, it's totally useless to me if kineme3d can't handle meshing it itself if it needs to.įear not though This discussion is dead: it was a mere 30 lines of code to add support for meshing nurbs objects ala fbx (I'm pretty sure it won't be as nice from. I'm not an artist, so these tools, while really cool, provide very little value to me personally. No 3D Studio, no rhino, no maya, no cad programs, no wings3d, no milkshape, no blender, nothing. I - this may come as a surprise - have no 3d tools on my machine.
Or maybe you want to save disk space, or remove the possibility of having stale duplicate models ("Did I update the mesh when I tweaked the model? I can't remember!") First, laziness: you don't want to bother dealing with meshing it yourself.