Hi all,

Why do we call part 33909 "Tile 2x2 with studs on edge", while LEGO calls this a Plate 2x2 (with reduced knobs).

Same goes for 92593 which we do call a Plate (1x4 with two studs) and so does LEGO (Plate 1X4 W. 2 Knobs).

Shouldn't we describe 33909 as Plate too? I.g. "Plate 2x2 with Two studs on edge"?

Or change the description of 92593 to "Tile 1x4 with one stud on each edge" or something.

I always thought of 92593 more as a tile than a plate though... my 2 cts.

[edit] Same goes for 87580. More a tile than plate IMHO, though LEGO calls this a Plate too (2X2 W 1 Knob)


What do you guys think?
I say we call 33909 a Plate too.

Jaco

Hi all,
I propose to add the following entries to LDConfig.ldr:

Hi.

I have come up with a cunning plan for those parts, so I would like to get it. 

https://www.bricklink.com/v2/catalog/cat...P=6469#T=C
https://www.bricklink.com/v2/catalog/cat...=6469a#T=C

Christian.

Hi,

Here are some photos of patterned parts from sets 41615 and 41616. Could someone work on these parts? I can provide further photos if needed.

Many thanks!

https://www.bricklink.com/v2/catalog/cat...1#T=C&C=11


https://www.bricklink.com/v2/catalog/cat...=2#T=C&C=2


https://www.bricklink.com/v2/catalog/cat...=1#T=C&C=1


https://www.bricklink.com/v2/catalog/cat...=3#T=C&C=3


https://www.bricklink.com/v2/catalog/cat...5#T=C&C=85


https://www.bricklink.com/v2/catalog/cat...=2#T=C&C=2

I'd like to discuss the argument opened here:

The LDD ldraw.xml file has this structure:

<!-- Arch  3 x  6 x  5  30613.dat -->
<!-- PAVILION 6X3X5  19063 -->
<Brick ldraw="30613.dat" lego="19063"/>
<!-- PAVILION 6X3X5  30613 -->
<Brick ldraw="30613.dat" lego="30613"/>

<!-- Animal Dolphin  6228b.dat -->
<!-- DOLPHIN 9M  6228 -->
<Brick ldraw="6228b.dat" lego="6228"/>

How does it look like in Studio?

How would an information like this treated in an editor? Would it show also the alternate number or just jump to the right part is an element number is entered say in a search?

w.

These two are identical.

973d01.dat "Minifig Torso with "TINE" Stickers"
973d05.dat "Minifig Torso with Front and Rear Stickers with "TINE" Logo on Blue Background"

They use the same stickers, both front and back.

Hi all,

Sometimes I use small and deeply nested submodels just to make it easier to handle coordinate system transformations. For example, I might just put a liftarm and a pin into a submodel so that I can move them around together.

In these cases it is not always useful to show the submodel as a submodel in the building instructions. Hence, I would like to treat the submodel as inlined in LPub3D. However, I cannot find an option to achieve this. I can choose "Convert to callout", which can sometimes be used as a workaround, but not always, specifically with nested submodels. I can "Ignore this submodel", which does almost achieve what I want except that the parts are then also removed from the PLI. Or I can "Treat as part", which also almost does what I want except that the submodel is shown assembled in the PLI. What I need is something like "Treat as inlined". Is this possible somehow?

Thanks for your help
Lutz

Hi Guys

I have just uploaded the last available models to the OMR.
After a tough 4 months and about 500 models later, the OMR is up to date and I want to say thank you.


1st: To Jaco, who has created a wonderful list to facilitate the search.
2nd: To all authors who take their time to draw models, and
3rd: to the part authors who tirelessly draw and test parts, without which no models could be drawn.

Should anyone still discover models that I have overlooked, then please report.

Thanks.

Best regards
Johann


  index.jpg (Size: 4.91 KB / Downloads: 156)

Hi, 
I need a [color=#000000][size=medium][font=Times New Roman]cable as in the attachment: LEGO |WeDo 2.0. part no. [/font][/size][/color]LS06a.dat (LSynth Constraint Part - Typ 6a - „Power Functions WeDo 2.0 Cable").
Does anyone have this part or know where to find it?

Thx in advance!

Attached Files

Thumbnail(s)
   

Topic for 1994 Technic models