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

Think these were first seen on the 2025 F1 sets from March. Did a cursory scrub through the parts tracker, a search there and here in forums to be sure... (Swear I thought I saw these float by but can't find them now, seems this is the year for left/ridge compound curve wedge slopes with 2x2, 4x1, etc)

Limited colors for builds yet but look to be pretty interesting to design with:

• https://www.bricklink.com/v2/catalog/cat...P=6929#T=C
  
• https://www.bricklink.com/v2/catalog/cat...P=6930#T=C
  

* Activity and Parts List show when you Cert/Hold a part with the green tick/red stop, but looking at the list it does not tell, if you just left a comment.

   
   

w.

I have noticed that the 64 bit LDraw installer is especially slow when running on my current-generation ARM-based Windows PC (Surface Laptop, Copilot+ PC, Snapdragon® X Elite / 12 cores).  The actual apps x64 run pretty well on the ARM device (via emulation), but I am sure an ARM compiled version of apps like LDview would be even better.

I was wondering if anyone has explored creating a native Windows ARM version of the LDraw suite, or even just the installer?

Sincerely,
---Tom