The following is the final draft of the CAReadme.txt for the CC BY 4.0 conversion:
https://www.ldraw.org/draft-documents/ca...draft.html

This is being provided for comment and discussion prior to final implementation.

Assuming there are no show stoppers, I am targeting the 2023-01 (Mid January 2023) release for implementation. That release will have a complete re-release of the library will the 0 !LICENSE lines changed as appropriate.

For those who are curious, we're currently at about 64% of all parts and part edits that are 4.0 authorized. How that shakes out to % of parts that will be entirely 4.0 remains be determined. However, the library will never be completely 4.0 since at least 1 very prolific author has passed away and efforts to contact his estate have come to a dead end. Given the age of the library, I doubt this is the only case.

I have noticed that in some cases parts might fall apart when primitives being substituted in those with high-resolution versions. For preventing that from happening, I suggest including a meta command "NOSUBSTITUTE". What I intend, is that when put it before primitive of standard resolution, it would force that primitive to always be rendered as the standard resolution one, no matter the settings, similar to how 8\ and 48\ primitives behave, ensuring that part would appear normal no matter the settings. 

This command would be useful because it works with sphere primitices in a fine way, unlike ndis, which would only close mesh gaps, not make shape flow properly

Hi,

this release will add five small improvements and fixes one bug regarding the "Save As..." button.



As always, you can download LDPE from this page:

http://nilsschmidt1337.github.io/ldparteditor/

Changelog:

(5 new features and 1 bug fix)

With this release you will be able to...

• ...keep all files from the initial temporary project on application restart.
  
• ...see the D value (distance) of the distance meter not only shown in "LDU" but also in "mm" and "Stud".
  
• ...copy hint/error/warning messages to the clipboard to paste it to the PartsTracker.
  
• ...have a customizable line size button where you can set the thickness of the line for yourself (Ctrl+Click on a line size button).
  
• ...use more line size buttons (five).
  

1. "Save as..." removed sometimes a correct directory prefix (e.g. "48\") from the file header.
   

1. Download and extract LDPartEditor_win32_x64.zip
   
2. Run LDPartEditor-1.8.63.msi
   
3. Start LDPartEditor from the start menu
   

1. Download and extract LDPartEditor_linux_x64.zip
   
2. Install ldparteditor_1.8.63-1_amd64.deb
   
3. Start LDPartEditor from the menu or via launcher
   

1. Download and extract LDPartEditor_mac_x64.zip
   
2. Mount LDPartEditor-1.8.63.dmg
   
3. Drag LDPartEditor.app to the Applications folder
   
4. Copy ldparteditor.sh to your home folder
       4a. Open a Terminal.app and run ./ldparteditor.sh
       4b. Or open a Terminal.app and run /Applications/LDPartEditor.app/Contents/MacOS/LDPartEditor
   

• OpenGL 2.1 compatible Graphics Card
  
• Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• CPU: Multicore-Processor e.g. Intel Core 2 Duo or AMD Athlon II (>2.0Ghz)
  
• RAM: 4GB
  
• Video-Memory: 1 GB
  
• Free Disk Space: 100 MB
  

• Operating System (64bit): Windows 7,8,10, Linux [e.g. Ubuntu Linux >=14.4], Mac OS X [>=10.6]
  
• OpenGL 3.3 compatible Graphics Card
  
• CPU: Multicore-Processor with 4 cores (or more)
  
• RAM: >4 GB
  
• Video-Memory: >1 GB
  
• Free Disk Space: 512 MB
  
• For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
  

If complimentary conds are something we're going to hold vote then they need to be documented somewhere other than having to search the forums. My understanding was that they are nice to have but not required. Either way we need better documentation and I'm not the best person to write it.

Thread for Star Wars 2022 Models

I am trying to generate instructions for a model but LPub is only giving me the parts list and a picture of the model. There are no building steps. What am I doing wrong? Please help.

Attached Files

Thumbnail(s)
   

Hi

I'm trying to use a 2x1 hinge and set the 2x2 hinge top at a 45 degree angle but I can't get the bar to attach properly into the cradle when I have the top at the angle. Please help.

Attached Files

Thumbnail(s)
   

Hey, everyone. I’m new to adding custom textures to .DAT files from LDraw. I would like to know what programs are needed and a detailed tutorial on how to apply the decals.

I’m trying to apply custom faces into this subfile, but I want to learn how to do it.

Part 31512 - Powerpuff Girls Face

Hello,

I have a few comments on the official library part number specification.


First point.

I think the following sentence in the specification should be corrected:

"This is managed by adding a single alpha character to the end of the base part number (e.g. 3626a.DAT and 3626a.DAT, the solid stud and hollow stud versions of the minifig head)."

The correct sentence should be (see the second 3626.dat):

"This is managed by adding a single alpha character to the end of the base part number (e.g. 3626a.DAT and 3626c.DAT, the solid stud and hollow stud versions of the minifig head)."

Second point.

The description for the shortcuts is, in my opinion, inaccurate.
It is described that the shortcuts are marked by appending a c-suffix, e. g. c01.
It is not described how to proceed if there are two identical shorcuts that differ in the color of a part.
See for this a Forum post of me to the monkey 2550:

https://forums.ldraw.org/thread-26694.html

Here the second position was named with a new c-suffix (c02), although the color of the hands and feet are the same.
What if the monkey now has brown hands and feet?

In this case, I would use the c-suffix to determine the color and an f-suffix to determine the different positions.
c01 would be yellow and co2 would be brown.

Third point.

The description for the patterned parts is, in my opinion, inaccurate.
In the Parts Tracker are the following Minifig Heads: 3626bp84 and 3626cp7g.
This parts use the same pattern and only differ in the stud.
My suggestion is that the pattern is unique within a design. This is true even if there are multiple design numbers for the design, for example as at the round 2x2 tile (4150, 14769).

Regards

Manfred

Hi,

I'm the Debian maintainer of ldraw-parts: https://tracker.debian.org/pkg/ldraw-parts

I saw the new Contributor's agreement moving to CC BY 4.0 which is great for Debian because the legal problems of CC BY 2.0 made ldraw-parts "non-free" as far as the Debian free software guidelines are concerned. The CC BY 4.0 license doesn't have these problems and this would mean that ldraw-parts could be included into Debian "main" instead of "non-free".

Unfortunately, as of release 2205, I do not see any mentioning of the new license in the release zip. Instead, both CAlicense.txt as well as CAreadme.txt and all "!LICENSE" headers refer to "CCAL version 2.0".

https://www.ldraw.org/legal-info also still refers to CC BY 2.0.

Will this change in a future release?