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

A couple of items that would help me out:
- If a pbg file references a ~Moved to part, show the new part, not the old.
- The ability to paste a rotation matrix string (or the whole line)

Hi,

did any of you run successfully Datheader under Linux?

w.

Hello all,

I have a submodel with several degrees of freedom, e.g. something like this:

   

It can be rotated around the end pins and around the central beam and folded at the two joints. My problem now is to find the correct configuration to fit the final pin into a given hole. For me as a total beginner in digital modelling it is quite intriguing that this task would be trivial in reality, but is a considerable challenge digitally.

However, I cannot be the first one facing such a problem. So I wonder how you guys address it. Trial and error? Some powerful tool? Currently, I am writing a lot of my ldraw files by hand, but for trial and visualization I use LeoCAD. Having said that, I am certainly interested as well if some other editor is helpful here. (If it runs under Linux, this would be a great plus, but not essential.)

Thanks for your help,
Lutz

Hi,

the LDraw SteerCo has unanimously decided to eliminate the current Physical_Colour parts from the official LDraw Parts Library via fasttrack. Physical_Colour parts are parts with hard coded colours, an unique part number and an underscore in front of the description. LEGO calls these "Element numbers". Following a few part numbers from the current library for comparison:

4277932.dat
4277933.dat
300321.dat
4116604.dat
...

But before they get "obsolated" by the Library Admin, we seek feedback and input from the community. Have your word.

Willy Tschager
on behalf of the LDraw Steering  Committee