SylvainLS

Oh, and BL already added 7.1 after the question of the over-broadness was raised. Proof that the terms were overreaching CYA to start with.

Yes, you explained why it’s there. I understand that and already said the same thing a couple weeks ago on Stud.io’s forum. What I say is that: It’s overreaching CYA legalese mumbo-jumbo that, as you also said, is (about) the same everywhere. People don’t read it or think that it does not apply to them. and that: Because it’s everywhere doesn’t mean it’s not overreaching. Because a lot of people don’t care or understand doesn’t mean that sites can write anything they want or that other people shouldn’t care. Maybe they only write that so that they can show your MOCs, maybe they will never sell boxes with your MOCs or other horrendous things. But then, why is it not written that they only need the rights to show pictures of and instructions for you MOCs? Brickshelf does write what the purpose is. Flickr is about pictures only. BrickLink is about selling LEGO, that’s “the operation of the Site.”

What happens: Everybody copies everybody’s ToS. Nobody reads them. My opinion: “everybody does it” and “nobody cares” aren’t excuses.

Wrong Java version. 52.0 means Java 8.

Happy that finally worked! (By the way, it’s not “my title,” it’s your browser adding an “explanation” because XML files can also be rendered (like HTML) so it tries and fails to render it instead of proposing you to download it. )

That’s weird. Have you downloaded the latest version (2016-12-07)? And does it look okay? (not truncated or full of garbage?) md5sum is 0cc14abdd3e926bfdd5dd1053a421d4e (I really should include that in my update posts…) Could you send me your lxf file? (I’ll send you a PM, as you can’t yet.) Yes. As of September 16th, the file has been cleaned and all the parts have been retested: … and as you can see in a following post in October, the parts from brick set 2248 / LDD 4.3.10 have been added. The file is updated to follow LDD (rare) updates and to replace digital-bricks.de parts with Unofficial parts as they arrive. The Transformation tag is okay. LDD sees it and deduces that lego ID 95646 can be exported into 95646.dat, so it works. It’s the Brick tag that’s wrong and it would only be used in import, so it’s not really a problem for you now..

Yes, that’s a strange export problem: LDD doesn’t care whether the .dat files are available or not on disk, it only transforms the LXF file into an LDR file, so that the parts are totally missing in the .ldr means there’s a problem in the ldraw.xml file. A typo or wrong duplicate somewhere? Did you try with my ldraw.xml file (even only temporarily if you don’t want to use it whole). After checking, all the parts you cite above seem to be available in the Official Library. By the way, I don’t understand why you transform 54809 Electric Motor Boat Propellor with 2 Blades (which is part of 54824 Electric Motor Boat with Light Bluish Grey 2 Blades Propellor and Rudder) into 95646 Electric Mindstorms EV3 (which is available as 95646.dat in the Official Library). (That’s not a problem for export: LDD exports 95646 as 95646.dat because of the Transformation tag. But it’d be a problem for import as LDD would translate 95646 into a subpart, so into nothing.)

What are you meaning by “they don’t work”? Are the parts wrongly placed or are they absent? They work well here. Note that my ldraw.xml file is tuned to the latest LDraw Unofficial Library (because either the parts aren’t available in the Official Library or they have been modified since its last release and it’s easier to install and use the whole Unofficial Library than to pick only the, numerous, new files). [It also contains (non)-transformations for parts that are not yet available from LDraw.org (but are available as raw translations from LDD at digital-bricks.de), for those who really need them. But the parts you cite aren’t among those.]

Sometimes, if you’re zooming in too much, panning is a pain. Zoom out, pan, zoom in.

LDD has to orient parts for stud-connections, else it would be impossible to build at angles with regular plates and bricks with LDD’s auto-snapping and collision detection. So I’d say it’s the only mechanism that will allow parts to snap to studs if the target part is angled. It’s not necessary for pins. And if you replace your half-pins with full pins and the tile with a beam, you’ll see LDD doesn’t care about the orientation of the pin, the beam will always try to connect as is. That can bring its own troubles sometimes No problem here You sure all the studs are correctly oriented? (It should also work if only one stud is correctly oriented, if you present the tile on this stud (which is not always easy to do), a bit like the trick I tried to explain with screenshot above.)

Okay, so your problem is with the pins. When you snap a part, LDD automatically orient it to be aligned to the target brick. But not the pins. They will stay rotated as you present them. They won’t orient to the hole. (But note that half-pins will orient if you connect them by their stud. Studs align. Pins don’t.) On your model, if you select one of your half-pins, you’ll see that the light blue “selected” box around it is aligned with the floor (a few aren’t). Or, if you use the rotate tool, you’ll see it’s rotated -67.42° (or something like that modulo 90°) relatively to the technic brick. Just turn all your half-pins to be oriented 0° (or 90°, or 180°, or 270°). When you approach a vertical tile, it will orient with the stud of the half-pin and snap to several half-pins because, now, they are aligned.

Can’t download the file, so I’ll shoot in the dark: If it’s because you can’t approach and snap the tile, make a small build with plates with clips and handles to temporarily attach your tile in order to rotate it about the right angles before moving it to its final position. Also, maybe you can copy a part that’s already in the right orientation (or easily turned to be). If it’s because LDD snap parts so that they are rotated by 0°, 90°, 180°, or 270° only, and your part don’t want to snap because of collisions or you’d want to place it in another orientation, you can force LDD to snap the part if you place it with another part that will be the one that snaps at Nx90°. On the screenshot below, the blue plates are the base I can’t move, and I wanted to place the red plate in that way. I placed the green round plate and the red plate elsewhere, in the correct position relatively to each other. I selected both and placed the green round plate on the blue 1x1 (drag&drop with the green round plate, dragging the red plate along; if you drag&drop by the red plate, you can’t do it). Oh, and as you used half pins, turn them the right way (aligned with the beam you want the tile to cover, I guess). As they are pins, they don’t snap at Nx90°. The tile will try to snap on one half-pin and it they are not aligned, it won’t snap to all of them. HTH

I don’t see a lot of custom bricks for LDraw out there.

Welcome! LDD prefers to snap parts when it can. To avoid this, you have to be looking at the parts the right way (straight at them). Or you can use other bricks (tiles, baseplates…) to help you place your bricks by connecting them to these “helpers” which you’ll delete once done (for complex placement, it’s called “scaffolding”).

Update 2016-12-07 Added: 20401 / 20401.dat Decoration Ball 11.3 62698 / 62698-f1.dat Minifig Computer Laptop (Open Flat) md5sum: 0cc14abdd3e926bfdd5dd1053a421d4e

Actually, they are: It’s an assembly of four parts (the frame, the belt, and the two axle holes). So that may explain these problems, though other assemblies don’t have them.

Update 2016-11-30b Corrected: 4006 / 4006.dat Minifig Tool Spanner/Screwdriver Added: 47576 / 47576.dat Wheel 17.6 x 5 with Solid Spokes and Axlehole

The wheels, 47576, are only available on digital-bricks.de (converted from LDD).

Update 2016-11-28 Added: 15469 / 15469.dat Brick 2 x 2 Round with 4 Petals Base and Axle Hole 15619 / 15619.dat Minifig Bandana Ninja

You need to be a registred beta tester to access it. (If you’re, you have a new red “Build” icon/sub-menu in your BrickLink menu bar, between “Shop” and “Community.”)

If you haven’t yet done it (at least I didn’t see it), you might want to repeat that there: http://forum.bricklink.com/ Developpers read it. Let’s profit of the beta status for that kind of suggestions.

I only checked that there’re no parts in Stud.io that is not from LDraw Official and Unofficial Parts Libraries or digital-bricks.de. (IOW, I checked the names, not their contents.) I follow BL forums (both “normal” BL forums and stud.io’s forum), and nothing was said about that. (Stud.io was not announced (see above posts) and is not discussed on the “normal” forums.) I may add that the temporary POVRay file generated for rendering is actually LDView’s. (Thus the presence of the GPLv2 text in a file called LDView.txt.) There’s no LDView executable that I could find so I deduce that LDView’s code has been somehow integrated into Stud.io. I’ll let you read the GPLv2 text to make your mind on the spirit of the matter, even though the beta status could be argued and time will tell….

Update 2016-11-25 Added: 22408 / 22408.dat Minifig Shield Pentagonal 47507 / 47507.dat Cockpit 6 x 6 x 2 Cabin Base with Pin Holes

Maybe premature questions: Will there be a new topic “Official LEGO sets made in Stud.io”? (For now, it’s LDraw underneath but, who knows, maybe there’ll be differences, for example with how the flexed parts or new options/structures are handled.) And, way more important , will there be a “Stud.io builder” badge?

Update 2016-11-24 Added: 22411 / 22411.dat Minifig Plume Horsetail