Hey,

this version will extend the "change winding"-tool to work with lines and condlines, too.
It also corrects a "Merge to Nearest Vertex" bug. This merge function will now skip pure condline control points.
There was an important change on the LDraw library URL, too (www.ldraw.org -> library.ldraw.org).



As always, you can download LDPE from this page:

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

Changelog:

(4 new features and 3 bug fixes)

With this release you will be able to...

• ...use the change winding tool (j) on type 2 and type 5 lines, swapping the end points.
  
• ...have the "verbose" option common to nearly all tools, and be remembered between sessions.
  
• ...deep inline a subfile and it will mark the end of that subfile, too.
  
• ...have the CR LF at the end of a line to be included in the selection when you click on a line number.
  

1. "Merge To Nearest Vertex" recognized condline control points as vertices to merge for.
   
2. The LDraw library URL was outdated (www.ldraw.org -> library.ldraw.org).
   
3. 3D scenes only rendered to 1/4 of 3D window in some rare cases.
   

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

1. Download and extract LDPartEditor_linux_x64.zip
   
2. Install ldparteditor_1.8.66-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.66.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.
  

I am done with the sliding bricks.

On Bricklink they are listed as "bb0037" and "bb0037b" in our library we do have only "bb0037b" as "x946"

• bb0037
  is loosely mounted on the Sliding Brick Holder and kept in place by an extension on the bottom of the Train Base (LDraw: 303, BL: x902)
  
• bb0037b (LDraw: x946)
  needs to be pushed in the SLiding Brick Holder to "clip" in place, it will not come loose easily and does not require the Train Base to be held in place
  

1. x946 and x946b or
   
2. x946a and x946b
   

• u9597a - housing as bb0037
  
• u9597b - housing as bb0037b
  
• u9580 - weight (2x)
  
• u9582 - cover
  
• and the existing bearing 3111 (2x)
  

• Shall we add shortcuts? They might be reasonable as the brick usually holds two train wheels and swivels with them (by approximately 11 degree in either direction. The question is, what is uncoloured, best is tthe train wheel...
  
• They are used as follows
  

1. x946(a) with wheel 244c02
   - black wheel with black rubber (sets 162, 727)
   - red wheel with black rubber (set 182)
   
2. x946b
   - red wheel 244c01 motor without rubber (set 720)
   - red wheel 243c01 (Set 721)
   

• I moved the origin by 6 LDU to have it swivel around the centre of the circle that the bows on the part are part of.
  -> This might have a lot of impact on existing models, as this part is practically since an eternity on the tracker. On the otherhand it is unofficial.
  -> What do you think? is it ok to move the origin or if we use a new naming, the old part will anyway become obsolete
  

I tried to download a recent version of LDConfig.ldr from

https://www.ldraw.org/library/official/ldconfig.ldr
or
https://library.ldraw.org/library/official/ldconfig.ldr

This was not possible. Where can I download a recent version of LDConfig.ldr?

edit: I found the answer. It was located here (case sensitive):

https://library.ldraw.org/library/official/LDConfig.ldr

Since we had only 5 confirmed nominees, no election was necessary.

Therefore, the 2023/2024 LDraw.org Steering Committee [1] is:

Philippe Hurbain
Gerald Lasser
Orion Pobursky
Max Martin Richter
Willy Tschager

[1] Try not to confuse the LDraw.org Steering Committee (SteerCo) with the LDraw.org Standards Board (LSB). The Steering Committee sets the course for the LDraw Organization while the Standards Board deals with the LDraw File Format.

Congratulations to the reconfirmed members!

Max Martin Richter
On behalf of the LDraw.org Steering Committee

Hi folks,

I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2023-01. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.

Download the file from my website: http://www.holly-wood.it/mlcad/mlcad_ini-en.html

Bye, w.

A minor thing that I've always been curious about:

Keywords are not allowed to contain words or phrases from the part or model description. So for the model of "Benny's Spaceship Spaceship Spaceship!!!" you could not have a keyword of "Benny" or "spaceship". Easy.

But what about the model for "Tokyo" (the Architecture skyline set) which includes the Tokyo Tower? Can the entire phrase "Tokyo Tower" appear as a keyword, or does it have to be just "Tower" since "Tokyo" already appears in the description? By itself, "Tower" might be too generic to be useful.

My feeling is that it's fine to just apply that weaselly concept of "common sense", but it's worth asking as some LDraw tools may need to distinguish the rule when evaluating file headers.

A suggestion would be to clarify that a !KEYWORDS term—a complete word or phrase—is not allowed if the same word or phrase appears exactly in the file description.

Hi all,

Is there any way to extract the models from the game LEGO Bricktales?
These worlds are wonderfull vignets and have nice builds.

I finished playing the game and I am working on various models from it.
Example: https://forums.ldraw.org/thread-26926.html

I also started building some of the worlds and level vignets, just for fun, but this is very intense.
It would be nice if you could extract builds form the game, just like with instructions and other LEGO 3D sources from the past.

Any help or advices is apprieciated.

Jaco

Basic sets (mainly 5+/7+ with instructions) released in 1990-1993 as the third wave (Script "BASiC" logo)
Set 715 Basic Building Set 7+ Medium Box (Year 1990)
A-model Formula 1



  715-1 - Basic Building Set 7+ - Formula 1.mpd (Size: 18.39 KB / Downloads: 3)
   

OMR compliant
Missing items: Flexible rope

Hi,

When I create a snapshot from the command line, like so:

<?php 

system('LDView64.exe "temp_3001-4.ldr" -SaveSnapshot="3001-4.png"'); 

<?php 

system('LDView64.exe -SaveZoomToFit=1 -SaveAlpha=1 -AutoCrop=1 -EdgeThickness=5 "temp_3001-4.ldr" -SaveSnapshot="3001-4.png"'); 

Hi I need help to learn on to draw the geek servo motor for lego Studio 2.0 . Thank You