SylvainLS

For 43463 and 43461, it’s because 6282 (the assembly they should be part of) is missing. Just a little bug. For 289000: good catch! For packing back into a lif, there’s LIFCreator: By the way, note that LIFCreator needs lots of memory.

Even if it was scaled and stretched, that’s not how LDD looks on a 1080 lines display. Obviously, the colour palette is cut but all the parts categories show with 1080 lines (even when maxed as yours are) (13 full lines of categories, not 7½). Same for the width: there should be more space between the groups of icons on the toolbar (more difficult to quantify). So, again, either your whole display is not at 1080 or LDD is zoomed in / magnified, and that’s not LDD’s “fault”: something else is doing it.

Your image is 800x600 and it’s stretched (16:9 stretched to 4:3). That’s why I asked. And I was talking about a setting in Windows that would zoom on LDD. 768 lines is just enough for LDD. 1080 is plenty. As you say LDD has no settings for this and it’s plain dumb about the screen size, therefore something is wrong with your system.

Are you sure the definition is 1920x1080? Or is there a zoom / HDPI setting somewhere?

It’s really not clear what you’re trying to do. What do you mean by the “ldraw file found on another thread”? The ldraw.xml file? It’s used for conversions to/from LDraw but LDD doesn’t use .dat files at all. It only needs their names. And while it’s true most of the 3D models for the new parts in this thread have been made from 3D models from LDraw, they have nothing to do with ldraw.xml¹ and LDD doesn’t need any .dat file to work with them. (¹ Well, except for those of us who want to convert their LDD MOCs from/to the LDraw format.) So, in order to help you, we need you to expand on what you want, what you do and what doesn’t work exactly.

(Our best guess is that) 4.3.12 was made to solve the problems in the thread I linked to. (It only exists for Windows, not Mac) The problem is that 4.3.12 is actually 4.3.11 (so far, it’s okay) with the Brick version 777 (that’s not okay at all). The latest official brick version that came with 4.3.11 is 2670. That’s a lot versions and a lot of brick missing. And it can’t update / download the latest version (it can’t even connect to internet, it keeps saying that). So, uninstall LDD, both the program (with the desinstaller) and your settings and the db in %appdata%roaming, then install the good old 4.3.11 that you can find in the other thread. Once it’s installed, launch it and you’ll find the parts you were looking for. Then, you’ll be able to install the custom and modified parts and enjoy the latest LDD

@jordy19 “Removed the whole LEGO folder,” which one? The one in Program Files (x86) or the one in Users? Also, when you reinstalled, are you sure you used 4.3.11 and not 4.3.12? (See this thread) I wouldn’t advise starting with a broken LDD.

Well, actually, it doesn’t exactly work. If you use one of the new assemblies with c01 in its name (say 32283c01), you’ll see that: It’s called 32283 in LDD, not 32283c01. In the LXFML, it’s still called 32283. But, even though one of its subparts is called 32383 too, it doesn’t seem to pose any problem, even for import (export doesn’t care about assemblies, only subparts). Still, I find that a bit confusing.

Update 2020-10-23 Added: 10164 / 10164.dat Minifig Headdress Beanie with Pom Pom 11437 / 11437.dat Minifig Helmet Ornament Horn Elaborate 15446 / 15446.dat Minifig Helmet Visor with Night Vision 29601 / 29601.dat Minifig Gun with Round Heat Diffusers, Fin and Spherical Emitter 30210 / 30210.dat Dish 2 x 2 with Angled Bar 47991 / 47991.dat Panel 5 x 10 x 10 Rocky Skull 60751 / 60751.dat Minifig Helmet with Cheek Protection and Thin Bands 93106 / 93106.dat Minifig Metal Detector without Stud on Search Head 94721 / 94721.dat Figure Friends Accessories Brush Round, Small 94723 / 94723.dat Figure Friends Accessories Sponge md5sum: 686a99e8cf1a7784b6d36891e532dd2d

Shameless plug: lxf2ldr converts them to LSynth primitives. So: lxf2ldr, then lsynth, then import in Studio or open in any LDraw editor.

If you have a warning sign on some parts, it’s because you have a damaged db.lif or db directory (it’s generally when there’s a problem in the 3D model (.g files) or because it’s missing). Check it or go back to the original db.lif.

You need to use LDD Extended (menu View | New themes), it’s not available in the “normal” mode. The paint tool and colours work a bit differently but you’ll need to get used to it as many bricks aren’t available in the normal mode.

Well, there’s as much merit in keeping with BrickLink as with LDraw but as BrickLink has only one part and LDraw and now LDD have several parts, and they match, I’d keep with LDraw. If someone is looking for “5292,” LDD will show them this assembly whether it’s the assembly’s name or the name of one of its subparts. (Note, 6282.xml isn’t in the RAR either. So 43461 and 43463 are “dangling” parts.)

On the contrary, it’s very important: that means you downloaded the dreadful 4.3.12 from LEGO. It’s broken. The correct Brick Version should be 2670. 777 is missing an awful lot of official bricks. See this thread, there’s a link to a correct copy of 4.3.11 installer and several explanations on how to install it on Windows 10 if you have troubles.

Well, one could say 5292c01 isn’t 5292 (And I submitted 5292c01.dat to LDraw as the motor + electrict plate to match “LDD’s” 42908. I couldn’t name it 42908-something.dat, especially not -c01.dat, as it has fewer subparts than 42908.dat.) By the way, it’s nice that assemblies’ names can have “c01” in them.

Update 2020-10-20 Added: 23766 / 23766.dat Minifig, Head Cuboid with Raised Rectangle 94719 / 94719.dat Figure Friends Accessories Comb, Small with Heart 94720 / 94720.dat Figure Friends Accessories Brush Oval, Large Rematched: 3308 / 3308a.dat Arch 1 x 8 x 2 Importable: 3308.dat / 3308 ~Arch 1 x 8 x 2 (Obsolete) 29161.dat / 10190 =Minifig Flipper Thick 88408.dat / 59275 =Minifig Flipper Thin Added Custom Assemblies: 2698c01 / 2698c01.dat Technic Action Figure (Complete) 5292 / 42908.dat Electric RC Race Buggy Motor (Complete) 6272c01 / 6272.dat Electric RC Race Buggy Receiver Unit with Auxiliary Output (Complete) 9062 / u9062c01.dat Motor Pull Back 4 x 9 x 2.333 Type 2 with Black Base 32283c01 / 32283c01.dat Motor Pull Back 4 x 9 x 2.333 Type 1 with Black Base 37191c01 / 37191c01.dat Minifig Torso Brick 2 x 3 with Arms Added Custom Parts: 1023 / u1023a.dat Sheet Plastic 11 x 27 Trapezoidal 1024 / u1023b.dat Sheet Plastic 14 x 20 Triangular 1025 / u1023c.dat Sheet Plastic 11 x 20 Trapezoidal 1026 / u1023d.dat Sheet Plastic 10 x 17 Trapezoidal 2738 / 2738.dat Technic Suspension Arm 2 x 6.5 Type 1 2999 / 2999.dat Technic Large Wheel Hub 30037 / 30037.dat Wing 9 x 12 - 6 x 2.333 Down 32079 / 32079.dat Technic Beam 9 Liftarm Offset with Boss 32137 / 32137.dat Technic Connector Block 3 x 2 x 2 66909 / 66909.dat Bar 2L with Top Studs md5sum: 8a8072e8561b79d4ef7fa000aff3597c

Two problems with 20201017: There’s an inversion between 5292 and 42908: 42908 is the whole motor with case and axles, 5292 is the motor and part of 42908. The assembly should then be 42908, not 5292. 6282.xml is missing in the git repository.

Yes, Studio 1 isn’t updated anymore. Has not been for a while now.

The number is the Design ID. You can also open the XML, it’s text and contains the name and category. And assemblies are in the Assemblies directories and are LXFML files, also text files. You may also want to move the files elsewhere first (and always keep the original db.lif safe).

Nope I try not to use non-free programmes (exceptions are LDD and Studio.io). You seem to have a reluctant PC. It’s been a while I’ve had any problems with Linux on my hardwares.

The Hinge tool is to rotate parts that are connected together (a door in its frame, a clip around a bar, or the special hinge parts like 2429/2430, etc.). If you want to rotate selected parts, just use the arrow keys on your keyboard. You can only rotate them by 90° increments. Anyway, as soon as you connect them on other bricks, they’ll want to align with them.

Well, it could be both: if /a/b/c/d is a file, you know to try and read it as a LIF, if it’s a directory, you try and read it as an expanded LIF, or you try to find a directory “db”, or a file “db.lif” in it

Sure there are! The default path seems okay to me. You could also use a command argument or an environment variable. WINE_PREFIX comes to mind (to replace “.wine”; not always set) but you could also simply use a variable for the whole path: if not set, use your default. It would allow to set/use different dbs without the cumbersomeness of passing a command argument. (Usage: “DB_PATH=bla ./LegoToR …” instead of “./LegoToR --db_path=blah …”) Note, the Readme says “/LegoToR,” either you need a dot before the slash or you need to remove the slash and have LegoToR in the PATH.

Studio’s forum.