I'm firmly of the opinion that we need to get the flex parts out there. I don't care how but we need part numbers and parts and every length that has appeared in a set. In my opinion it is quite terrible for users of LDraw to have no easy access to usable parts that could be auto-generated in seconds by some of us.

So far the release has been held because of technical issues with the library. This is no reason to not have the parts out there as we can always replace them if a decision is made.

http://www.ldraw.org/cgi-bin/ptdetail.cg...s/75-1.dat
http://forums.ldraw.org/showthread.php?t...199#pid199

So my proposal:

1) We quickly come up with a naming system

2) We auto-generate self-contained parts in all appropriate lengths (I already have perl code for this)

3) We submit one of these to the Part Tracker

4) Once it is certified we adjust the others to take into account comments and put them up

4) If the system is changed in the future we auto-generate again

Tim

I have the ability to add syntax highlighting site wide (forums, wiki, the upcoming main site). It works for most common programming languages but there's no module for LDraw syntax. Before I waste time writing a module for LDraw syntax, is this something that would be of interest?

LEGO Friends vs. Minifigs by Dunechaser, on Flickr

The new mini-dolls are going to be fun.

I've made a short time-lapse movie of me building the Unimog:
Youtube Video

Hi all,

I'd like to call on those who use Linux and LDraw to help edit this page on the wiki

http://wiki.ldraw.org/index.php?title=Ge...ed_-_Linux

Given the huge variety of linux flavours and tricks for getting things to work I think user-editable content is a better idea for this one that fixed content.

Tim

Do we need the LDraw Wiki?


1.)
There is a whole section with LUT-parts.
Do we realy need these compilation of pages, when the extraction from LDD is possible, and are becomming common?

2.)
There's an obsolete page with info about ldconfig.ldr.
It needs an update, or must be removed. It's only causing confusion.
The only correct page is here. Or am I wrong?
(b.t.w. are these two pages both correct? article 93 and article 547).

3.)
Do this discussion belong here in the forum instead?
We need a place to collect facts about our standards, and routines, but the discussion should be moved here.

Hi,

the LDraw Steering Committee has agreed to update the LSC Final Draft - Membership with the following text:

Quote:Membership of the LSC shall have a minimum of 5 people. The LSC can vote to create additional vacancies for future elections. The LSC also defines a procedure for voting to eliminate seats added in the future. One seat is reserved for a current LDraw Library Administrator. If there is more than one LDraw Library Administrator then the LDraw Library Administrators will self select a member to represent them on the LSC.

Hi, I am just noticing that

here
http://www.ldraw.org/cgi-bin/ptdetail.cgi?f=parts/x564c01.dat

and here
http://www.ldraw.org/cgi-bin/ptdetail.cg...459s01.dat

the images on the PT look weird. Something must be broken with the logic which applies
color to subfiles.

This bug may be related to the one that this file
http://www.ldraw.org/cgi-bin/ptdetail.cg...s/x564.dat
gets shown in a lighter grey than this one
http://www.ldraw.org/cgi-bin/ptdetail.cg...564c01.dat

hmmmm - Travis, do you know of this problem already?



EDIT:
here's some more files appearing broken, just for debug helping:
http://www.ldraw.org/cgi-bin/ptdetail.cg...945sde.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...945sgb.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...945sch.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...945snl.dat
http://www.ldraw.org/cgi-bin/ptdetail.cg...55as02.dat

What is the best and easiest way to get a good quality 2D render of an LDraw file?
I'm looking to make some set files for BlueBrick and I need (good) 2D renders of a top view.

Would anyone like to give input to defining the rendering properties of the materials in ldconfig? For instance, could we add the following lines at the end of the file:

0 // LDraw Material Definitions
0 !MATERIAL METAL Ambient 0.2 Diffuse 0.7 Reflection 0.7 Refraction 0 Specular 0.5 Roughness 0.05 Brilliance 3 Phong 0.5 Phong_Size 40


Alternatively, we could create our own POV-Ray include file with these values and distribute it. I remember that we used to distribute a POV-Ray include file with the All-In-One installer.

Any thoughts?

Thanks,
Scott