Eurobricks Knights
  • Content Count

  • Joined

  • Last visited

Everything posted by M2m

  1. Recently I created an couple of custom decals and while doing so I made some interesting discoveries in LDD. 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).
  2. I finished a Proof-of-Concept. That means a couple of things are working. But quite allot of things still to-do: LDD and Blender have different axis, Flex parts are floating around, correct grouping of subparts (g, g1, g2, .... files), materials, textures, testing on macOS Anyway this is the state so far:
  3. Yeah I'm pretty much on the same page with you. LDD is still the best tool for building in my opinion. I switched my render workflow to import my LDD builds into Mecabricks and then use it's Blender Plugin for rendering. Mecabricks has amazing materials :)
  4. Thats a nice change. You might also create a pull request in github. I'm not working on the blender plugin or LDD as much currently as i did in the past. But I'm happy to see that its of use to some people :)
  5. I got Lego Digital Designer working on macOS with Apple Silicon (M1 Chip) You need to get UTM https://mac.getutm.app/ and follow this guide to get Windows 11 installed: https://docs.getutm.app/guides/windows/ Afterwards its essential you get the OpenCL™ and OpenGL® Compatibility Pack from the Microsoft Store (https://devblogs.microsoft.com/directx/announcing-the-opencl-and-opengl-compatibility-pack-for-windows-10-on-arm/ ). Otherwise LDD will look garbled and is unusable. Performance is really quite nice.
  6. I got this part working. The issue was that this parts .xml file has a comment and the plugin didn't parse xml comments correctly. Updated version here (and tested with Blender 3.4): https://raw.githubusercontent.com/sttng/ImportLDD/main/importldd.py You have to un-install the plugin 1st, afterwards restart blender, then install again. Hope this fixed the issue. Maybe you can send the LDD file so I can check ?
  7. Can we get this part: https://rebrickable.com/parts/1748/tile-round-1-x-2-half-circle/ I think it's quite a useful one.
  8. Are you on Windows or macOS or Linux ? In fact i don't maintain the plugin anymore. But I might check on your error.
  9. Assuming you use Windows: Assuming you use macOS
  10. To be more specific this one: https://www.brickowl.com/catalog/lego-minifigure-hat-36112-38401 The picture Brickowl themselves put there, seem to be digital. Anyone know, if and where to get it ? Any format (LDraw, LDD, etc) is fine.
  11. Well until I get a real 3D version the pictures aren't helping. I was just guessing that there might be a 3D file out there, based on the rendered pictures. But as the pictures are directly from TLG, only they have a 3D file currently. I'm not good enough / too lazy to create 3D model of this part myself. So basically not much I can do :(
  12. Thanks for the explanation and guiding me into the right direction. It makes sense, and I can even confirm it after some further investigation. You can still pull the graphics if you get the Element ID and use the link below. https://www.lego.com/cdn/product-assets/element.img.lod5photo.192x192/<ElementID>.jpg According to Rebrickable and BrickOwl this part has an Item No or Element ID of 6224507 (https://rebrickable.com/parts/38401/minifig-costume-mask-cat-bright-pink-nose-print/ / https://www.brickowl.com/catalog/lego-black-minifigure-hat-36112-38401). So to pull the graphics from TLG you can use these 2 links: https://www.lego.com/cdn/product-assets/element.img.lod5photo.192x192/6224507.jpg or https://www.lego.com/cdn/product-assets/element.img.lod4photo.192x192/6224507.jpg Mystery solved, but still now 3D version of the part ....
  13. Its not in Mecabricks - thats where I want to get it in ultimately. Interesting know that TLG seems to share the picture with Brickset. And yes for obvious reasons TLG has 3D data of all their parts. So its remains a mystery where the renders come from....
  14. Well I would wonder how Brickowl got the render of this part (from LEGO). I can't find this part on the LEGO Website (neither buy nor broken nor lost) and also I couldnt find a PDF Building Instruction for that minifig. So I indeed would wonder where they got it from - I doubt they get it from LEGO ? Would they ?
  15. I think round 1x1 pieces will likely also connect then, because of how collisions work.
  16. First of all thanks for the great tutorial ! Regarding Polygon welding in Blender: I think Blender only assumes 2 Polygons to be connected when these use the exact same vertices of an edge. Example in 2D. Lets say you have these 4 vertices: v1 (0,0) v2 (1,1) v3 (0,1) v4 (1,0) And these 2 polygons: p1 (v1,v2,v3) p2 (v1,v2, v4) Blender will only regard p2 and p2 connected at edge (v1, v2) because the exact same vertices are used. Now if we have the following setup: v1' (0,0) v2' (1,1) v3' (0,1) v4' (0,0) v5' (1,1) v6' (1,0) And these to polygons: p1' (v1',v2',v3') p2' (v4',v5', v6') Blender will not regard p1' and p2' being connected, because even so the edges defined by v1', v2' and v4', v5' are the same coordinates they are different vertices. You might try the "Merge by Distance" tool as part of the "Vertex" menu to merge vertices of a certain distance.
  17. Thanks Stephan for all the hard work !
  18. I finished a Python program that (re)creates a lif file from a folder structure. So basically you can first use LIFExtractor.py (by JrMasterModelBuilder) to extract db.lif, then add mods and new bricks and afterwards repack the modified db folder with this tool (LIFCreator.py). 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):
  19. You can continue to use LDD - thats what I do. It works on Windows 10 (and I guess 11) without issues. On macOS you are more in a pain (I am), because you can't upgrade your OS without loosing it. It does work with Wine however.
  20. I made some adjustments to the collisions of 49311 https://github.com/sttng/LDD-New-Parts/blob/main/Primitives/49311.xml I think this fixes the problem.
  21. I had a quick check at 49311, it works good for me. I surround it with 3001 2x4 Lego bricks and left a hole to fit 49311 in. Thats why I assume the door frame might be the culprit in your example above ?