SylvainLS

Update 2020-08-05 Rematched: 62808 / 40359a.dat Minifig Key Importable: 62808.dat / 62808 ~Moved to 40359a Added Custom Parts: 46834 / 46834.dat Technic Clutch with Axle Connector Outer Side 46835 / 46835.dat Technic Clutch with Axle Connector Inner Side 46882 / 46882.dat Technic Panel 15 x 2 x 7 Mudguard with Trapezoidal Arch 65413 / 65413.dat Technic Gear 28 Tooth Double Bevel with Peghole 65414 / 65414.dat Technic Differential Casing for 5 Internal Gears Modified Custom Part: 22969 / 22969.dat Wheel 56 x 46 Technic Racing Added Custom Assemblies: 40918 / 40918-f1.dat Technic Linear Actuator 12 x 2 x 2 (Contracted) Note on Customized Part: 47996 Boat Rigging 4 x 28 Rectangular is now flexible, and therefore LDD won’t convert it. lxf2ldr will convert it without flexing it as the part isn’t in LSynth. md5sum: 1103713abeaf19fbdccedf003e5a0088

Well, then it seems the bounding box is what defines the center of a part for the conversion because I had to remove a 90° rotation for 377203 (plus a translation). And for 35442, there was a 0.8 cm move on Z (a 0.4cm translation had to be changed to a 1.2cm one). And it appears it’s the difference with the older version: the bounding boxes (Bounding and GeometryBounding) both being moved 0.8cm for minZ. Interesting. Though, I’m not sure it would be really useful to automatize the transformations. Oh yes, I read that but didn’t connect the two

Also, there are decorations referenced in DecorationMapping.xml that are not in the git repo. Seems to be ElementIDs associated with standard parts but without the images. Some incomplete tests?

Update 2020-08-04b Added Custom parts: 15522 / 15522.dat Minifig Head Simpsons Marge Simpson 15523 / 15523.dat Minifig Head Simpsons Bart Simpson 15524 / 15524.dat Minifig Head Simpsons Lisa Simpson 15525 / 15525.dat Minifig Head Simpsons Maggie Simpson 15527 / 15527.dat Minifig Head Simpsons Homer Simpson 22969 / 22969.dat Wheel 56 x 46 Technic Racing 32296 / 32296.dat Tyre 50/ 29 x 54 Technic Racing 32298 / 32298.dat Tyre 61/ 41 x 54 Off Road 46334 / 46334.dat Wheel 17 x 75 Motorcycle Solid (needs Work) 46335 / 46335.dat Tyre 38/ 22 x 75 Mock-Up (needs work) 65617 / 65617.dat Brick 3 x 3 x 1 Corner Round with Curved Top 67140 / 67140.dat Tyre 28/ 48 x 75 Motorcycle with Racing Tread Modified Custom parts: 35442 / 35442.dat Plate Gear 6 Tooth 2 x 2 377203 / 37720c.dat Animal Bat Emblem 1 x 2 md5sum: 4c10ab4bae81cef8736bb554e0d2a86b

Also 35442 / 35442.dat Plate Gear 6 Tooth 2 x 2 377203 / 37720c.dat Animal Bat Emblem 1 x 2 have been modified. I don’t know if I missed the modification earlier but their position and orientation have changed. I saw that while I updated ldraw.xml

@Stephan There’s a problem with 4745 Propeller 2 Blade Twisted too: no .g And for 22569 RIM Ø 62 X 46, the axle connection is turned 45° (or the whole wheel is…).

Update 2020-08-04 Added: 98279 / 98279.dat Minifig Campaign Hat Rematched: 4209 / 4209a.dat Hose Reel 2 x 4 x 2 Holder Importable: 4209.dat / 4209 ~Moved to 4209a 4209b.dat / 4209 Hose Reel 2 x 4 x 2 Holder with Hollow Studs 28686.dat / 30293 =Rock 4 x 4 x 1.333 Top 28696.dat / 30294 =Rock 4 x 4 x 1.333 Bottom md5sum: bafe86dbe2c4f9cb571b2a9905d8eb3a

I already do

@Stephan By the way, 9062 and 9063 are in the new GitHub repo (I hadn’t seen you made a new one before ).

@manglegrat You can correct it easily in Developer mode where you can toggle the physical tests (before loading): start LDD, open a new file, toggle the tests, open the file you want to edit, find one of the 36840 or add a new one, select by shape, then you can move them all one by one. Oh, and you can toggle the tests back before editing, it’s just for the loading that they must be off.

36840 was totally updated and its center was changed on July, 16th. If you had an unconnected one with enough room around it, you’d have seen it go up one plate. But, of course, you rarely have that in a normal scene….

@PicnicBasketSam Er, there’s no 9062/9063 files in Stephan’s files, at least on GitHub. Actually, there isn’t any 9062.* or 9063.* in LDD at all. Anyway, you can just delete the .xml (and the .g in LOD0 if there are any). You can also open the XML in a text editor to know more about them. Yep, but then you also need to unbend / flatten them and that may be as difficult as making the pattern from scratch.

You could also use LDView (or other) to take a snapshot of the piece, then crop it.

You could also try converting the files to JPG before making the PDF, the loss is minimal and the filesize is generally smaller (at least it is for scanned documents; I don’t make many PDFs).

Like there’s for LDraw? (One on LDraw’s Parts Tracker, one on BL, er make that two on BL as there’s one for the parts and one for the gallery, and I’m sure there are others out there.)

Yes, even more so when there are files to delete. That’s what a “git pull” does on a “standard” git repository. But then, forcing the use of git isn’t userfriendly.

@5N00P1 Did you try the fonts trick? The problem with the fonts causes seemingly unrelated problems: Studio doesn’t know the size the text will take so it thinks there’s no room or more room than there actually is and objects don’t appear or are moved. I don’t remember it affecting the local part list but it’s worth a try. Each time there’s a new release, there are new little bugs that should have been caught by an average QA (don’t even need to be a good one). They are quickly solved but still, Studio has lots of such little bugs that come and go with the versions. It’s trying. And the devs are still adding new features (they announced the return of Mosaick!).

There might be instructions in the LXF (generally, LDD-generated instructions are crap, but still). Studio doesn’t convert the instructions from LXF but lxf2ldr.html can.

Don’t know, haven’t used Blueprint in ages.

Which issues? Two issues I know of: The fonts. It seems Studio goes directly for the fonts files, without going through Windows (or at least Wine)’s API. So it can’t find the fonts and changing their size doesn’t work and so on. Solution: make a “Fonts” directory in drive_c/windows and link there (ln -s) the .ttf for the Windows fonts (especially Arial but all the ones you want). Too thin outlines. In Page Design, the parts’s outlines are way too thin and almost invisible. Exporting to PDF gives the same resluts. Solution: well, I don’t have one I tested the Win10 VM MS distributes for testing Edge (works for 6 months I think) to export a few PDFs and it worked well but, guh, Windows is so awful , even for such a small use.

Ah, so you copy the paxml to Extended. Normally: LDD.lif contains the info for the standard mode and LDDExtended.lif contains the info for Extended. The paxml contains all the colour info and the fully decorated parts (fully = with the correct decors combinations) that can be used in the standard mode. Extended doesn’t have a paxml (normally) because it allows to use all the parts, all the colours and all the decors (each decor limited to the right part and location on the part but you can mix the decors). If I copy the paxml into LDDExtended, what I get is: A lot of parts are missing. The parts first appear in the default “standard” colour, not the usual red. As soon as a colour is chosen for the palette, it works as usual. Conclusion: I don’t think it’s a good idea to use a paxml (especially a bad one) with Extended.

@Kuramapika1 The paxml is the brick palette for the standard mode of LDD. It’s not used in Extended. Someone could try to make a modern one, for instance from the infos from BL or Studio’s ADP Palette (which is 4 years old though). Now, talking about decorations, it doesn’t seem to be working for 26678 (it works for the others).

Update 2020-07-16 Added: 18859 / 18859.dat Dish 8 x 8 Inverted with Hollow Studs 98338 / 98338.dat Minifig Weapon Spear Short with Pin Hole Added Custom Parts: 24869 / 24869.dat Wheels Roller Coaster 39793 / 39793.dat Technic Connector Block 3 x 3 with 9 Perpendicular Holes 65416 / 65416.dat Technic Brake Disc 6 x 6 67329 / 67329.dat Brick 1 x 2 x 1.667 with 8 Studs on 3 Sides 67810 / 67810.dat Brick 2 x 2 x 1.333 with Curved Corner Top 405983 / 40598c.dat Minifig Weapon Grenade with Large Tapered Top and Four Indents 405984 / 40598d.dat Minifig Weapon Grenade with Small Tapered Top and Two Ridges Corrected Custom Parts (new versions): 39790 / 39790.dat Technic Beam 15 x 11 with Open Center 13 x 9 39794 / 39794.dat Technic Beam 11 x 7 with Open Center 9 x 5 md5sum: fd79f4c22d4d6205960613319418d7e6

For starters, LDD doesn’t need a powerful PC with a powerful discrete GPU just so you can put three bricks together. (i7 laptop here, with IGP: LDD works well even with thousands of bricks; Studio, I need to lower the quality, and then, the fan is still going like crazy and the UI is just usable for small things.) I won’t talk about the UI, it’s like every LEGO CAD: some love it, some hate it, and any opinion in between. The Studio developers communicate a bit more than BrickLink (which is still not much) but they work the same way: adding new features instead of solving old bugs. So it’s progressing but has growing pains.

It was reported on the Studio forum. You need to search or read everything because it’s not really well organized. I think it’s also in the Wine report for Studio (there are several reports / several Studio versions). As for the pros and cons: Virtual desktop: the Wine window(s) are contained in a bigger window, looking like Windows windows (style/decors). Even when both the Wine desktop and Studio are maximised, you still have two window titles, one Windows-like for Studio and one from your Linux WM, so you lose a bit of vertical space. Also, the Wine desktop has a fixed size: you must change its size in winecfg otherwise its content doesn’t follow. Windows not managed by the WM: the application appears in a window of its own (like with the default option) but it’s not managed by the WM, so it won’t iconify or appear in a taskbar as “normal” window. If you use desktops to arrange your windows, the Wine windows will appear in every one. That can be annoying.