I’ve been working on a LEGO database project for quite a while now, and I think it’s finally at a point where it would really benefit from some fresh eyes.

It’s called Buka Atlas. On the surface, it's pretty much similar to the other catalog pages. I did try to give it some unique features, though. 

It’s still evolving, but the core system is in place and fully usable. I’ve been testing it myself (a lot), but I’d really like to see how other people interact with it — especially people who enjoy digging into details.

Some features (like collections) are currently limited to registered users while I’m testing things, but most of the site is open to explore.

If anyone is interested in taking a look, clicking (or tapping) around, and sharing thoughts (bugs, confusing parts, or just general impressions), I’d really appreciate it.

I’m particularly curious about:

• navigation and usability
• search and filtering behavior
• anything that feels unclear or unintuitive
• edge cases or things that “don’t feel right”

Here’s the site: https://buka-atlas.com/

No pressure at all — even a quick browse is helpful 🙂

Thanks!

For my birthday last year, I built this website and sent it out as an invite for my friends:
https://brq.is/birthday

It was a pretty fun little Lego + web project and I thought some of you might find it interesting.

I actually built the four models referenced in the different site sections and ordered parts to build 5 of each that I sent to some of my closest friends as "physical" invites. Each "set" had a custom PAB minifigure styled after them and the figure was holding a 2x2 tile with a QR code I printed that linked to the instructions. I didn't get any photos of those before I sent them out, unfortunately.

Originally, I had planned on the bottom of the four models to lock together and reveal a QR code to the site, and the brq.is domain I bought to have a really short "brick sounding" domain for a URL shortener and QR code generator. I was working on some code to convert a QR code to an LDraw model that could be opened in stud.io. I also forgot about that project until now... I start a lot of projects 

I'm a fairly new member here on EB, but am quite active for some time on the Rebrickable Forum now, so I read about MOCView there and wanted to share it with you, as I really like the software.

This is a great tool, which places LDraw (and therefore Studio) models in a 3d scene and allows you to take pictures of it, record videos or walk through your build in minifig size.

The creator of this tool is both active on Steam, where you can chat with them in the comments of their updates as well as in the thread on the Rebrickable Forum, if you have any direct questions, etc. But you can also use this thread here to discuss this and/or ask questions, I will try my best to answer them.

For now, this is a Windows-only application, although it works via Proton (for Linux machines). However, you need to test, if you meet the minimum requirements to really use it. For me, it sadly only started, but than had so much lag and frequently crashed I couldn't really test it.

Hope, that I could share something cool,
Kind regards,
Luna (aka yqc)

Hi.

[Rules of the Topic]

Allowed Sets

• Set that has been officially released by LEGO and available for the purchase.
• Set whose Official Instructions has been released from TLG and are available in LEGO website.
  IMPORTANT NOTE: if building instructions or set's references are not easily available on common sources, please report that.
• The Set have to be constructed using official LEGO instructions and not interpreting preliminary or official images.
• The Set have to contain something you can build. Sets with scattered parts or single or few minifigures are not allowed.

Irregular Posts

• Important NOTE: Irregular entries (inserted in posts that don't respect the Topic's Rules) won't be indexed.
• When you fix an irregular post, inform the indexer, so that he can update the index database.

Good habits

• Avoid unnecessary posts inside this topic, if possible.
• Always use a new post to add new entry/entries. Don't add (or remove!) models to any existing post.
• If you think to build more sets in a short period of time, don't post them one by one but amass a bit of them and then post them together. Try to avoid to post more than one time in a single day.
• For any question/explanation/request/communication contact the indexer using private messages, when possible.

Use of images in the topic [Guide]

• Only images related to posted sets (and then lxf file) are allowed, as a preview.
• Only one image for each set is allowed.
• Don't quote images from other posts.
• Any other image can be inserted as text link.
• Images should be simple and clear: no "creative" images are allowed, but simple screenshots.
  Avoid compositions (more images in one), images with another image as background, animated images, 3D images, renderings with external software, image with custom added parts, etc...
• Try to place objects inside the image so that the image results compact (i.e. avoid internal large blank space if possible) but clear.
• Try to place the camera so that the set results well visible. Avoid flat framing but choose a good 3D angle.
• As images are for preview purpose only, should be not too big!
  Maximum size allowed is 512x512 pixels for big sets (such as castles, modular buildings, stations, large space ships, etc...).
  Use intermediate sizes (for example 448px, 384px, 320px, ...) for smaller models. The 256x256px size or lower is often good for small sets.
• Crop images completely removing horizontal and vertical blank stripes around the subject (zero-pixles margins).

Insert a model

• Report set's data and emphasize that in bold.
  Set's data include set Number, set official Name and set's Theme and subtheme if any.
  For example: 5988 - Pharaoh's Forbidden Ruins - Theme: Adventure
• If the set has more "configurations" (different models), please specify which one you are reproducing with LDD (Model A, Model B, etc...).
  NOTE: Alternate Versions (official different configurations for the same set) are counted as separate sets.
• If the set has been Re-Released with an identical or similar version, report the alternate Set ID(s).
• Report both the version of LDD and the brickset used to build the model.
• Insert a screenshot of your creation, in order to provide a preview. One screenshot for each set (see the rules about images above).
• Write an Error List, reporting if the model is complete or some element is missing or replaced (by a similar part, a brick assembly or any custom solution). Use part IDs to identify the bricks.
• Don't divide a single set in more than one post.
• Put a single set in a single .lxf file. You are encouraged to use LDD groups function to separate different elements in complex sets.
• LDD model should be similar to the original model as much as possible. Include minifigs, if any.
  Replace missing decorations with suitable ones, if possible.
  Modified models are welcome, but in different .lxf files, as an "extra".
  Every personalization (personal logos, additions, changes) makes a model a "Modified Model".
• and obviously... Share you lxf file! 

Update a set

• Update the post where you originally inserted the set.
• Report the update in the Upgrade Topic.
• Be care to follow the rules of the Upgrade Topic.

[Sets created by other users]

• If the set has been built by another user, contact him and ask him to update his entry. Provide some help, if you find a way to solve some issue.
• If contact model's builder is not possible or he don't want to update it, insert the updated model in a new post as if it is a new model, but specify it is an update and insert the link to the original model's post.
• Inform the indexer before posting.

Use of the new bricks from the custom LDD updates  [new!]

• A model without custom bricks is necessary to the entry to be accepted as regular.
• A model with custom bricks is allowed as an extra.
• You are encouraged to publish both the models for your entries.

Book or Request a set

• Refer to "Official Lego sets - Book, WIP, Requests" Topic.
• NOTE: you can ever choose to make an already made or booked set, if you want.

Besides

• You are encouraged to inform an LDD file maker if you notice an adjustable defect in his/her LDD file!
• If you notice something wrong in the index, please report it to the indexer.
• If you use custom pieces to replace missing bricks in LDD, please post it in the "LDD custom bricks" Topic!

• Read the rules before posting here.
• Only regular entries will be indexed.
• Allowed sets: instructions officially released, no spared parts. Report references if necessary.
  
  Insert a model
• General rules: don't split model in more posts, don't add or remove entries to an existing post, group entries.
  Don't add personalizations to the model (except in order to replace missing parts). Use Groups. Extra are allowed, as text links.
  Models containing custom parts are allowed ad extra only.
• Necessary content: Set's Data, Image, LXF File, Error List.
  - Set's data: Set's ID, Set's name, Theme/Subtheme, alternative model (Model A, B, ...), alternative Set IDs if any.
  - Image: one for each set, simple screenshots, PNG with Alpha channel, maximum size 512x (big sets), crop (zero-pixles margins), not scattered, no flat view.
  - LXF file: one for each entry, direct link, report LDD and brickset version.
  - Error List: missing bricks/decorations, replaced brick/decorations, brick made replacements.
• Various: minimal quotes, don't quote images, report errors. (index/other entries).

• Type the number, name and theme of the model (I prefer Brickset themes) at the top of your post.
  
• This topic only makes sense if you give a link to your model, so other people can download it
  
• Put a picture of the virtual model in your post.
  
• Say if there are errors, if there are, tell what the errors are.
  
• Not too big pictures, please follow the EuroBricks guidelines.
  
• One set in one file. So not one set in 2 files, or 2 sets in file.
  
• The set should be build using the original instructions.
  
• Exporting models from ldd is forbidden unless you have the permission from the original author. Pleas do check everything very, very carful (also the inside of the model), because the export is not very accurate.
  
• Models like Montly Mini Builds or Club models are allowed.
  

• MLcad
  
• SR3D Builder
  
• Leocad
  
• Bricksmith
  
• BrickDraw 3D
  
• LDCad
  

DM me on FB messenger for more information.

- Endless fun.! Turn Unreal Engine into the most powerful Lego CAD ever!

- Digital Lego: build / edit / animate / physics / play - directly Unreal Engine 

- Auto-apply brick materials: colors, solid, transparent, metallic, chrome, rubber, grow in the dark etc. with master material feature support. You can fine tune only the master material - in example changing the opacity value of the transparent material master, then all the transparent bricks in the scene change at once. 

- Auto-apply stickers and print decals. 

-It took less than 5 minutes to import a typical Lego model. 

LEGO set 77050 - Nooks Cranny and Rosie's House, modeled in LDraw using LDCad, rendered with Studio. by Philo Hurbain

Studio models:
hotdog stand by dinorage
Chemistry lab with lots of gear and tools by Amarok365
Modular Central Train Station with arched roof by timpustelni

"Boat "Josefa"" (https://skfb.ly/6GCS6) by Alexandre González Rivas is licensed under Creative Commons Attribution-NonCommercial (http://creativecommons.org/licenses/by-nc/4.0/).

"Old Camera Bag .::RAWscan::." (https://skfb.ly/on7ZC) by Andrea Spognetta (Spogna) is licensed under Creative Commons Attribution-NonCommercial (http://creativecommons.org/licenses/by-nc/4.0/).

"Freeman Alley Dataset" (https://skfb.ly/oqKps) by matousekfoto is licensed under Creative Commons Attribution (http://creativecommons.org/licenses/by/4.0/).

"Boat "Josefa"" (https://skfb.ly/6GCS6) by Alexandre González Rivas is licensed under Creative Commons Attribution-NonCommercial (http://creativecommons.org/licenses/by-nc/4.0/).

"Old Camera Bag .::RAWscan::." (https://skfb.ly/on7ZC) by Andrea Spognetta (Spogna) is licensed under Creative Commons Attribution-NonCommercial (http://creativecommons.org/licenses/by-nc/4.0/).

"Freeman Alley Dataset" (https://skfb.ly/oqKps) by matousekfoto is licensed under Creative Commons Attribution (http://creativecommons.org/licenses/by/4.0/).

Here's some background: There is a website called "archipelago", that allows you to host randomizers for games. So, for example, you'd put in a pokémon game and a mario game, and while playing the pokémon game, you can find mario items that will then go to the mario game.
Some people have made a lego version, where you can "receive" the lego bricks you need to build your set, and "send" other games items for pages of instruction. However, they're not perfect, and had to be done manually. I think I can fix this.

However, to do so, I would need an API that, when given a set ID, gives the pieces needed for each step. AKA, step 1 needs a red stud and a brown 2x4, step 2 needs a black technic rod... (it could also just be the piece's ID, I don't mind). I am wondering if such a thing exists.
 

Thank you for your attention.

Ok, let's do this.

Inspired by @M2m thread I've started wrting a 3D Studio Max script that allows importing, editing and exporting LDD brick geometry and their XML data. They are rough, some geometry data is unknown (this doesn't have any visible or noticable impact so far) but it works and here's the result (click for bigger pictures):

Fixed connectivity issue of 90 deg tube (pretty popular piece for 2018/2019 technic sets):

Custom 3x5x2 panel that I saw in one of the Chinese custom (not copied from Lego) models:

I was curious how my MOC would look like with more realistic, narrow tires so I shrinked Unimog tire to fit on 42029 rim. Dimensions: 81,6 x 30:

For the tractor enthusiasts - how could a Class tire look like on an Arcos rim - also that Chinese model. Dimensions: 64,2 x 20 (I've made is slighty bigger than original tire):

Moved some parts around and fixed default orientation of some of technic panels:

Caveats:
- Many Duplo parts are missing here (and are not available in LDraw library anyway)
- Studio doesn't provide specific connectivity for Duplo, so I had to make do with simple stud or axle connexions.
- Compatibility with regular LEGO is limited (you can place bricks over Duplo, but Duplo on bricks doesn't position correctly and generate collisions).
- Some parts create unwanted collisions, eg. Duplo wheel on axle. Problem is that Studio part designer generate collision data automatically, I have no control on this. Turn collision off when this happens.

Hi Guys,

I can't manage to turn the roof over and put it on. Does anyone know how to do it?

Have a good Day!

I would like to build the Srh Tower out of Lego.
I have already developed the basic framework in Bricklink Studio, but I have encountered problems with the roof. It has a horizontal as well as a vertical curve, which means that, to my knowledge, it cannot be built using the Snot technique. Despite searching extensively, I have not been able to find any other construction technique that would allow me to build this double curve. I am really desperate and would be very grateful for your help!

P.S. Here are a few pictures of the roof:

Srh Tower front

Srh tower back

Srh tower diagonally above

Srh tower side

P.S. I can also post pictures of my current progress from Bricklink Studio.

Best regards!

Which one would you recommend? 

Lego Studio 2.0 is a blurry on my 4K screen. Otherwise it seems to be easy enough to use.

Bricklink Stud.io?
LDD?
LeoCAD?
LDCad? - Seems difficult to use.
MLCad?
Mecabricks.com? - Seems to get stuck loading pieces. 

I'm trying to design custom minifigure tools. I need a model of a minifigure  that is as accurate to real life as possible  when it comes to the  dimensions.

Does anyone have a recommendation? 

Right know I'm wondering about the angle of the hands. In the LDRAW library it seems to say 14.5°. Is that correct? (https://library.ldraw.org/parts/7189)

But I've struggled to find a way in Studio to accurately do this outside of "build to Lego Step X" and then swap to MOD instructions, back to Lego for Steps Y-Z, back to MOD, etc. This works fine in some cases, but feels like a hack job in others with a lot of PDF editing and clarifications needed (e.g. disassemble section A, but modules B and C intact, then build Lego steps G - J, etc.).

Does anyone have any tips for a newbie to make this style of instructions in an easy, clear way?

Thanks for the help and advice!

The issue comes at step 361, where the assembly that will eventually be the bottom of the main thrusters clips on to the chassis.  There are three parts to that assembly--a center section that clips via hinge onto the chassis, and two "wings" that are hinged to the center section, and are supported on either end by resting on a slope brick protruding from the chassis.  However, I cannot figure out an angle--either between the assembly and the chassis, or between the wing and the center section, or a combination thereof--that avoids collisions.  If I have the wing of

the assembly resting on the slope brick as intended, the wing section collides with the bar arm below; if I have it angled up enough that it doesn't collide with that, it collides with some of the chassis bricks above.  There is also a range of angles where it collides above and below.

Right now, in the screenshot, you'll notice that I don't have the wing resting on the slope brick as intended.  If I do change the hinge angle to where it does rest, that solves the intersection with the upper brick on the chassis, but you'll also notice that the dome on the underside of the wing is already intersecting with the arm bar below; that problem will still exist if I hinge it farther down.

I have a couple of questions:

1. The part I'm calling an "arm bar" that's below this assembly is this piece.  Stud.Io calls it #30359b,  "Bar 1x8 with Brick 1x2 Curved Top End (Axle Holder Inside Small End)", Brickset calls it #60572, "Brick W. Shaft 1X8X1".  I've never actually encountered one in real life--is it supposed to flex somewhat?  If so, that may be the issue.

2. If that's not the problem (or not the whole problem), is there a solution to this that I'm missing, or is it just one of those things where Stud.Io has unrealistic expectations?

Also, if needed (and permitted) I can link to a higher-resolution version of the screenshot, I had to scale it down to fit the file size limit and it may be difficult to make out the details (I'm hardly a good judge of that since I already know what I'm looking for and where).

Hope this is in the right section. I have recently started getting serious with using Bricklink Studio and using the instruction maker. What I'm struggling with is how to edit the PDF afterwards. More specifically how to split the PDF into smaller sections (part 1, part 2 etc). I know there are some fantastic videos on Youtube that cover using many of the features in Studio but have not found anything on this so anything that is offered is greatly appreciated 

I'm about to start learning Adobe Illustrator to create my designs, but I just wanted to see whether anyone would particularly recommend any other programs, like AutoCAD perhaps?

Any advice greatly appreciated.

Many Thanks!

LDD Manager allows you to analyze and manage your LDD files, and to upload Wanted List to BrickLink. There’s also a bunch of other features, like a possibility to search and find all the bricks in LDD Extended Mode, and generate custom Brick Palettes.

UPDATE December 2013: The latest version is now 1.25 with support for LDD 4.3.8. If you have a previous version, you should download the new version. NOTE, installing a new version will remove your previously imported LDD-files, but hopefully it's not too much work to import them again.

UPDATE 2017: LDD Manager is no longer available for download. Due to time reasons, I couldn't maintain it anymore.

Note that this software requires MS Access 2003 or higher. If you don’t have it installed on your PC, you need to download and install the free Access 2003 or 2010 runtime first.

Download LDD Manager and help file here.

Download free Access 2010 runtime here if you don't have Access allready installed

Looking forward to your comments.

- The first time build must make same steps as the building instruction

- hide all steps

- double click / ctrl click / Delete steps in order, to get parts for every steps

As I was looking for an outlet to share a little building project that is ongoing, I found my way to Eurobricks. Funny thing: I seemed to have made an account already, way back in 2014, but it seems that I forgot all about it. So I'm happy that I'm back.... :-). This topic will be about a CADA rebuild in LEGO. This is the first time I have bought a CADA box (or even something else than LEGO), and I'm very much looking forward to see if I like the experience. Everything is still sealed in the box at the moment. Every time I have been exposed to LEGO-like (rip-off) brands by accident, it has been a disappointment, mostly in terms of quality, how it looks and feels. I suspect (and hope) that CADA could be the exception, based upon general positive reviews and overall impression of their professional approach. I chose the digital LEGO subforum to post because at first I used BrickStudio to do the rebuild. But I then decided to go for the real life bricks, so the topic will cross over at some moment. 

But first a bit of background: When LEGO started to bring out detailed cars in their Icons line, in normal brick style and with only a smattering of Technic stuff, I was immediately sold and started buying them. I think it started with the T2 Volkswagen Camper van for me, and I also liked the subsequent Beetle, but the more recent ones like the F40, Mustang and Corvette really stoked the fire. The only one that I found a bit underwhelming in how it mirrored the real life car was the James Bond DB5, and I still had a blast building it.

I must confess I'm not even a big car fan in real life. It was back when I was in elementary school that I had a lot of Matchbox cars, to the point that every box that looked remotely the same size and dimensions elicited a spark inside. Now that I'm an adult, cars just need to work reliably and carry stuff. For me though it's definitely the genius building techniques used by the Icons designers that really get me going. The tricks they employ to get certain angles, curves and joints seem endless to me. I can easily stop mid-build and marvel at a particular NPU or nifty construction, and show it around proudly to semi-interested family members :-). 

As is probably the case with a lot of builders of the Icon series car, you secretly hope that they will build your favorite car next. While the Beetle was a close call, my all-time nostalgia car is the 2 CV Citroen. Particular the one in the color red, and with round headlights. This was our first family car that I have memories of, I think as a 4-5 year old kid. I distinctly remember the backseats were just a thin layer of skai, stretched over a metal framework (no safety belts). Very uncomfortable and it also got very hot in the summer. The gear lever was angled horizontally in the dashboard instead of vertically next to the driver. There was a rubber roof that you could roll open to change the 2CV in a cheap convertible. And it had such a distinct sound....it reminded you more of a whining outboard motor of a boat than a car engine. The top speed on the dashboard showed 120 kilometers per hour, but I have never seen one driven faster than 100.....and sitting in it sounded and felt like you were doing 200....

Next up: the CADA box arrives! 

I have this project I have to do in LDD (cannot use LDraw or Stud.io for this one, don't ask me why...)

But, I am sure a certain piece should fit, but LDD won't let me because it thinks it does not fit.

Tnx

i switched to linux, i have heard studio doesnt work under linux (and that has been my previous experience too with other distros), but now it totally works. I use kubuntu 25.04 with wine, the current 64 bit windows version installed just fine, and everything works.

Hope this helps some of you guys wanting to go away from microsoft or apple.

- Support "Mecabricks Advanced" real brick round edges / bevels feature (optional: "Mecabricks Advanced" available on Mecabricks website cost 25USD)
- Support Mecabricks all 165 brick colors
- Adjustable brick imperfections: scratches, fingerprints all at once or any specific brick or color.
- Solution for decoration on a transparent or chrome brick, etc.
- One million+ bricks count tested. Smooth and high FPS game play with a 10GB VRAM graphic card.
- Quick and easy to turns any brick or any brick color to light up 
- Easy customize brick materials and color, adjust only the master material to make its instance materials be changed at once

It is tested on macOS 10.14.6 and Windows 10. It worked with LDD 4.3.11, bluerender 0.6 (that is the new added bricks where loaded and rendered) and of course I also tested it with JrMasterModelBuilders LIFExtractor.py (packing with this tool, unpacking with JrMasterModelBuilders LIFExtractor and vice versa). Still I don't guarantee any functionality and suggest you to keep backups (especially of the original db.lif).

WARNING: You accept full responsibility of using it yourself !

https://github.com/sttng/LIF-Creator

How to:

./LIFCreator.py /Users/your_user_name/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/db

On Windows type the following into the command-line

LIFCreator.exe "C:\Users\<YOUR USER>\AppData\Roaming\LEGO Company\LEGO Digital Designer\db"

Below a bluerender test (the leaves are a new custom part):

6541 - Intercoastal Seaport - by roamingstudio
6542 - Load Launch Seaport - by roamingstudio 

I would contact "roamingstudio" myself and ask him to to either restore the link or simply send the 2 files to me, but for some stupid reason Eurobricks won't let me send ANY message's so I'm really screwed here.  I am hoping someone can and will help me, please.  With that said, I do have a generous amount of LDD sets, so if you want one and cannot get it on Eurobricks, reply to this and let me know.

I was using Stud.io when it froze and crashed, and after it crashed I saw that my file was a .io.backup file. I tried opening it in Stud.io but the parts never load (gets stuck at 0 / 1 when parsing). After I tried opening it the file shows as a .io file now, but under file type it still says "BACKUP File" when I view it in File Explorer. This is a rather large model so I really hope it can still be recovered. Has anyone else experienced something similar and managed to get their file to work again? Thanks!

I've been playing with luminous materials in Studio and have tried to replicate the kind of basic global illumination style HDRI lighting I used to aim for in Cinema 4D. Below is the result, the first render is my lighting with Intensity in Studio's Render menu set to zero and for comparison below that is the standard Mechanic lighting with Intensity 2.

I think that by getting rid of the default illumination and effectively turning off the HDR sky in Studio the model looks less overexposed, especially the upward facing surfaces which instantly lose the bright, sterile white reflection. The darker model means the highlights stand out a lot more, and since studs and edges are reflective there are plenty of nice highlights to look at! I also added some illumination in the scene, the white parts around the edge of the landing pad and in the upright light are luminous soft white and there is a bit of glow coming from the engines.

I rendered these with transparent background and added a coloured backdrop and some noise in Photoshop. It's not a realistic image by any means but I think it'd a decent improvement, it's certainly helped my renders blend in with my photos on Instagram profile. Here's the Studio file of the lighting arrangement (_HDRI Lights by Ron_McPhatty.io) if you'd like to to give it a try, remember to turn the "Illumination" option in the Render window down to "0" before clicking render.

To achieve the lighting effect I arranged a heap of large plate pieces into rings, angled them at downwards to aim at the subject positioned in the centre and positioned a few luminous panel spotlights directly above to give extra shadows and highlights. Other lights can be toggled on and off by Hiding/Showing the parts groups, so it's possible to light objects slightly differently for example all light from one side to give the impression of a bright planet. Here's how it all looks in Studio...

Here's a few more examples with different models. I hope the idea is useful, any suggestions to help me improve the set up would be great, and feel free to use and abuse the lighting set up if you like it and I'd love to see other models rendered in this style.

It has been a long time since Lego Digital Designer (LDD) has been updated with new parts. For a long time the exact format of the code from the LDD parts was not exactly understood. Now, a few members of the Eurobricks community cracked the code and are able to create parts in the format LDD uses. This post shall list these new parts and contains a link to a zip/rar file with those new parts.


Rules

Off course we would all like to have as many new parts as soon as possible. That doesn't necessarily guarantee the highest quality standard. Therefor we have compiled some rules. Only parts that adhere to these rules will be added to the parts pack(s).

• Parts may only come from open sources. That means that LDraw parts are allowed, but that Mecabricks parts are strictly forbidden;
• A part must always have connectivity and boundary boxes;
• A part may include collision boxes but this is not necessary for approval.

Reaching the LDD part database

First things first. How to access the current parts of LDD? We need to know that before we can add new parts.

Windows

1. Download LDD LIF Extractor for 32- or 64-bit systems. The LIF file contains the LDD parts. The LIF Extractor can be found here: LINK;
2. Unzip the LIF Extractor zip file;
3. Navigate to: Users/[UserName]/AppData/Roaming/LEGO Company/LEGO Digital Designer. The "AppData" folder could be hidden; if so: activate "Show hidden files";
4. Here you'll find a file named "db.lif". Drag that file onto LIFExtractor.exe (it doesn't matter where LIFExtractor.exe is located: downloads folder, desktop or anywhere else, just drag db.lif onto the exe file);
5. You'll now find a folder named "db" and one named "Palettes". Rename the original "db.lif" into something else (i.e. "xxdb.lif"), this is your parts back-up file!
   
   You'll find the following in the "db" folder:
   
   Folders

• "Assemblies": This folder contains the *.lxfml files for the assemblies.
• "Decorations": This folder contains all decorations.
• "MainGroupDividers": This folder contains the images of the part groups.
• " MaterialNames": This folder contains English and German names for the included color. Advise: do not open this file in a normal text editor, it will mess up the file, making it unusable!
• "Primitives": This folder contains the technical data for the parts. Navigate further to "LOD0", this folder contains the 3D models for the parts.
  
  Loose files
• "CurrentMaterials": This file list all current colors that are in LDD.
• "DecorationMapping": This file contains which decoration belongs to which parts.
• "info": Regular info about LDD.
• "Materials": This file contains all color RGB values.
• "pes": This file says something about friction which might have something to do with the old exploding animation.
  
  You'll find the following in the "Palettes" folder:
• Multiple *.lif files.
• Extract LDD.lif and LDDExtended.lif in the same way you extracted the db.lif file.
• Now you have two folders: LDD and LDDExtended. These folders contain *.paxml files: text files which create ready-to-use multi-colored part palettes.
• Here you add the 2020NewPreColoredParts folder. This gives you access to all new pre-colored multi-colored and printed new parts.
   

iOS/Mac

1. Download LIF-Extractor from JrMasterModelBuilder. It can be found here: LINK.
2. Go to folder: 

   /Users/myusername/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/

3. Extract the db.lif using JrMasterModelBuilder's LIF-Extractor.py Python script by using Terminal:

   python LIFExtractor.py /Users/myusername/Library/Application\ Support/LEGO\ Company/LEGO\ Digital\ Designer/\db.lif

4. This will create a "db" subfolder containing the extracted contents of the db.lif file. Rename "db.lif" into something else (i.e. "xxdb.lif"), this is your parts back-up file!
5. Enter the folder, go to "Primitives". This folder contains the technical data for the parts. Navigate further to "LOD0", this folder contains the 3D models for the parts.
6. For information about the folder structure, see "Windows" above.

Accessing the new parts

Now for the real exciting part: adding parts to LDD. Lego Digital Designer should be closed for this.

1. Download the update parts pack (*.rar file) to the location of the "db" folder from the latest post below;
2. Unpack the folder;
3. If asked if you want to replace files, click "Yes to all". Now you will have the latest parts and the newest part geometries.

Available Now! Mecabrick2UE advanced- Mecabricks Unreal Engine 5 tools

Price 20, Please DM via FB messenger "Nachapon Lego"

- Support "Mecabricks Advanced" real brick round edges / bevels feature (optional: "Mecabricks Advanced" available on Mecabricks website cost 25USD)
- Support Mecabricks all 165 brick colors
- Adjustable brick imperfections: scratches, fingerprints all in once or any specific brick or color.
- Solution for decoration on a transparent or chrome brick, etc.
- One million+ bricks tested. Smooth and high FPS game play with a 10GB VRAM graphic card.
- Quick and easy to turns any brick or any brick color to light up
- Easy customize brick materials and color, adjust only the master material to make its instance material be changed at once

Photo showing my painted and gloss varnished hubcaps on the Burger Truck (a rather excellent set with, gasp, no stickers! Set ID is 60404):

Thingiverse link so you can download the Bricklink Studio file: https://www.thingiverse.com/thing:7116321

Download: latest version

On Windows 32 bits: download  and replace the one in “C:\Program Files\LEGO Company\LEGO Digital Designer\”

On Windows 64 bits: download  and replace the one in “C:\Program Files (x86)\LEGO Company\LEGO Digital Designer\”

On Mac: download and replace the one in the “Contents\Resources\” folder in the app (open “Applications” in Finder, right click on the “LEGO Digital Designer” package and select the “Show Package Contents” option to explore the pakage folders). (Thanks manglegrat!)

This file is also used and distributed with these tools:

• lxf2ldr  C++/Qt version (both CLI and GUI), more options but needs to be compiled
• lxf2ldr.html  HTML/JS version, works everywhere!

If you have other modifications or additions, post them here or send me a personal message and I’ll include them to the benefit of all.

If you need a part, feel free to ask here and I’ll try to add it (provided it exists in LDraw and LDD).

History and Contents

• It’s based upon gallaghersart’s latest version (see this thread).
• It includes the modifications shutterfreak published in his thread.
• It uses some of the LDraw unofficial parts (mainly for new parts in LDD Brick version 2075).
• It includes some name corrections (because LDraw renamed or moved some parts, added new variants, etc.).
• I tried to more accurately convert the colors (now mainly according to Ryan Howerter’s conversion table). It’s not easy because all sources (Swooshable, Mecabricks, Ryan) don’t agree, and there are holes and overlaps. But as these differences, holes, and overlaps occur for rare colors or colors that aren’t available in LDD, it should be okay.
• In a megalomaniacal way, all the entries I have modified have an “SLS” at the end of their heading comments. New entries have an “SLS” at the front of the comments.
  So it’s easy to know when to blame me.
  As of 2016-09-16 and the big overhaul, I assume all the errors.

Know Limitations

• As of LDD 4.3.9, flex parts (hoses) are not exported anymore (even unflexed).
• Minifig arms and hands are not connected in LDraw. I don’t know whose geometry is off (both?) but the shapes differ a lot. At least, hands are correctly connected to whatever they clip and arms are correctly placed in their sockets and somewhat wrap around the hands’s stems.
• Some variants are not recognized by LDD (e.g. clips, or tiles with/without groove, etc.) In those cases, I prefer to use the most recent variant in LDraw as it generally is easier to find and cheaper.
• Sometimes, several LDD parts correspond to a unique LDraw part. Sometimes, the transformation is accurate for one variant but not for another. For example, the Flag 2 x 2 is known to LDD as 2335, 11055, and 60779, but LDraw only has the 2335 variant. 2335 and 60779 use the same transformation but 11055 is vertically offset. I preferred to badly convert 11055 to 2335 rather than not convert it at all or badly convert 2335 and 60779.
• ldraw.xml is used both ways (LDD to/from LDraw). It’s not something I do frequently (too many resulting collisions) so it’s not well tested. One problem I can see is that, when several LDD parts correspond to a unique LDraw part, the conversion that’s listed last is the one that will be used. The reverse (first written is the one used) is true for assemblies that use the same subparts, in the same quantity (like electric cables).
• A lot of LDraw parts are simply wrong. Almost all the parts that combine System (studs and anti-studs) and Technic (pins and axles, and their holes) are wrong in that they assume the technic holes are at the same height than side studs (on the picture below, the circles are concentric).
  
  LDD assumes the holes are 0.2 mm (0.5 LDU) higher.
  In ABS, the holes are 0.12 mm (0.375 LDU) higher (dixit Jamie Berard in his famous presentation). In order to limit the number and magnitude of errors, LDD is considered to be right.

How to write a new transformation for a part in ldraw.xml

What?

ldraw.xml is an XML file that defines how LDD can export to (or import from) LDraw files.

It does so by defining a match between the part’s IDs and how to rotate and translate the part from one geometry to the other.

Matches are defined by “Brick” XML elements.

For example, this one says to LDD that the Brick 1x1 that it knows as 3005 is also known to LDraw as 3005:

<Brick ldraw="3005.dat" lego="3005" />

(Note the “.dat” in the ldraw ID.)

Matches are not needed if the part IDs are the same: the transformation element is sufficient for LDD to know the part exists. (So the example above is useless  )

Rotations and translations are defined by “Transformation” XML elements.

This one says to LDD that the Brick 1x1 just needs to be moved up:

<Transformation ldraw="3005.dat" tx="0" ty="-.96" tz="0" ax="1" ay="0" az="0" angle="0" />

The translation (tx, ty, and tz) is in centimeters (0.8 cm is the width of a brick, 0.96 cm its height).

The rotation is given by its axis (the line passing through and ), and its angle in radians.

And all the coordinates are in the direct (“riht-handed”), Y points up, coordinates system of LDD.

The transformation explains what should be done to import from LDraw besides changing the axes (LDD’s Y is up and XYZ is a direct basis, LDraw’s Y is down and XYZ is an indirect basis; so changing the axes only means changing the sign of Y).

So, in an LDD to LDraw point of view, the transformation is reversed: it says what happens to a part if you don’t do anything to its coordinates besides changing the sign of Y. In other words, the opposite transformation has to be applied to the LDD coordinates of the part in order to get the LDraw coordinates (with Y reversed).

Why?

Each part has an orientation (which way up? which way left?) and a center, point of origin, or reference point (we’ll use “reference point” from now on).

But LDD and LDraw don’t always agree.

To know the orientation and reference point in LDraw, I find LeoCAD the easiest tool: just select the part and its axes are drawn (X red, Y green, Z blue), starting at its reference point. Okay, LeoCAD’s «X, Y, Z» is LDraw’s «X, -Z, Y» but what’s another little change of basis? 

Sometimes, their disagreement is trivial.

For example, for the simple 1x1 brick (3005), both LDD and LDraw agree: the stud is on top and the reference point is on the vertical line going through the center of the stud. But they differ for the height at which the reference point should be: LDD says it’s at the base of the brick, LDraw at its top (but at the base of the stud).

(On every picture, X will be red, Y green, and Z blue.)

So the transformation for that part is straightforward: if the LDraw part is imported as is, with only Y reversed, it will end up 0.96 cm (the height of the brick) higher than it should. So we have to lower it by 0.96 cm:

<Transformation ldraw="3005.dat" tx="0" ty="-.96" tz="0" ax="1" ay="0" az="0" angle="0" />

Sometimes, their disagreement is more profound and the transformation is therefore more complicated.

For example, for the musket (Minifig Gun Musket 2561), LDD puts the reference point in the handle and “up” means the handle is vertical but LDraw puts the reference point in the barrel and “up” means the barrel is vertical. Even more, the stock is on the wrong side, so X and Z are different too.

With an identity transformation, the part is rotated by an eighth of a turn (X to Y) (π/4) around the Z axis to put the barrel vertical, and then by a quarter turn (X to Z) (-π/2) around the Y axis. After that, it has been translated up and horizontally.

After calculations (see below), we’ll end up with this transformation:

<Transformation ldraw="2561.dat" tx="0" ty="-1.72" tz="0.336" ax="-0.3574067443365933" ay="-0.8628562094610169" az="0.3574067443365933" angle="1.7177715174584016"/>

How?

So, how do we find the right values to have the correct transformations?

What’s the ID? Having the right part

Check the ID of the part in LDD.

Check the ID of the part in LDraw.

Beware of variants, LDraw uses a letter suffix (a, b, c…) where LDD totally changes the ID or keeps the same ID for new variants.

Don’t hesitate to look on BrickLink for the part ID: BrickLink keeps a list of alternate IDs (when the same part has several IDs) and links to variants and notes.

If the IDs are the same. Nothing to do.

If the IDs differ. We add a Brick element:

<Brick ldraw="123a.dat" lego="456" />

Don’t forget the “.dat”!

That was the easy part.

Which way is up? Finding the rotation axis and angle

We start in LDD.

Up is Y, or Y is up.

X and Z are a bit harder to see on the LDD scene unless you use LDD’s developper mode (which has the LDD axes drawn at «0,0,0» as red X, green Y, and blue Z lines). Or, if you’re sure you didn’t move the camera in a brand new model/file, X is pointing bottom right, and Z bottom left.

We place our part among other parts that we know will be correctly converted (like 1x1 plates, or harpoons ) to have references. Using different colors greatly helps!

We export to LDraw…

… and look at the results:

We decompose the transformation in multiple simple rotations, around the X, Y, or Z axis.

• If it has been turned around X, a quarter turn from Y to Z is a positive π/2 angle.
• If it has been turned around Z, a quarter turn from X to Y is a positive π/2 angle.
• If it has been turned around Y, a quarter turn from Z to X is a positive π/2 angle.

To make it short, it’s a direct (right-handed) basis.

<transformation tx="0" ty="0 tz="0" ax="0" ay="1" az="0 angle="0"/>

You can try each simple rotation one by one to be sure of their angles (especially their signs ).

Beware, combining rotations change their axes (e.g. turning around first X then Y is equivalent to turning around first Y then Z). So if you check that the Y rotation is okay, then the X rotation, don’t forget to combine them as Y then Z.

For the musket, we need two rotations: an eighth of a turn (π/4, 45°) around the Z (blue) axis that puts the barrel vertical, and then a quarter turn (-π/2, -90°) around the Y (green) axis. Or we can first make the quarter turn (-π/2, -90°) around the Y (green) axis, and then an eighth of a turn (π/4, 45°) around the X (red) axis.

Remember, “import”-wise, we’re trying to find what should happen to the part in the LDD scene to be like the LDraw one, with the LDD axes (the harpoons ).

My head is turning. Combining rotations

If more than one simple rotation is needed, we have to combine them.

For that, we’ll use quaternions.

Eh come back! That’s not that difficult!

A quaternion q can be written as q = a + b.i + c.j + d.k, where i² = j² = k² = i.j.k = -1 (so i.j = k = -j.i, j.k = i = -k.j, k.i = j = -i.k).

a is the real part, b.i + c.j + d.k is the imaginary part.

A rotation by the angle angle around the axis «ax, ay, az» is the quaternion q = cos(angle/2) + sin(angle/2).(ax.i + ay.j + az.k)

Do note the 1/2 factor on the angle!

To combine two rotations, we just multiply their quaternions and apply the rules above to end up with a a + b.i + c.j + d.k form (or, more accurately, a C + S.(ax.i + ay.j + az.k) form, where C and S are cosine and sine of the same angle and ax² + ay² + az² = 1 ).

If we rotate first by q and then by p, the result is the rotation by p.q.

Note the order: q then p is p.q. Multiplication is not commutative with quaternions: if you do it the wrong way, you’ll end up with the correct values but the wrong signs.

There’re lots of fun to have with quaternions and rotations as quaternions. But what is said here is sufficient for our purposes.

An example:

Most of the times, we do π/2 rotations (quarter turns, 90°).

angle = π/2 therefore cos(angle/2) = sin(angle/2) = cos(π/4) = sin(π/4) = √2/2;

So, for a “horizontal” quarter turn (yaw, around Y): q = √2/2 + √2/2.j (as j/Y is the “vertical” axis).

Let’s combine it with a half turn (π, 180°) around the X axis (IOW, upside-down):

cos(π/2) = 0, sin(π/2) = 1, so p = 0 + i

p.q = (0 + i) . (√2/2 + √2/2 j) = √2/2 i + √2/2 i.j = 0 + √2/2 ( i + k )

Now, let’s get the resulting angle:

The real part of p.q, 0, is the cosine of angle/2.

0 is also the cosine of ±π/2 (±90°).

Therefore, the resulting angle is π (180°).

Now the axis, «ax, ay, az»:

It’s the √2/2( i + k) imaginary part. That’s the vector «√2/2, 0, √2/2».

We need to remove the sin(angle/2) factor. That’s easy as the sine of π/2 is 1.

So our axis is «ax = √2/2, ay = 0, az = √2/2».

Written in ldraw.xml:

ax="0.707…" ay="0" az="0.707…" angle="3.1415…"

Another one, a quarter turn around Y and then around X:

q = √2/2 + √2/2 j = √2/2 (1 + j)

p = √2/2 + √2/2 i = √2/2 (1 + i)

p.q = 1/2 (1 + i) (1 + j) = 1/2 + 1/2 (i + j + k)

We rewrite it as p.q = 1/2 + √3/2 (√⅓ i + √⅓ j + √⅓ k) to have a unit vector (ax² + ay² + az² = 1) in the parenthesis and to clarify the cosine and sine: 1/2 and √3/2.

They are the sine and cosine of π/3 (60°).

Therefore, the resulting angle is 2π/3 (120°).

In ldraw.xml:

ax="0.577…" ay="0.577…" az="0.577…" angle="2.094…"

Back to our musket:

An eighth of a turn (π/4, 45°) around the Z axis that puts the barrel vertical: q = cos(π/8) + sin(π/8).i = C + S.k

Then a quarter turn (-π/2, -90°) around the Y axis: p = cos(-π/4) + sin(-π/4).j = √2/2 (1 - j)

p.q = √2/2.(1 - j)(C + S.k) = √2/2.(C - S.j.k - C.j + S.k) = √2/2.C + (-√2/2.S.i - √2/2.C.j + √2/2.S.k)

Wow! Hum, okay. So √2/2.cos(-π/8) is the cosine of half our angle. Get the calculator out…

angle/2 = Acos(√2/2.cos(-π/8)) = 0.8589

Our angle is 1.7178.

We “remove” the sine of angle/2 from our vector, so that p.q = cos(angle/2) + sin(angle/2).(ax.i + ay.j + az.k):

ax = -√2/2.sin(-π/8) / sin(0.8589) = -0.3574

ay = -√2/2.cos(-π/8) / sin(0.8589) = -0.8629

az = √2/2.sin(-π/8) / sin(0.8589) = 0.3574

As an exercise, you can verify that ax² + ay² + az² = 1. So we did it right!

Et voilà:

ax="-0.3574067443365933" ay="-0.8628562094610169" az="0.3574067443365933" angle="1.7177715174584016"

One step to the left. Getting the translation right

Now that the part is correctly oriented, it may need to be moved.

The translation is in centimeters (cm). 20 LDU = 0.8 cm.

Values are often multiples of 0.4 (half a stud) for tx and tz and multiples of 0.32 (height of a plate) for ty.

Other, finer, tunings are often in multiples of 0.008.

If the rotation is complex, all bets are off 

In LDD, we try to place the part so that its LDraw up axis ends up up in the scene, and we try to align its LDraw X and Z axes with X and Z of the scene (at least, that it is not rotated by a weird angle).

That way, moving the part along its axes is also moving the part along the scene’s axes. It will be easier for getting the translation right.

For our musket, that means the barrel up. (I didn’t align the X and Z axes here because, yeah, I’m a warrior, I don’t need that. Besides, you’ll see what happens because of that. )

Again, I find it easier in LeoCAD: the key bindings, the coordinates clearly shown in the status bar, etc. The thing is, LeoCAD uses a direct Z up basis. So if you move «dx, dy, dz» in LeoCAD, you’re moving «dx, -dz, dy» in LDD (and vice versa). Confusing? Noooh. 

Anyway, choose your own poison but beware of its little quirks.

To help fine tuning, using transparent colors greatly helps, especially for clip-bar connections.

Now, we note the coordinates of our part in our LDraw editor and move it so that it ends up the way it should. We look how much we moved it. That’s it! Just convert it to cm (= LDU × 0.8 / 20) and we have our translation. Well, mostly, the signs are wrong. Remember: the transformation is what should happen to the LDD part to end up like the LDraw part, we just did the opposite and moved the LDraw part to be like the LDD one.

Besides the signs, if you didn’t correctly align the axes, you’ll have to find which is which 

For our musket, we need to go up and sligthly to the “left” (from bottom right to upper left when your LDraw view is oriented as a new LDD file, as are all the screenshots here). That means negative dy and dx. But as the part is not aligned on X and Z (but still not badly rotated), the negative dx becomes a positive dz.

Et voilà!

<Transformation ldraw="2561.dat" tx="0" ty="-1.72" tz="0.336" ax="-0.3574067443365933" ay="-0.8628562094610169" az="0.3574067443365933" angle="1.7177715174584016"/>

(So, okay. I had to try first tx then tz, both negative and positive, before I found the right one. But I didn’t want to have to remake the pictures! There: I’m not a warrior, I’m just lazy.)

Hi everyone,

I’m part of a small team based in Paris working on an idea we’d love to get your feedback on — especially from experienced builders like many of you here on Eurobricks.

We’re developing a tool that turns any personal photo (a pet, person, object, etc.) into a custom buildable construction set. The concept is simple:

1. You upload a photo on the platform.

2. It generates a 3D model based on the image.

3. Once approved, we send you all the bricks and custom instructions to build it yourself — kind of like a personal MOC kit.

💡 The idea came from our love for creative building and the desire to make more emotionally meaningful sets — like building your dog, your childhood car, or even a gift for a friend based on a memory.

We’re not trying to sell anything here — just genuinely curious what this community thinks about:

• The idea itself
• Whether you’d use something like this
• What you’d expect in terms of quality, control over the design, or brick type/scale

We’d be super grateful for any thoughts, suggestions, or even critical feedback — we want to make something truly useful and fun for the community.

Thanks a lot in advance!

Dimitri

Available now! Studio2UE digital Lego tool. Turn Unreal Engine into the most powerful and most freedom Lego sandbox game / game maker / realtime renderer ever! UE5 supports VR, AR, ios, android etc. 

It is evolving the ways people play with digital Lego bricks! Most powerful and freedom ever! The tool is the most powerful /easy / fast / correct / massive / beautiful / all formats digital Lego model importer for Unreal Engine ever! It turns any digital Lego model into UE game asset or map level in a very short time (3 minutes typically). DM me on FB for information or watch 100+ Lego Unreal Engine videos and tutorials on my YouTube channel.

Studio2UE fast and easy import tool. It can import not only Bricklink Studio io  model, but also Ldraw ldr and LDD lxf model. Mecabricks model import tool coming soon.

DM me on FB messenger for more information. There are hundred more Lego Unreal Engine demo and tutorial videos in Nachapon Lego YouTube channel (link in first comment).

- Endless fun! Turn Unreal Engine into the most powerful Lego CAD ever!

- Digital Lego: build / edit / animate / physics / play - directly in Unreal Engine.

- Auto-apply brick materials: colors, solid, transparent, metallic, chrome, rubber, grow in the dark etc. with master material feature support. You can fine tune only the master material - in example changing the opacity value of the transparent material master, then all the transparent bricks in the scene change at once. 

- Auto-apply stickers and print decals. 

-It took less than 3 minutes to import a typical Lego model.

Hey, all, I have a summer project working with my university to create a 2D, postcard-esque design of a neutron star or black hole. We are leaning more towards a neutron star design. The concept of the project is to use two or more sets in circulation and kitbash them together into such a design. I have some working drafts, but I thought some input and opinions from the Lego community could be helpful. I had a draft I was satisfied with, but then I realized that it uses parts from retired sets (sets 21340 and 41961). The first two images are that draft and the third and fourth are reference images. I've thought about using The Great Wave set (31208) and using each 16x16 square to create a little design, but the dark blue doesn't show up well on the black and looks weird on the "light nougat." The rough draft of that is the fifth image. I was also thinking of using the Creative Space Planets set (11037), but I couldn't think of a satisfying way to emulate the "astrophysical jets." Those are the sixth image. The last image is some theory-crafting with the exotic peacock and exotic parrot sets (21340 & 41961).

In general, I was just curious if you all had a suggestion on design choice or perhaps suggested Lego sets. The general plan is to try to keep the price at or under 150 dollars.

Lego LDD Counter-Strike map MOD build by me (15,000 pcs, it took many days to build, reference using half-life level editor called hammer, about ten years ago)

Unreal Engine 5 sample game modified and lego model was imported by me, This mini-game took me only half an hour to make (modify)

I just tested with a gtx1650 notebook PC, it runs smooth

Missing / Unused Decals of LDD 4.3.11

LDD 4.3.11 contains a couple of decals / decorations which are however not used or referenced in the DecorationMapping.xml file. This are 72 of the overall 1992 decorations:

601500.png
601501.png
601502.png
601503.png
601504.png
601506.png
601507.png
601508.png
601509.png
601510.png
601511.png
601512.png
601513.png
601514.png
602875.png
602876.png
603721.png
606301.png
606303.png
606304.png
606305.png
610479.png
610480.png
610481.png
610482.png
610970.png
610971.png
610972.png
610973.png
610974.png
610975.png
610976.png
610977.png
610978.png
610979.png
610980.png
611803.png
611804.png
611805.png
611806.png
611808.png
611811.png
616065.png
64352.png
64353.png
64354.png
64355.png
64356.png
64357.png
64358.png
64359.png
64360.png
64361.png
64362.png
64363.png
64364.png
64366.png
73157.png
84759.png
84760.png
84761.png
84762.png
84763.png
84764.png
84765.png
84766.png
84767.png
84770.png
94271.png
94272.png
94874.png
99594.png

There are also decorations for the faces for the Lego Friends Minifig heads but the Geometries do not have the relevant data to be able to be textured.

On the other hand DecorationMapping.xml also references some decals which are however not included in LDD 4.3.11. This are 45 of the 2086 mappings:

decoID	designID
601676	3070
601680	3070
601681	3070
601683	3070
601684	3070
601685	3070
601688	3070
601689	3070
601690	3070
601691	3070
601692	3070
601693	3070
601694	3070
601695	3070
601696	3070
601697	3070
601698	3070
601699	3070
601700	3070
601705	3070
601709	3070
601721	3070
601722	3070
601725	3070
601727	3070
601733	3070
601734	3070
601735	3070
601736	3070
601737	3070
601738	3070
601739	3070
601740	3070
601741	3070
601742	3070
601743	3070
601744	3070
601745	3070
601746	3070
625352	25114
625423	28716
625585	25113
626388	28716
626390	25740
95114	27059

Most missing decorations are for part 3070 'Flat Tile 1x1', but also for the Hammerhead Shark Hat, the 'normal' Shark Hat, part 25740 (which isn't included in LDD) and part 27059 (also not included, but this seems to be an Alias for part 90541 "STOCKING CAP", which interestingly has all necessary code to be decoratable in the primitive xml file as well as in the .g, g1 files).

Unrelated sidenote: DecorationsMapping.xml was introduced after LDD 4.0.2. The earliest version I found to include this files was LDD 4.1.7. Before the decal information was included in the Primitive xml for each part I guess.

DecorationMapping.xml is included in definitions.lif in earlier LDD versions (starting from LDD 2.0 up until LDD 4.0.2).

Mon projet serait un montage que je ne pourrais pas me permettre de faire de suite car trop onéreux pour pouvoir acheter les pièces immédiatement, mais je tiens à avoir un rendu visuel BrickLinck, une notice de montage et un tableur listing des pièces pour prévoir les achats

"Hello, I'm looking for a BrickLinck designer who would be looking for a (very large) project and would do it for free.

My project would be an assembly that I couldn't afford to do right away because it would be too expensive to purchase the parts immediately. However, I'd like to have a BrickLinck visual rendering, assembly instructions, and a parts list spreadsheet to plan purchases."

If you guys still have access to LDD, I'd like to get a screenshot of all the parts in each category in extended. Thanks in advance!

These are my questions : 
- What's the easiest workflow for importing my scene Inside blender? Inside Studio, which file format to save as, and do i need an addon for opening that file in Blender?
- how good are the textures once imported in Blender (does the model keep any texture at all?) I guess they won't come with the optional scratches and slight discolorations that make the renders Inside Studio look realistic?
- Also, any idea where I can get a free rigged minifigure to add to my scene and start some animations? (i Don't need one that bends knees or elbows, or can do textured facial expressions... just the basic minifigure moves)

Thanks in advance for any help you can provide :)