I copy here a discussion between Travis and myself about sphere primitive. Question is - should we change this primitive?

Travis Cobbs Wrote:I don't think it would have mattered in this case, but please be aware that LDView's sphere primitive substitution produces a sphere with geometry significantly different from the LDraw sphere file's internal geometry. (Enable and disable primitive substitution with this file loaded and wireframe mode enabled to see what I mean.) The three "edges" of the eighth sphere that is the basic sphere primitive sub-unit are the same in LDView's version and LDraw's version, but the geometry between the edges is very different, so will produce different results when viewed with primitive substitution on vs. off if geometry is intersecting the middle of the sphere. (Note that the 48/ version of the sphere was actually produced by me using LDView's algorithm, so that one exactly matches LDView's substitution when the substitution is kicked up two notches.)

Philippe Hurbain Wrote:About sphe primitive - wouldn't it be best to change primitive to match LDView primitive substitution version? I have always been annoyed by the warped quads in present primitive. Granted, a few parts would get weird edge lines at junctions with other elements, but at least it would no longer change with primitive substitution (16x resoluton at least).

Hi Chris,

As Orion mentioned elsewhere this article seems to be outside the webmasters control. Which is fine but means we will need to come up with a solution to migrate it to the new site.

If it is merely a static file then that is straightforward. If not we might have some hassle.

Tim

Using Part 30632 "Technic Grille 6 x 4 x 3 with Two Pins and Two Pin Holes" in MLCad and LDView generates an Error List with missing .dat elements. The Grille looks terrible. Could anyone help with verifying please ? Where can I get the missing files ?

Thanks, Arthur

Tim,

I do not think that this was a good idea. We already have linkt to the LDConfig.ldr in:

Colour Definition Language Extension
Downloads

You'd better add this to:

Colour chart

and since you are there let Scott check if the chart is up-to-date and please add Philo's graphical version:

w.

Hi all,

Given the unexpected transition to the new site, and the limited time of the webmasters I've started this thread for people to post any glaring holes they notice on the new site. If you go to find some important information (eg. the colour config files) and find it absent please leave a note here so we can prioritise transition.

We do have the original articles handy but reformatting for the new site takes time so obviously we should ensure that vital information goes up first.

Tim

PS. I think some things (like software lists) should be moved over to the wiki where corrections can be made by anyone. These will need to be linked to or embedded on the main site. But such decisions can be made on an ad hoc basis for now.

Hej everyone,
in the past I've added s\4181p08a.dat and s\4181p08b.dat to the PT. But I did a mistake, the part was already there as s\4865p01b.dat and s\4865p01c.dat. The old one are official since last year. But they aren't looking well. (The arrows are wrong formed and the rings are too thin and too thick.)
Due to the fact, that 973p8h.dat was submitted a couple of days ago. I'm thinking about solve the duplicate problem.

This is my proposal, what I will do: Correct and scale MY old files and upload them as s\4865p01b.dat and s\4865p01c.dat. (No errors will occur at official parts). I will change all unofficial files except of the torso, here I will add a comment and hope that the author will change this file.

Other way: Change all references in official parts using the old, "wrong" files to my version and correct the problems due to the chance, change unofficial parts in a way, that the "hold" can be removed in the early future. Problem for me: I'm not sure, which official parts are using the s\4865p01b.dat and s\4865p01c.dat. So I would need help here.

If there are not more than 10 or 15 official parts involved, I would prefer the 2nd way.


Any comments or suggestions?

/Martin

Hi everyone! I'm brand new here so I'll go ahead and introduce myself. Most all of my work is on Flickr.

I've done a variety of instructions which can be seen here.

Right now, I'm putting together some instructions for someone, and I'm in need of the microphone part.

I know nothing of creating parts so if someone could help me out, I'd be immensely grateful!

Hi,
My wanted part is the Superman Hair from the recent Super Heroes Lego.
Basically the hair with the curl at the front. Is there such a part?

It looks like I was too hasty in adding Olive Green and assuming that it was the The LEGO Group's Color 326 Spring Yellowish Green. Now that Bricklink is selling Yellowish Green; it is obvious that Yellowish Green matches TLG's Spring Yellowish Green. Olive Green seems to match as close to Spring Yellowish Green as it does Faded Green, so it will be matched with LEGO ID 210 Faded Green.

I plan on changing our LDraw Color ID of Olive_Green from 326 to 210, and adding the new color Yellowish_Green with Color ID 326.

Please let me know if anyone has any major objections to this, but this post is mostly to inform anyone working on these parts:
973pb990
3626cpb669
98166pb02
DARaptor2
DATRex3
DAPtera3
98086pb02
bb539c02

that Olive_Green will soon be code 210 instead of code 326.

I won't be so hasty in the future to release a new LDconfig at the beginning of the year...I'll wait until enough of the new colors are out in the wild that making matching decisions will be more straight forward.

Thanks,
Scott

EDIT: Added an [attention part authors] to help those who should read this to read this. TG

Chris,

what are the filepaths for Alias and Physical_Color under:

http://www.ldraw.org/library/official/<filepath> ?

Thx, w.