Hello all,

I've released another maintenance update for the 1.1 version of LDCad.

This release is mainly to improve support on pre 2.0 OpenGL implementations in regards with shading related crashes during LDCad startup. See also the 'known issues' section on the website if the improvements don't work for your particular driver/VGA.

You'll find the new version at

www.melkert.net/LDCad


The 1.1 mascot screenshot for closure, enjoy:

This is a staple hair piece in recent sets and I really need it in leocad. It's used on Agent Chase and Fuse, Chase Mcain, several Harry Potter characters, at least one of the minifigures in the Minifigures series, and the list goes on.

-Eagleeyedan2

Since we had only 5 confirmed nominees, no election is necessary. Therefore, without further ado, the 2012/2013 LDraw Standards Committee (LSC) is (in alphabetical order):

Travis Cobbs
Chris Dee
Roland Melkert
Orion Pobursky
Allen Smith

Congratulation to the new LSC!

Willy Tschager
On behalf of the LDraw.org Steering Committee

As per http://www.ldraw.org/article/382/#Procedures:

Quote:Annual Summary

The members of the LSC will be responsible for publishing an annual summary to the community several weeks prior elections for the next year’s term. This summary shall outline the progress of the previous term, note all versions of the spec ratified during the term, and summarize the future goals and ideas of the current LSC members.

This post explains the small history line "BFC rationalisation" which appears
in the bunch of updated official files that Chris just has uploaded to the PT for me, thanks, Chris!

I had recently done a systematic syntax check of all currently official files.
Through this I discovered these files having some common glitches, which I ironed out.
They were:

(a) appearance of header elements throughout the file, mostly due to inlining relicts, e.g. "Name: xyz" or "BFC CERTIFY CCW"
(b) repeated BFC CERTIFY statements throughout the file (probably due to MLCad save operation)
© changing of winding from CW to CCW or vice versa inside the file (usually a result of inlining)
(d) other syntax errors

Hi All,

I hope this is OK to post here...

Having previously created a number of animations using POV-Ray for rendering the frames I thought I would try using LDView to render the frames required instead. (Thanks to Travis (author LDView) for answering a number of my questions in this forum which helped me to get this working).

First online result of this can be seen at the folllowing link:

http://www.youtube.com/watch?v=Y7Iq3wju3O0

Rendering this is POV-Ray would take about 100 times longer... (Such as http://www.youtube.com/watch?v=TudW-8FjMzE)

The 'falling parts' code (my software) is new and rather than one part falling at time (which is how I have done these animations previously) now multiple parts are in motion in any one frame. The 'algorithm' is not perfect yet, some parts still 'fly through' other parts - work in progress ...

Rob

(TCBUK)

I was wondering if there is a complement primitive for this file? I tried flipping and turning the 1-8cyls2.dat file. But that does not work. Could somebody please help? Thank you in advance.

Attached Files

  test-prim.dat (Size: 67 bytes / Downloads: 0)

I was wanting to separate the metal portions of
http://www.ldraw.org/cgi-bin/ptdetail.cg...859c00.dat
into 1 or more separate files.

Reason for this was that in the current implementation,
when you use that part in a model,
and you assign some color to it,
all edges on metal appear in that color,
this makes that part look weird.

Reason for that is that all edges and optional edges in that file
are coded in color 24, regardless whether they bound plastic or metal parts.

My problem is now this:

I can easily identify quads and triangles of color 494 (metal) and move them to a separate file.
Second step should have been to also move their bounding edges and optional edges there.

Would I have finished that, then the color problem would be gone, because in that new file X.dat,
I would use color 16 for quads and triangles, and 24 for edges and optional edges,
and then reference that file from 2859c00.dat, using color 494. This way, both the surfaces and
the edges would appear in correct color.

However, identifying which edges to move to X.dat is terribly difficult.
There are tons of such edges, and manual selection will introduce lots and lots of errors.

To accomplish this task, I would need help of a tool which doesn't exist yet.

It would let me specify some color, by which I would like to identify affected quads and triangles
(here: 494).
The tool should then run through the file and identify all edges and optional edges which bound
these, i.e., which share coordinates with them.

Using such a tool, it would be easy to find all edges in 2859c00.dat which need to be moved to a separate file.

(Of course, from a logic point of view, each own metal portion should probably go into its own,
separate ~part file, but to me that's second priority. Solving the miscolored edges problem has first.)

Unfortunately, without this tool, I sadly have to give up on this task for now :-(

Hi,

This afternoon I've been looking at the cool 'unofficial parts library', they looked good on the website but when I opened them in Bricksmith I cept getting 'Bricksmith couldn't find all of the pieces in this file. The following are missing: s\xxxx.dat, s\xxx.dat', (those filenames are just an example) and realized why this was, it's because all of the file 'scripts' / contents when opened in a text editor have an '\' in them when it should be an '/', replacing all of them allows Bricksmith to find the subparts (located in the 's' directory).

Now, the problem was editing these thousands of files so I found a program called textmate ,when I went back the parts opened fine with no errors and had no changes to the file extention.

Here's how to fix this:

Download the unofficial parts library and extract the 'LDRAWUNF' directory to the bricksmith folder so you have the folders 'LDRAW' and 'LDRAWUNF' (LDRAW should already be there as it comes with bricksmith).

Find the 's' subfolder in 'LDRAWUNF'>'parts' and move it onto the desktop (make sure it is moved not just duplicated).
Download 'Textmate' then after installing. goto 'file', 'open'.
Locate the 'parts' folder in 'LDRAWUNF' and in the parts folder select all of the dat files and hit 'open'. (there should be nothing but .dat files in that folder since we moved the 's' folder).

Goto 'edit' and click 'find', then 'find in project'.

Type in the 'find' bar '\' (with no quotes) and hit 'find'.

In the 'replace' box, type in '/' (no quotes) and hit 'replace all'

Close the box and go to 'file', 'save all'.

Now go ahead and move the 's' folder back into the 'parts' folder in 'LDRAWUNF'

All or most parts should now return no errors when being opened.

***NOTE*** the 'parts' or 'p' folder containing official parts that comes with bricksmith should not be touched for this fix.

Note to mods, Im not sure what category of the Ldraw forum this should be located in.

Please vote on the proposal below. Please modify the Subject to include your name and vote, in addition to giving your vote in the text.

Quote:Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:

<Set Number> - <Set Name>[ - <Sub Model Name>]

Where:
<Set Number>: The number assigned on the container of the set.
<Set Name>: The name of the set printed on the container in English.
<Sub Model Name>: This is Optional in most cases. This is required for alternate models that are detailed in instructions (e.g. the Creator theme). In this case the naming is left to the discretion of the author but should be descriptive of the model contained in the MPD.

Quote:Each model in the OMR will consist of several files that are packaged together into a single MPD file. For sets that include instructions for multiple models, each model will have its own MPD file. Each MPD for the set will be named in the following manner:

<Set Number>[-<Optional Qualifier>] - <Set Name>[ - <Sub Model Name>]

Where:
<Set Number>: The number assigned on the container of the set.
<Optional Qualifier>: Is a sequential number, starting with 2.
<Set Name>: The name of the set printed on the container in English.
<Sub Model Name>: This is Optional in most cases. This is required for alternate models that are detailed in instructions (e.g. the Creator theme). In this case the naming is left to the discretion of the author but should be descriptive of the model contained in the MPD.

The <Optional Qualifier> is not mandatory and gets added only if there is more than one set that could be assigned the same <Set Number>. The first set using a given number would be understood to never contain the qualifier however numbering should start with the oldest set and some investigation should be done in existing set databases.

Example:
6901 - Mobile Lab.mpd (Produced in 1980)
6901-2 - Space Plane.mpd (Produced in 1998)