Its origins go back to 1995, and the accuracy of the brick models is often hit or miss (there's an especially notable problem where all the holes in Technic bricks are at the wrong height). LDraw is a (mostly) fan-created library of 3D LEGO pieces and software for doing things with them. For example, if you build a model in LDD, then export to OBJ with an LDraw-based program, the geometry in the OBJ will be of LDraw's pieces, as if you had built it in LDraw to begin with.įor these tests, I built a simple test model in LDD, which I was then able to also work with in LDraw-based programs (in this case, LeoCAD) and in Mecabricks, thanks to the cross-compatibility mentioned earlier (though Mecabricks lacked the specific window pieces I'd used, so I had to swap them out with a very similar part it did have). So, while these systems have some level of cross-compatibility (LDD can import and export LDraw models, and Mecabricks can import LDD models), this has no bearing on the brick geometry used. The three systems mentioned above actually have their own libraries of 3D LEGO pieces. Rather, it's a list of what pieces to put where, in what colors, etc. But just how inefficient? Let's find out.įor those who may be new to all this: When you create a model with LDraw-based software, LDD, or Mecabricks, the saved model doesn't contain the actual geometry of the pieces.
They'll also probably be told this isn't a very good idea, because the results will be highly inefficient. Often times people just use exports of LDraw models or similar things, without thinking about it too much.
Let's say you're working on a model for a new Rock Raiders vehicle, or making a fan game, whatever.
0 kommentar(er)
