-
Posts
1,354 -
Joined
-
Last visited
Content Type
Profiles
Forums
Gallery
Everything posted by SylvainLS
-
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Hi, a couple errors found in the GitHub parts: 65401 / 65402: wrong connections (or wrong 3D model) (again!), you can put a pin in the axle hole / you can’t put a pin in the pin hole. 65633: still missing a file on GitHub and LDD goes kaboom. -
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
Did you keep Palettes\LDDExtended.lif after extracting it? LDD reads ALL the files and folders in Palettes, and depending on the order it reads them (seems pretty random), it reads the lif after the extracted directory (the one with the modified MaterialSelector.xml), thus reverting the changes. TL;DR: move the .lif you extracted elsewhere. -
Sorting Custom Parts in Stud.io
SylvainLS replied to Vilhelm22's topic in Digital LEGO: Tools, Techniques, and Projects
Unfortunately, no, for the moment there’s no way to have categories in the Custom parts palette. -
Setting up a x2 process for multiples
SylvainLS replied to monkypaws's topic in Digital LEGO: Tools, Techniques, and Projects
In Studio, you need to use the two copies of the submodel in the same step to get the x2, otherwise the instructions are repeated (like in official LEGO instructions, actually). If the copies are too far away from each other in the model and you can’t find a good / satisfying angle to show how they should connect, one solution is to add pages and images. You may create those images with another version of your model (= 2 .io files, one principal with the two copies used in the same step and one where they are used in different steps and from which you can extract just the pages/pictures where they are inserted in the model). -
[KEY TOPIC] LDD New Parts
SylvainLS replied to Stephan's topic in Digital LEGO: Tools, Techniques, and Projects
Hi, 1. The bricks are only available in LDD Extended. To be available in ‘normal’ LDD requires more work, starting with knowing which parts are available in which colours. 2. If you have red ? in the palette, then you’re missing files. Either you didn’t install the custom parts correctly or you used LDD 4.3.12. LDD 4.3.12 is crap, it comes with an outdated parts library. Some of the official parts are customized here (more decors, bugs fixes…) and only the modified files are distributed here. So your LDD may see the parts because of these few files but it’s missing the 3D models for these parts. Desinstall (and scrub) LDD and install the 4.3.11. There’s a few posts on the forum with more info. -
LDD ghost groups
SylvainLS replied to drugwash's topic in Digital LEGO: Tools, Techniques, and Projects
It’s Studio, no dot, now. Zooming in/out is done with the mousewheel. The only newer version of LDD is 4.3.11 and it didn’t change much to 4.3.10 in terms of feature. Forget the rezipping, it just adds more possibilities of screwing up. I shouldn’t have mentioned it. Now, the modified .lxfml should load… unless you have deleted things that shouldn’t have been deleted, or left things that should have been deleted. The only solution is to be sure of what you do when you edit the XML. Some smart editor (Notepad++) could help you there. Well, one simple solution is to remove all the groups: leave only <GroupSystems> <GroupSystem> </GroupSystem> </GroupSystems> and delete everything else about groups. -
LDD ghost groups
SylvainLS replied to drugwash's topic in Digital LEGO: Tools, Techniques, and Projects
When you delete a group in LDD, its place in the list of groups is taken by the last group in the list. When a group contains groups, you need to delete the super group, then the children… grand childeren… and it appears endless. But if you don’t move your mouse from the X, you can validate the dialog with the keyboard: click-return-click-return…. Anyway, an LXF file is just a ZIP file that you can decompress. Inside is an LXFML file which is XML (so text) that you can edit with a text editor, like Notepad++ (not Wordpad or Word!). Once edited, you can recreate an LXF file (reZIP IMAGE100.LXFML & IMAGE100.PNG together into a .zip and rename as .lxf), or simply load the LXFML in LDD. Make backups before playing around…. Now, if you insist on continuing using LDD, you may at least consider going to version 4.3.11 / 2670… (many new parts, well, ‘new’ 4+ years ago) and even maybe install the custom parts from this thread (need 4.3.11): -
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
35189 is a custom part, added mid June 2020. -
Update 2022-05-05 Added: 15504 / 15504.dat Minifig Tail Cat 15627 / 15627.dat Panel 1 x 6 x 6 with 4 x 2 Window Cutout 15864 / 15864c01.dat Minifig Helmet Large Square with Side Extensions 18395 / 18395.dat Flame 5L Curved with Bar 0.5L and Triangular Base 20592 / 20592.dat Minifig Hair Mid-Length Flipped Ends with Cat Ears 28145 / 28145.dat Minifig Hair Wavy Parted with Large Thick Glasses 88618 / 88618c01.dat Animal Ostrich 99250 / 99250.dat Minifig Neckwear Ribbon with Medal Rematched: 25893 / 25893a.dat Plate 1 x 1 Round with Bar Handle on Short Stem Importable: 25893.dat / 25893 ~Plate 1 x 1 Round with Horizontal Handle Below (Obsolete) Added Custom part: 49492 / 49492.dat Minifig Shepperd Crook Rematched Custom part: 22969 / 22969a.dat Wheel 56 x 46 Technic Racing Importable as Custom part: 22969.dat / 22969 ~Wheel 56 x 46 Technic Racing (Obsolete) md5sum: 4c874725e68af4438beab65c409a0fc1
- 327 replies
-
- conversion
- ldraw
-
(and 1 more)
Tagged with:
-
They will be looking at making 494 a “real” colour for Studio, so all the parts should work after that’s done. Not sure when that will be released though… because Studio is a bit late regarding colours (missing the last ones, like Neon/Vibrant Yellow and a few Satin/Opal ones) and the last LDraw updates and there’s a long list of bugs and suggestions….
-
The part on the left is with 383. The part on the right is the stock one, with 494, and it indeed renders White. My previous tests were too quick and there must have been a play of light that made me think is was metallic. That’s why I added coloured parts around in this render 494 is not “known” as a colour by Studio (yet), so it doesn’t work.
-
Hi, First, the way you say it, it seems you think replacing 16/24 with 383 would make the colour “adjustable.” It’s the other way around. 16/24 are the special “I’m not a colour, please replace me” colours. Lines (subparts or primitives) in those special colours get their colours from the file that use them. So, for BL 2909c03, Studio uses 2909c03.dat as a 3D model. 2909c03.dat uses 74741-f1.dat in colour 16 (so it’s paintable in Studio) which uses the two plastic subpart in colour 16 (so they are paintable in Studio) and u9409-f1.dat in colour 494 (Electric_Contact_Alloy, a fixed colour). If you replace 16/24 in u9409-f1.dat, you fix the colour of the spring and it’s not paintable / “adjustable.” Now, for your prolem, I think it’s simply that 494 shows very much like White in Studio. But if you render the part, it correctly shows as metallic. If you replace 494 with 383, it’s the same. But if you use a “simpler” colour, like Red (4), it will show correctly in Studio. The problem is in Studio, it doesn’t show these metallic colours very distinctly (or not at all), not with the part or the colour. I’ll talk to the devs about it. Now, a few other remarks on what you were trying to do: First, I wouldn’t replace the 16 & 24 colours in the spring but the 494 in 74741-f1.dat: instead of many changes, you just make one. Besides, changing 24 (special edge colour) is a bad idea (better to remove the lines entirely as they become useless if they are the same colour as the rest of the part). Also, I’d start with 74741-f1.dat, to have the whole part. If you edit the spring, you only have the spring and must use the other subparts in your build. (One thing is sure: the stock part won’t use your modified spring.) The simplest procedure is to copy 74741-f1.dat under another name, edit it to replace 494 by 383, import it in PartDesigner, export it to Studio. But, again, that won’t solve your problem! In Studio, the spring will still show white but it will render as chromed.
-
Looking for digital version of a part
SylvainLS replied to M2m's topic in Digital LEGO: Tools, Techniques, and Projects
The main image on BO is a photo but the others are renders. If you check on Brickset for design 38401, you find one (the best one). Brickset gets its images directly from TLG, so that’s a render from TLG. TLG certainly does have 3D models of all their parts nowadays. Now, for the others renders on BO, maybe they are older versions that are not on Brickset anymore but if they are from elsewhere and not from TLG, well, we’ve already established they are not from LDRaw, so she only other possibility for them is Mecabricks (which I doubt because of the quality, or lack thereof). (And it’s Studio now, no dot. The dot was dropped with version 2 ) -
Looking for digital version of a part
SylvainLS replied to M2m's topic in Digital LEGO: Tools, Techniques, and Projects
Undoubtedly a render from LEGO. So, ask LEGO for a 3D model? -
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
No problem… it just means you’re too young to have had to write your own code when you wanted to write images (ah, Ye olden times of BMP and TGA) -
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
There’s “8bits” and then there’s “8bits.” One value is the total size of a pixel (bit depth), the other is the size of a channel. You can have PNG files in 1, 2, 4, 8 or 16 bits per channel and 1, 2, 3 or 4 channels (indexed, greyscale, grey+alpha, RGB, RGBA). “Bit depth” = bits per channel multiplied by number of channels. “Bit depth 32” = 4 channels (RGBA) with 8 bits each. “Bit depth 8” = either indexed (there’s a palette of 256 colours, and each pixel has a colour) or greyscale (256 levels of grey). Generally, “8/16bits” means 8/16 bits channels and RGB(A) channels (so a bit depth of 32 or 64). -
Update 2022-03-11 Corrected typos. Corrected: 30377 / 30377.dat Minifig Mechanical Arm with Clips Parallel 65578 / 65578.dat Plate 1 x 1 Round with Angled Bar 93609 / 93609.dat Arm Skeleton with Horizontal Clip Bent 56.31 Rematched: 3049 / 3049d.dat Slope Brick 45 1 x 2 Double / Inverted with Bottom Stud Holder 10498 / 90641.dat Technic Constraction Shell 3L Flat Importable: 4092a.dat / 4025 Train Bogie Plate with Long Pin 6069.dat / 48933 Wedge 4 x 4 Triple 10498.dat / 10498 =Technic Constraction Shell 3L Flat 10830.dat / 10830 Minifig Tool Magnifying Glass with Thick Frame and Lens 16175.dat / 16175 Minifig Construction Helmet with Hair Short 18835.dat / 18835 ~Minifig Hair Mid-Length Straight with Crown 23999.dat / 23999 Boat Hull Floating 40 x 12 25126.dat / 25126 Minifig Baby Body 30483.dat / 30483 Minifig Head Wookiee with Bandolier 47545.dat / 47545 Minifig Head Rodian without Pattern 53914.dat / 30388 Hinge Brick 1 x 6 Locking Double, Two Finger End with 7 Teeth 54671.dat / 30365 Hinge Brick 1 x 2 Locking with Dual Finger On End, 7 Teeth 54672.dat / 30540 Hinge Brick 1 x 2 Locking with Dual Finger on End Horizontal, 7 Teeth 73092.dat / 73092 ~_Magnet Cylindrical in Casing Black (Obsolete) 87561.dat / 87561 Block 6 x 4 x 1 with Handles and Minifig Pattern 90391p01.dat / 90391 Minifig Pike / Spear Elaborate With Flat Metallic Head md5sum: c23e5c8ac2930b04d87567172c0ec74a
- 327 replies
-
- conversion
- ldraw
-
(and 1 more)
Tagged with:
-
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
If it was missing bricks, then it was crappy 4.3.12. -
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
33909, 26604 & 32952 are in Official LDD (since, respectively, Jan 2018, Feb 2017 & Jan 2018). Check that you have LDD 4.3.11 with Brick version 2670 (menu Help | About). If not, look earlier in this thread for one of the dozen times we explained 4.3.12 is crap and how to install the correct version. -
Update 2022-03-03 Added Part: 11575 / 11575.dat Animal Poodle Corrected Part: 32476 / 32476.dat Constraction Limb 4 x 7 Bent 45 with Ball Joint and Opposing Axleholes Added Custom Parts: 27965 / 27965.dat Cable Flexible 22L with 2 Bar Connectors 30680 / 3068a.dat Tile 2 x 2 without Groove 44553 / 44553.dat Minifig Hat Tall Hat with Small Brim and Pin 45275 / 45275.dat Technic Shield 5 x 5 with Circular Grinder 53500 / 53500.dat Electric Constraction Eyes 4.5 x 2 x 1.5 Light-Up 65834 / 65834p01.dat Wheel 14 x 35 with 4 Spokes with Integral Medium Azure Tyre 69778 / 69778.dat Technic Gear 20 Tooth 69779 / 69779.dat Technic Gear 20 Tooth 71720 / 71720.dat Wheel 24 x 107 Motorcycle with 6 Spokes 71721 / 71721.dat Tyre 27/ 48 x 107 Motorcycle with Racing Tread 71722 / 71722.dat Tyre 37/ 38 x 107 Motorcycle with Racing Tread 75544 / 75544.dat Technic Windscreen 11 x 11 Motorcycle with Angled Pegholes 76110 / 76110.dat Technic Competition Arrow (Complete) 77813 / 77813.dat Tile 1 x 1 Round with Groove and Handle 80796 / 80796.dat Brick 1 x 2 x 1.667 with Studs on 2 Opposite Sides 86876 / 86876.dat Brick 1 x 2 with Centred Stud on Long Side Added Custom Assembly: 43097 / 43097-f1.dat Technic Linear Actuator 8 x 2 x 2 Type 2 (Contracted) 62233 / 62233-f1.dat Constraction Ball Cannon (needs part 60932c01.dat that can’t be submitted to LDraw) Corrected Custom Part: 27448 / 27448.dat Turntable Flat Base 2 x 2 md5usm: 4b30c99ccf63f6c4d7ad5d5bb25415ce
- 327 replies
-
- conversion
- ldraw
-
(and 1 more)
Tagged with:
-
Custom LDD bricks and fixes
SylvainLS replied to Equilibrium's topic in Digital LEGO: Tools, Techniques, and Projects
27448: Hmm, the transformation in ldraw.xml was committed on 2020-05-20. I don’t have the history for 27448.xml in my LDD prior to 2020-12-14 (when I installed on a new computer…) but the bounding box hasn’t changed since. So if something happened on my computer, it’s between these dates. On GitHub, the first version of the file is from 2020-08-03. It’s the same as my December version. So it’s either an old error or a change I missed between May and August. Well, I’ll change the faulty transformation…. With the difference between the two, I meant to examplify that two people could disagree on what is “right” and therefore do things differently, even in the case of criteria. They would both still be “right” because there will always be holes (new unforeseen parts) or ambiguities in the criteria. (It sure would simplify ldraw.xml if both LDraww and LDD agreed but it was not the point.) That doesn’t mean there should be no criteria, but having very detailled ones and being very strict about them is not really useful in the context of LDD (it is more useful for LDraw).