![]() You could “colorize” STLs for LEGO plans by importing your STL into a Minecraft world with and “reshape” and “repaint” it in Minecraft before creating the plan for your LEGO bricks. While being single-colored it is a disadvantage for the creation of LEGO plans, STL files are in WIDE circulation and most of them are absolutely FREE for personal use. Since the VAST majority of today’s household 3D printers are single colored, this is not a significant 3D printing limitation. ![]() STL files are widely used for 3D printing and do not contain color information. The most common 3D model file formats are: Some are widely available and free, others are scarce and you might need to pay for. Vastly simplified a 3D model is a scalable “picture” of an item you can “fly around” and look at from any perspective you wish.īecause of the broad application of 3D models, they come in different shapes and colors. If you ever saw a 3D printed object, played a modern video game, looked at Google Earth, used a GPS, or saw one of the great animated movies from Pixar, Dreamworks, Disney or other studios, you have been in close contact with 3D model files. What is a 3D model file, and where to get them? A Windows/Mac/Unix Computer with a Chrome/Firefox/Safari browser.I think the method works well, better than going through the XMLs every time (though it has be to be updated with each LDD release). I was positive it didn't have any file writing code, and since I saw it dumped it to the console, I figured you just copy-pasted it into a file. Yea, what you just said is what I got from reading your source. Then the parts list generator loads that in at runtime (way faster than looking through all the XML files again, saves a couple of seconds )Įxcept db.lif is located in %AppData%LEGO CompanyLEGO Digital Designer one more folder here, I think. I dumped it to the console, saved the contents of the console to the "partNames.txt" that comes with the converter. So all I had to do to get a link between the part number and its name was to open each XML file, read its name, and link it to its file name. ![]() 2863.xml), and they all have the part name stored in the XML file itself. Each of those XML files is named after the part number (ex. It should be stuffed with XML files and a folder called "LOD0". Finally, go into the Assets/db/Primitives folder. This would create the partsList.txt file if it were run, correct?įrom the top of my head, you first extract the Assets.lif file, then find db.lif and extract that one. As for your source, it looks like it just creates a simple file tree almost. His LIF Extractor doesn't produce a file list, unless you edited it to write one as it extracted the archive. Get it at Įdit: yes, the code is pretty horrible. Note that for both "tools" you need to add XOM to the buildpath. I used JrMasterModelBuilder's (did I get that right?) LIF exctractor to get to those There's a third file in the jar that parses the XML files that define the bricks, but isn't actually used in the tool. ![]() Here's the complete source code (2 files): It will then spit out an html file in the same directory as the jar that has thec same name as the LXF file, which contains the parts list. Though I suppose you can also supply it with an absolute path to a file if you so desire. lxf file name of a file that is located in the same directory as the jar. I thought that by running it it would explain itself well enough, but I guess that wasn't the case. Sorry about that! Yes, the program is *very* simple. Download, but didn't know how to use it for lack of readme (ended up extracting the JAR and reading your strings).Ĭan you provide source code perhaps? I'd love to see how it's written. ![]()
0 Comments
Leave a Reply. |