Leaderboard

Game Extractor has had the ability to extract LEGO Digital Designer LIF files for a while, but since Game Extractor isn't very stable, I wrote my own LIF extractor in Python. The download contains the Python source file for use with a python interpreter, as well as Windows 32 bit and Windows 64 bit executables. Download LIF Extractor GitHub For those of you who will probably ignore the Readme.txt file entirely, here's the information on it: You accept full responsibility for how you use this program. This program is released under GNU GPLv3. LIF Extractor is a command line utility for extracting the LIF files found in LEGO Digital Designer. It will extract all files contained inside the LIF archives, into folders adjacent to the archive it was called on. The LIFExtractor.py file requires a python installation to run. The executables found in the folders have no dependencies. Choose the proper folder for your operating system. The Python script has been tested to work on Python versions 2.7 through 3.2. To extract LIF files, pass the path to the LIF files as command line arguments to the program. On Windows, this can be done by dragging and dropping the LIF files onto the LIFExtractor.exe icon in the explorer window. This program was created to allow for interoperability with the LEGO Digital Designer formats. In order to properly read the LEGO Digital Designer formats, it is necessary to access the data contained with the LIF file archives.

Its old. But was a lot of drama back then. I remember when he told everyone he would only releas the mod if his crappy Youtube Video got 100.000 clicks. After it got 100.000 clicks he said he wouldnt count them for some reason. Oh and of course his forums....TIM IS BEST MODDER KOTF IS BEST MOD HOW DARE YOU INSULT HIM IF YOU DONT LIKE IT DONT PLAY IT RARGHRAGHL.

I have been trying to figure these out. I am at least certain that they contain the geometry data in some way. The files seem to have some kind of binary format, but from what I can see they have small repeating patterns, which could be 3D coordinates. The problem is that the files seem to be linked to each other in some way. For example, by far the smallest .g file is the one of the stormtrooper helmet, which of course has by no means the smallest polycount of all brick models. So I think it gets its other geometry data from other .g files. The directory name, "brickprimitives" seems to confirm this. The LFXML and XML files that share the names of the .g files define all the properties of the bricks. Mostly their physics simulation properties (bounding boxes, center of mass, etc). They have a link to a part number (a .g file) Edit: figured out why parts are split into multiple files; textured objects require a different kind of rendering, so it looks like parts of the brick that have different textures than the rest are separated into their own files. I have verified it with a few bricks, and all bricks that contain textures seem to be split up.

Yeah, I remember you! Welcome back to the vacuum of space and time that is known as RRU. I see you couldn't escape for long, so I warmly welcome you back.

It's a bunch of legal jargon designed to get consumers to skip it so corporations can screw people over unfairly. It's deceptive by nature and a law to put a user-readable summary at the top of an EULA should be put into place. Also, a board is made out of wood. Reading EULAs makes you bored. Please.