Florimel

Thanks to all of you for your precious advices. Legal concerns are one thing, but I agree that ethics needs to be considered. This is primarily the reasons why I was seeking here for counsel. Definitely, I wouldn't injure the good relationship that we are having with the LDD developement team. They are doing an outstanding job with their software and are providing a great service to our community of LEGO fans. Long live LDD !

So it means that, as long as I do not reference any specific .LIF file, or any specific .G file, if I focus only on those respective formats themselves (as opposed to the actual content of some specific files with those format), it's not a problem to document my findings, or to provide some convertors, right ?

Some methodologies were already available online, explaining how to extract LDD's geometry for the propose of interoperability, like this first method or .They both rely on manual extraction of the 3D geometry displayed on screen using Dassault Systèmes' 3D PrintScreen tool, and varying amount of manual rework of the resulting 3DXML file before it can feed another application. I found this overall process to be quite cumbersome indeed. And this is how I get motivated to do some reverse engineering of the native assets themselves, basically to achieve to same interoperability objectives, but in a much straight forward manner.

Greetings, and welcome.

Excellent news indeed, I'm downloading now...

Hello to all ! Congratulations to all contributors of this great forum. I was an anonymous reader until now, but I decided to register ! I'm from Paris, France, by the way...

I've seen several threads on this forum and others asking for LDD export capabilities to standard formats, and generally speaking for a better interoperability between LDD and other softwares. I know that LDD's EULA forbids reverse-engineering but "except to the extent that this restriction is expressly prohibited by law". And indeed (according to wikipedia's article on reverse-engineering) both US and EU laws explicitely "allows reverse engineering for the purposes of interoperability". I've been able to reverse engineer the assets.lif archive file format and the .g binary file entries inside this archive (containing the geometry definition of the bricks). I have also prototyped a very simple .lxf 3d viewer that uses assets.lif content in order to render LDD models on screen. To which extend do you think that I can share the results of this work with the community?

I experienced the same issue with part 32013, as shown below. It cannot be attached to a simple 1x2 brick.