Hi all,

It seems LGEO is basically abandonned but some people are still using it (notably through Studio), so I’m posting here in case someone else has the problem and looks on these forums.  

So the problem is that, as reported in a thread on the Studio forum, the LGEO version of 30076 is rotated 90° (Z).  I checked that Studio is using the same defs as the latest LGEO lib I have and I tested with a standalone POV-Ray install and I get the same results so I can confidently say it’s not this problem.

I made a quick correction (attached; I only added two ‘rotate’ statements) and I’m sending it to the Studo devs.

Attached Files

  lg_30076.inc (Size: 13.48 KB / Downloads: 1)

Hi, 
I've found that the last digit of the transformation matrix for a flower is missing from 
40379-1 - Bear on line 340

the instruction is

Quote:1 191 -10 -16 -30 1 0 0 0 1 0 0 0  24866.dat

Quote:1 191 -10 -16 -30 1 0 0 0 1 0 0 0 1 24866.dat

Attached Files

Thumbnail(s)
   

Hi, I've picked up an error in 6360-1 - Weekend Cottage in the OMR.
It won't open in most editors. Even the OMR 3d view doesn't render the minifigs. 

The version posted on the forum by Robert Paciorek here 1980's and 1990's Town and Trains  6360 - Weekend Cottage.mpd doesn't have any problems as far as i'm aware. It has a section at the beginning where the submodels are inserted, however that's completely missing from the live version. 

Quote:1 14 0 0 0 1 0 0 0 1 0 0 0 1 6360 - building.ldr
1 2 50 -72 0 0 0 -1 0 1 0 1 0 0 6360 - male.ldr
1 47 150 -56 -10 0.383 0 0.924 0 1 0 -0.924 0 0.383 3899.dat
1 4 110 -40 -30 0.707 0 0.707 0 1 0 -0.707 0 0.707 3070b.dat
1 46 130 -40 -10 0 0 1 0 1 0 -1 0 0 6141.dat
1 46 140 -72 -30 1 0 0 0 1 0 0 0 1 6360 - female.ldr

I'm doing a presentation about LDraw at BrickCon in the Seattle as I do every year.

Here's last year's slide show:
https://docs.google.com/presentation/d/1...sp=sharing

This presentation is geared towards the vitual LEGO novice. Any feedback on things that might be worth including would be helpful.

What is the correct orientation of the duplo strecher?
The feet are attached at the studs, so logically the other end would be the head?
Should the head be toward the user or away from the user?

https://www.bricklink.com/v2/catalog/cat...age?P=6424

Looking for the Tauntaun arms and body. I see the horns and reins, but no arms or body?

These would be bricklink part numbers 86055, 86056, and 64800.

Thanks in advance!

Join me in welcoming new parts author Milan Schaefer [pinnacle3]

Please support them as they start their LDraw parts author journey.

Starting this as a separate thread since I think Peter had some good suggestions:

Quote:Getting back to the original topic; I wanted to discover some way of annotating official parts with a tag that states what would need to be fixed if a part for some other reason is being edited. IMHO, the "needs work" sounds appropriate although it is not currently used or even intended for such use.

Maybe !NEEDSWORK could be added as a meta instead of being appended to the description and/or comments/!HELP.

Why not create a !BRICKLINK meta specifically for taking care of the mapping? Or a !LINK meta with two arguments - one for the authority (e.g. BrickLink), and the other for the ID?

16-sided chords come in two types; 1-8, 3-16, 1-4, 5-16, 3-8, 7-16, and 2-4 are made of mostly quads while 5-8, 3-4, 13-16, and 7-8 are made of only triangles. I get that the final triangle count is the same no matter how the triangles are organized.

Nevertheless, the triangle-only solution has a lot of narrow triangles and they are concentrated to the same area. Why is that? I would understand it if the chords were created additively (previous chord + one triangle = next chord), but they aren't.

Should we do something about it?

For Needs work parts the header spec says:

Quote:If the part is good enough for public use, but has some deficiencies that need to be addressed, the text " (Needs Work)" (without the quotation marks) can be added to the end of the description. If the description includes "(Needs Work)", a comment must be added to the file immediately after the header that explains the work that needs to be done