I like to extend the possibilities of DATHeader.
Now I focused on the Physical_Colour parts.

As far as I have followed the last posts and discussions a part with the flag Physical_Colour should have the following:

1) There is only one line (linetype 1) in the wanted color.
1) There are only linetype 1 lines with colors different from color code 16.
2) The colorcode for this color is mentioned in the description in square brackets (fe [320]).
2) The colorcodes for these colors are mentioned in the description in square brackets (fe [320/83]).
2.1) If there is only one linetype 1 line the colorcode has to be mention in the description as follow (fe [320]).

If that is true and nobody claims I like to implement tests based on this definition.

I am sure that this definition is used in the past not correctly if the definition is correct. Please see the following part and references: http://www.ldraw.org/cgi-bin/ptdetail.cg...173283.dat

I would like to have the links in the posts to be opened in a new tab/window, so I can close that tab/window and can still read the post to the end.

I know that i can use the back button of the browser, but I think if you use external links, they should never close the calling page.

cu
Mike

I find the existing electric wire brick (5306.dat) somewhat weird.

I would like to have a second version in the official library without the wire stump. That way it is usable for curved wires without breaking coloring (the stump uses hardcoded poly and edge colors).

This could be fixed by moving the main body of this part to a subpart so the 5306 itself consists out of a single ref and the stump stuff (for backwards comp).

I could then use the subpart in my LDCad's deform generator without having weird color stuff going on (bricks 0, wire 16), it also makes sharper bends at the start of wires possible.

edit: Also the wire should be round and not square imho

Hope this makes sense, thanks.

I hope this is the right place to post this. I've found some errors in the Primitive Reference.
box3-7a.dat
As mentioned earlier (in a different thread) the description mentions "has a size of ... 1LDu in the {y} dimension". It actually measures 2LDU in the {y} dimension like its cousin box3-3.dat, as is clear from the image.

rect3.dat
The description here says "...excludes one edge {+x}". However the missing edge is {-z}.

I've started work on 85976, Train Track Narrow Curved. Because the connector is the same size I wondered if I could reuse some of the 9V track parts. That got my studying 2865s04.dat, Train Track 9V - Interlocking Track End. There's a lot wrong with that part; overlapping surfaces, T-junctions. After I commented in PT Michael suggested I fix the issues.
That's when I noticed there many versions of this part:
Official 2865s04.dat, Unofficial 2865s04.dat, 2865s04a.dat, 2865s04l.dat, 2865s04r.dat
They have different histories although they're based on the same original design. There are differences from fixing BFC but also small size differences.
Finally this part is specific to 9V track.
If I'm reworking this part to get rid of the technical faults I'd like take the opportunity to make it suitable for both 9V and RC. That would mean transferring a small part of the rail to the main track part. That way it should be possible to have just one subfile for all 9V and RC track pieces rather than a straight, left and right variant.
Is it ok to change 74746, 74747, 32087, 2859 and 2861? How would I keep the changes in synch?

hi

I'm looking for these part

http://www.brickset.com/parts/?part=4227282
http://www.bricklink.com/search.asp?q=44136
http://peeron.com/inv/parts/44136

I hope that someone will create these parts

thanks

I wrote this at the Part Tracker:

Isn't it time for some sort of definitive definition here?

7-digit number <=> ItemID <=> Part Physical_Colour <=> beginning with _ (underscore)
5-digit number <=> DesignID <=> Part Alias <=> beginning with = (equal to)
old design in a new mould, leading to a new partnumber, is a Part Alias <=> beginning with = (equal to)
partnumber only used for transparent parts <=> Part Alias <=> beginning with = (equal to)
partnumber only used for laquered parts <=> Part Alias <=> beginning with = (equal to)

Or am I totally wrong? I still find the difference between itemID, designID and our partnumbers very confusing.

and Philo answered:

Quote:Magnus, I'd suggest to put this on the forum for future reference...
Basically this is OK. A design number is _mainly_ a mold number, while item number is a shape in a specified color.
Unfortunately, LEGO also use 5 digits design numbers for patterned parts and sometimes (eg. hoses) for specific colors.

Hi Guys,

i'm looking for the part 47904 and either i'm too stupid to find it in the database or it's just not available.

Would be nice if anybody could help me.

Cheers

Stinger

NCS - Natural Color System

With a "Color Wheel" - like decribed in the article from Niels Bugge - there is no chance to catch all the distinguishable colors. NCS defines a Color Space in the shape of a Double Cone with vertical axis
- Saturated Hues placed at the outermost circle of the double cone
- Achromatic Colors on the Rotation Axis of the Double Cone with White on the top cone tip and Black at the bottom cone tip
- Color Nuances inside the Double Cone space layered on triangle plane with the corners Hue - White - Black
Look at the incredible architecture of this Color System
Logic behind the System

Not only a theoretical system - in the Web-Shop you will find the NCS Album containing 1950 removable printed colors sheets, each unique color example three times in the format A6 ! Ok, unfortunately not payable for an AFOL who is using all his available money for Bricks ...

I know, this product does not solve any "plastic color problem" but it is a professional system with unique identification of a recognized color and it is worth keeping an eye on. I own a similar Album with 186 hand-colored removable samples. It was produced by Chromos Verlag (Dr. Aemilius Mueller) 1958 for Swiss schools, it's color identification code is less usable then the one of NCS but it is still amazing !

Hope you enjoy,
Arthur

NB: Sorry for the wrong placement, should be positioned as an answer to "LEGO Color Overview / Comparison / Charts"

I almost posted this in off-topic, but LSculpt is an LDraw tool, so I decided to put it here.

A pink Stanford Bunny showed up in LEGO Star Wars: Yoda Chronicles, and it looks an awful lot like LSculpt was used to create it. See the following images:




(Sorry about the low quality; the pictures were taken of my TV using an iPod Touch. They get the point across, though.)

Does anyone know if this really was done with LSculpt?