SylvainLS

Yep, I meant “Stephan’s official releases of custom parts”

AFAIK, the Friends pieces are not currently official. By that I mean not on GitHub: I don’t download the .rar everytime but they generally match. Stephan should release them this week but has not updated the links and GitHub yet (they are ilsted in the last post in the topic). And because he sent me a link so I can check them (mainly for ldraw.xml), I know some bits are missing in his .rar. So maybe he made a mistake and “leaked” them somehow earlier and you caught it. The u-joint should be complete in official releases too. Anyway, we were also/mainly answering to badchriss: they have 4 broken categories and one category has the steering wheel as icon, a panel category, and other differences that strongly smell LDD 4.3.12 and brick version 777 to me.

I don’t know why they didn’t start with 4.3.11 :| I’m about sure the third digit isn’t just linked to the brick version / release: there’ve been modifications to the programme in 4.3.10 (or 9? I’ve forgotten) so that flex parts don’t export anymore. And there was the brick version 2248.1 for 4.3.10 that didn’t change the version.

Brick version 777 didn’t come with 4.3.5 too? My guess: they just wanted to repackage LDD, used 4.3.5 as a base but didn’t care to check it wouldn’t update its bricks.

Er, no. The new pieces are correctly categorized and go in existing categories. Those “unknown” categories are here because, either: You’re missing / didn’t copy assembly files. Assemblies are composed of subparts that are like “normal” parts, except they don’t have a “normal” category. If the assembly file is missing, the parts are then useable as standalone parts but are not correctly categorised. You have installed LDD 4.3.12, which comes with a very outdated brick library (version 777) and doesn’t update to the latest (2670, you can check that in Help|About). Brick version 777 doesn’t have the same categories as 2670, so the newer categories are not found and don’t have an icon. You did something wrong within your db folder. I’d go with n°2.

@mdogg The “problem” is that XML files are text files while .g are binaries. So, when you follow the links and select a .g file on the repository, GitHub doesn’t show its contents, and you have a nice “Download” button to download the file. But when you follow the links and select a .xml file on the repository, GitHub shows its contents. But at the same location for the “Download” button for .g files, there’s two buttons, “Raw” and “Blame.” The button you want is “Raw.” And it can be used two ways: If you click it, the file will be shown in your browser, you’ll then need to save the file (right-click then “Save as…”; or Ctrl-S). If you right-click it, select “Save as….” Another way is to download the whole repository as a Zip file: on the first page, there’s a green “Code” drop-down button with a “Download ZIP” option. You can then pick up the files you want from the downloaded ZIP file.

If you have a db directory instead of a db.lif, then you have already extracted the lif and moved or deleted it….

I think (I’m not a Windows user) that the path depends on Windows’ version. On my Wine, it’s in “C:/users/ME/Application Data.” There’s also a “Local Settings” directory that some applications use (I believe it’s a link to AppData/something on a real Windows). Anyway, it’s MS (pronounced “a mess”), so look for a “Lego Company” folder in your user directory, somewhere. Oh, by the way, the directory doesn’t exist until you start LDD at least once.

If you’re talking about the list I made a few months ago, here’s an updated list (550 parts instead of 650 ).

Yep, I agree with M2m. You could get inspiration from other projects, like the Linux kernel or Debian: have a period when you accept new parts, and then a freeze period when only fixes are accepted, then release and repeat. The “rolling release” where you release what’s ready doesn’t work because you’re only you and can’t work on both accepting new parts and preparing the others for release, so you end up with a “never release” where the release is postponed each time a new part is available but needs integration and fixes. You need to put your foot down on a freeze date, and that goes for yourself too

Update 2020-11-20 Added: 11216 / 11216.dat Bar Grill 13 X 17 with Studs and Tips 15362 / 15362.dat Claw 6.4L with Axle 24636 / 24636.dat Minifig Headdress with Widow's Peak and Two Large Curved Segmented Horns 27934 / 27934.dat Plate 1 x 2 with Extrusion with Hexagonal Decorations 28946 / 28946.dat Minifig Head Powerpuff Girls Blossom with Orange Hair and Red Bowtie 28948 / 28948.dat Minifig Head Powerpuff Girls Bubbles with Yellow Hair 28949 / 28949.dat Minifig Head Powerpuff Girls Buttercup with Black Hair 43889 / 43889.dat Animal Tail Joint with Short Pin Connector 89519 / 89519.dat Bar Grill 9 X 13 with Studs and Tips Rematched: 30191 / 30191.dat Bar Flexible H-shaped with Holders Importable: 30191-f1.dat / 30191 Bar Flexible H-shaped with Holders 89513.dat / 89519 Door 1 x 8 x 12 Castle Gate Portcullis Added Custom Parts: 2712 / 2712.dat Technic Rotor 3 Blade 2719 / 2719.dat Technic Plate 1 x 10 with Holes 2737 / 2737.dat Technic Steering Arm Tall 2792 / 2792.dat Technic Steering Top 2900 / 2900.dat Technic Flex-System Pin Hole Connector 2901 / 2901.dat Technic Flex-System Ball Connector 2908 / 2908.dat Technic Helicopter Rotor Holder 2989 / 2989.dat Technic Brick 1 x 4 with Holes and Bumper Holder 2991 / 2991.dat Technic Brick 1 x 2 Double Angled with Bumper Holder 2997 / 2997.dat Tyre 34/ 38 x 56 ZR 2998 / 2998.dat Wheel Rim 32 x 56 with Peghole and 6 Spokes with Pegholes 3651 / 3651.dat Technic Connector (Pin/Bush) with 2 Studs 4261 / 4261.dat Technic Steering Arm 4262 / 4262.dat Technic Plate 1 x 6 with Holes 4273 / 4273b.dat Technic Connector Toggle Joint Toothed 4442 / 4442.dat Technic Plate 1 x 8 with Holes 4504 / 4504.dat Hinge Plate 1 x 6 with 2 and 3 Fingers On Ends 4727 / 4727.dat Plant Flower 2 x 2 Leaves 4745 / 4745.dat Propellor 2 Blade 5.5 Diameter 65401 / 6540b.dat Technic Steering Arm Large with Peghole 65402 / 6540a.dat Technic Steering Arm Large with Axlehole 6543 / 6543.dat Technic Plate 4 x 6 with 4 Position Gear Shift Gate 6549 / 6549.dat Technic 4 Speed Shift Lever 28125 / 28125.dat Minifig Headdress Bald Head High 65509 / 65509.dat Plate 2 x 4 with Groove with 2 Studs 426502 / 6577.dat Technic Bush 1/2 Type 2 Added Custom Assemblies: 6282 / 6282c01.dat Electric RC Race Buggy Steering Unit (Complete) (exports with duplicated axle and level, doesn’t import) 6642 / 6642.dat Technic Flex-System Pin Connector Double Closed (doesn’t import, exports with one misplaced lid) 6643 / 6643.dat Technic Flex-System Pin Connector Single Closed 6644 / 6644.dat Technic Flex-System Ball Connector Closed 9244 / 3712c01.dat Technic Universal Joint (Complete Assembly Shortcut) 32181c01 / 76320-f1.dat Technic Shock Absorber 10L Damped (Extended) 41894c01 / 41894c01.dat Technic Steering Arm With 2 Ball Joints (Complete) Importable as Custom Parts: 4265b.dat / 426502 ~Moved to 6577 4273.dat / 4273 ~Moved to 4273b 4273a.dat / 4273 Technic Connector Toggle Joint Toothed With No Slots md5sum: e18435d056431a28cf7e297d72408d32

In the meantime: On GitHub, there’s a green button titled “Code” with a down arrow on the left and a small triangle on the right. Click it, you can download a ZIP file.

You need to be in LDD Extended mode (menu View | New themes | Extended). You can go back and forth between the modes, though, even when LDD was still updated, the last parts updates were only available in Extended, so “normal” mode has been pretty useless for some time now. LDD saves the last mode used in the LXF, so it starts in the “right” mode when you open a file. The big difference is in how colours/painting work.

Hi, It’s not clear to me: You’re first talking about exporting from LDD, so the parts have to be in LDD. Then you’re saying they aren’t in LDD. If you can’t find them in LDD with the other wings, then check in Help | About that you have LDD 4.3.11 with a brick version 2670. If you’ve brick version 777, then you’ve installed 4.3.12. See one of the numerous posts about this crap (like this last one).

According to LDraw: left = 92244, right = 92245.

For the pumpkin: 20693 is the shell, 20694 is the stem, and 20695 is the whole part. LDD numbers are often wrong this way, using a subpart number instead of the number for the whole part. I think “legacy” doesn’t mean “old” as in “they were modified” but as in “they were available in the old LDD.”

As they have ends (and Outer Cables don’t (?)), maybe you could look into how parts like the flexible axles work?

Direct link (The link to a comment is the “Posted blah” text on top.)

FYI, I prepared their conversion to LSynth and their difference with the other flexible parts is that I had to ignore 3 bones on each end. I generally ignore only 1: the one that is replaced by the special end part. That is, with other parts: b₁b₂b₃…b₃b₂b₁ becomes eb₂b₃…b₃b₂e, with your cables: b₁b₂b₃b₄…b₄b₃b₂b₁ becomes eb₄…b₄e. Otherwise, the last bones are too close to each others and LSynth makes “edgehogs” with bits of cables every which way. So, in short, I believe you should make your ends a bit longer and put fewer bones, especially at the ends

If what’s explained in this thread is not sufficient, see this other thread. But if this one is already too complicated, forget it….

Eh! You’re right, it’s familiar. I’m sure I’ve seen it somewhere. But where? (They could have used a more recent version though….) More seriously, the LXFML format have changed through the years. I don’t have any knowledge/example prior 2014 but there’s a schema (here and on lugnet I think?) that actually doesn’t describe the format used by LDD 4. 5.6 must be the format “in-house LDD” uses now.

@Kuramapika1 I won’t expand on LDD to LDraw conversion, I already did in the thread about ldraw.xml and several times in this thread. The short of it is: one part in LDD = one part in LDraw (and, for assemblies, we are talking about the subparts: one subpart in LDD = one subpart in LDraw), anything else and you can’t convert (or, at best, can’t import). And if you stick to 1 LDD part = 1 LDraw part, why not keep the IDs? But another, more important, reason to stick to real IDs is for the users to find the parts. And that’s valid even for subparts: they are searchable in LDD and the user may not know the assembly’s ID but only one of the subparts’ (the one ID visible on the real part they have in hand, for instance). Frankly, I see no reasons to confuse things by highjacking an ID when you can make any ID you want in LDD that help keeps things tidy and easy for everyone. As for 2698c01/2699c01, I haven’t been clear: What existed in LDraw were all the subparts and a complete figure (named 2698c01.dat). Most of the new LDD parts match the LDraw parts (foot, hand, arm-section, leg-sections, head) but the body/torso of the figure is only one part whereas, in LDraw, there was no shortcut part for the body/torso of the figure and it’s three parts (2698.dat, 2699.dat, and 2710.dat). Therefore I made and submitted to LDraw a part, 2699c01.dat, to match the LDD body/torso. The LDD part is 2698. 2698.dat is the main torso part (2699.dat is a connector and 2710.dat is the lower body), so 2698c01.dat would have been a better match but it was already used, hence why I named it 2699c01.dat. Some of you justly call the new LDD parts 123401 when they match the LDraw part 1234c01.dat. Some drop the 01. It’s okay, the important bit for search purposes is 1234. Therefore, strictly speaking, the part 2698 in LDD shouldn’t have been called 2698 because it doesn’t match 2698.dat and it doesn’t match 2698c01.dat, it matches a 2698+2699+2710 part that didn’t exist when you made it. Now that that body/torso part exists and is named 2699c01.dat, still strictly speaking (I’m not asking for a change), the LDD part should be 269901 or 2699. If I’d used a Technic figure in my builds, I’d have made and submitted that body/torso part before, or someone else could have done it before, because it’s a mechanical assembly: it’s a useful part to have that correctly place subparts that don’t move/rotate relatively to each other. IOW, if you want to pose the figure, it’s handy that these three subparts stay together, without having three parts to handle. So it’s just luck/timing that makes 2699 “not used” in LDD. (I also made and submitted a 2701c01.dat to combine 2701.dat and 2705.dat, the arm connectors, for the same reasons. But here, there’s no conflict.) So, please, don’t highjack IDs, there’s plenty of other possibilities.

Please, don’t “highjack” existing numbers. 2699 may not be used now but 2698 is, and is converted to 2699c01.dat that I created to combine 2698, 2699 and 2710 (the body) because 2698c01 already exists and is the complete figure. It’s already complicated enough. I don’t know what’s the problem with 6642 but it’s composed of 6642k01.dat and 6644k02.dat, so try to use ID that allow easy matching, like 664201. If you need other numbers, try to keep them close (like 664202…). But remember: if you make two different LDD parts for the same LDraw part, your part or assembly won’t be importable.

Update 2020-10-30 Added: 11250 / 11250.dat Minifig Tool Gavel 15082 / 15082.dat Animal Wing Bat with 0.5L Bar 15626 / 15626.dat Panel 4 x 16 x 10 with Gate 21787 / 21787.dat Minifig Hair Short Quiff 24054 / 24054.dat Door 1 x 4 x 7.667 with Curved Top 27149 / 27149.dat Minifig Hat Cylinder Tapered with Hatband 29633 / 29633.dat Minifig Hair Bob Cut Parted in Middle 29636 / 29636.dat Minifig Whisk 59232 / 59232.dat Minifig Flail 93091 / 93091.dat Figure Friends Handbag with Zipper 94724 / 94724.dat Figure Friends Accessories Spray Bottle with Heart Rematched: 23306 / 577c.dat Minifig Lightsaber Hilt without Bottom Ring 32531 / 32531b.dat Technic Brick 4 x 6 with Open Center 2 x 4 with Round Underside Studs 32532 / 32532b.dat Technic Brick 6 x 8 with Open Center 4 x 6 with Round Underside Studs Importable: 577a.dat / 23306 ~Minifig Lightsaber Hilt without Bottom Ring (Obsolete) 15556.dat / 23306 ~Minifig Lightsaber Hilt without Bottom Ring (Obsolete) 15556a.dat / 23306 =Minifig Lightsaber Hilt without Bottom Ring 32531.dat / 32531 ~Moved to 32531a 32531a.dat / 32531 Technic Brick 4 x 6 with Open Center 2 x 4 with Cross Underside Studs 32532.dat / 32532 ~Moved to 32532a 32532a.dat / 32532 Technic Brick 6 x 8 with Open Center 4 x 6 with Cross Underside Studs md5sum: e35bb62f0bef2f623e357cd19a94bb38

Ah, okay, you’re importing a LDraw file into LDD and some parts are missing. First, good thing you gave 64228 as an example. 64228 isn’t in the custom parts we talk about in this thread because it’s in LDD 4.3.11, Brick version 2670. And (my version of) ldraw.xml knows how to import 64228.dat into 64228. If your LDD doesn’t have 64228, check (Help | About) it’s version 4.3.11 with brick version 2670. If you have 4.3.11 / 777, see this message (in which “the other thread” is this thread). Then, if you’re still missing some parts, tell us their IDs