• ...choose whether or not "Merge to Nearest Edge" splits the edge on merged vertices.
  
• ...limit unrectifier to only inline rect primitives (hold Ctrl and press the unrectifier button).
  
• ...adjust the direction of the manipulator to the direction of an edge. I changed the behavior of "Move Manipulator to the Nearest Edge"!
  

1. Fixed an endless loop on the first start (affected 0.8.26 only).
   
2. Rectifier added the same edge line into two adjacent rectangle primitives.
   
3. Toggle comment / TEXMAP didn't adjust the text selection.
   
4. The new render engine is now optional. Its automatic hardware detection was broken.
   
5. When you inserted a protractor, the order of the vertex triplet was not deterministic.
   
6. Unrectifier inserted an extraneous empty lines where rects were previously.
   
7. The quick fix of "invalid use of 'BFC INVERTNEXT' / Flat subfile" only removed the BFC INVERTNEXT statement. It should also invert the direction of the flat subfile in flat direction to keep the same BFC winding.
   

1. Download the zip-Archive
   
2. Extract the archive content to the location of your choice
   
3. On windows, double-click "run.bat" to start LDPE.
   
4. On linux, you have to excecute the shell script "run.sh" to start LDPE.
   

1. On windows, double-click "update.bat" to search for updates.
   
2. On linux, you have to excecute the shell script "update.sh".
   

• 64-bit Java Runtime Environment (JRE) 1.8
  
• OpenGL 2.1 compatible Graphics Card
  
• Operating System (64-bit): Windows [7 or newer], Linux [e.g. Ubuntu Linux >=14.4]
  
• 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]
  
• 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 a SSD.
  

(2016-12-31, 13:40)Philippe Hurbain Wrote: Thanks Nils, seems to work fine now (I mean, Ogl3.3)!

1. The program loads the RGB values for colour 16 from ldconfig.ldr now.
   
2. You can customise the colour value if you want the grey colour back,
   

(2017-01-10, 14:57)Philippe Hurbain Wrote: As a user, I'd like to be able to visually identify which surfaces or lines belong to the model beeing edited or to a primitive/subpart (different coloring of surfaces/lines?). Currently it's confusing as you can select a surface or line from a primitive, try to modify it with no action, or duplicate it without knowing.

And a very, very tiny bug report: if you split a distance meter you get two normal edge lines instead of two distance meters.

(2017-01-10, 14:51)Philippe Hurbain Wrote:

(2016-12-31, 13:40)Philippe Hurbain Wrote: Thanks Nils, seems to work fine now (I mean, Ogl3.3)!

Actually, after more usage, I reverted to the old render engine. As editing time (or model complexity) increases my machine again got slower and slower (even outside LDPE).

(2017-01-10, 14:42)Willy Tschager Wrote: LDPE does not complain about these double (found with Datheader):

2 24 90.793 66.369 99.273 99.273 66.369 90.793
2 24 99.273 66.369 90.793 90.793 66.369 99.273

(2017-01-10, 14:51)Philippe Hurbain Wrote: Actually, after more usage, I reverted to the old render engine. As editing time (or model complexity) increases my machine again got slower and slower (even outside LDPE).