Leaderboard

I've spent a couple of days to look at the format used by LDD to store its bricks. I had to debate a bit with myself if I wanted to release it, but I concluded that a viewer couldn't hurt. As of now, it only shows .g files that do not have .g1, .g2, etc files of the same name. You'll find that you can still view such parts, but they'll not show any geometry at all, or parts of it are missing. I'd recommend extracting the assets.lif, then the db.lif, then dump the .jar file in there, then run it. The file format itself is a custom format, as we found out, and clearly designed to be used with openGL, which is the renderer used by LDD. For most files, less than half of the .g file is used to describe the geometry. The rest of the file I have sortof mapped out, but haven't found out what it contains. I have considered posting the specification of the file format as far as I managed to map it out, but I'm a bit cautious to do so given that I can not oversee the implications of a brick geometry file converter with respect to lego's copyright enforcement. It's still reverse engineering either way. Controls: arrow keys: rotate X and Y axis Q/W: rotate Z axis A/Z: zoom in/out N/M: wireframe off/on Download Link

-

We have been impressed and encouraged with the dedication of our Rock Raiders fans, and after years of requests we are looking at creating a new Rock Raiders. We are considering combining a mine craft style world, so you can build and dig in more ways, please tell us what you think?

You're welcome! The XML files do not contain geometry data, though. They contain physics data. In short, when a computer has to perform a physics simulation, it can simply not check for collissions between every single triangle of a model. You'd get billions of comparisons, and if you're supposed to render at 60FPS, you simply haven't got the time. So instead every model has a bunch of bounding boxes instead. Boxes are very easy to do collission tests on, and reduce the overall number of tests that have to be performed. These collission box definitions are in the XML file, along with some other properties, like the bone structures of tubes and how the brick can interconnect with other bricks.

http://www.rockraidersunited.org/topic/3942-ddi-looking-for-help-with-new-rock-raiders-title/