Since July 2024, I, along with a friend have been working on a digital Lego building tool that can do advanced part(s) substitutions on LDRAW models, in a scripting syntax + tool suite.
While I have stud and clutch detection, a lot of parts do not have snapping info which is a big problem.
Without the part snapping info , it either fails with "no such primative(s) found in %partid%.dat, or it connects the part either too close or far away.
Other times it does detect the studs and clutches and therefore the snapping info, but does the same.
And other times, it correctly connects the parts.
What I did about it on my end is fix my tools z axis bug, and I am working on correcly parsing snapping info that is not top-level reference in a parts .dat file.
But since I'm only a beginner when it comes to parts editing I don't really want to start editing like thousands of part .dat files.
LDCad müsste noch verbessert werden, da einige Teile nicht anschlussfähig sind, wahrscheinlich in einigen Teilen einige Verbindungen fehlen. Eine Frage habe ich noch: Wird es eine neue Lego Cad Software geben, bei der man neben dem Part Designer auch eigene Teile entwickeln kann, weil niemand die uralten Programme wie den MLCad & den LDPartEditor durchschaut, weil er etwas Neues gebrauchen könnte. Denn mit dem LDPartEditor kann niemand mehr durchschauen, was was ist. Man konnte wirklich wieder neue Programme entwickeln. Denn mit dem LDPartEditor ist das schon sehr alt.
Time to get your reviews in. 10 days until the next update and there are currently about 100 new parts with the potential to be released.
This is going to be a huge update with ~7700 part having minor updates (mostly Set keywords and the Obsolete category) but I'd like to see more new parts go out.
I just updated the MLCad.ini file accordingly to the latest LDraw.org parts update 2025-03. The .ini file defines (among other things) the parts available in MLCad's, LEOCad's and Bricksmith's minifigure generator.
Cylindrical primitives have conditional lines at their ends with control points such that they assume a linear continuation of the shape. The control points are visualized with the red, blue, and purple lines. This is perfect when the shape is continuing as assumed, e.g. at rounded corners of rectangular objects (yellow and green lines).
When trying to avoid rotating primitives 45 degrees, the solution tend to be placing two 1-8 segments back to back. The conditional lines in the middle are on top of each other, but have different control points (turquoise lines). Neither conditional line is accurate and reviewers may point out "missing cond line". The solution is to add a third conditional line with correct control points.
However, other reviewers see this "superfluous" conditional line and demand it being removed. What is the best way?
Hello L draw I'm New here. I'm making a request for 3 airplane parts.
67244 Aircraft Fuselage Aft Section Curved Bottom 8 x 16 with 2 Holes
67243 Aircraft Fuselage Forward Bottom Curved 8 x 12 with 4 Holes
and most importantly
67241 Aircraft Fuselage Forward Top Curved 8 x 12 x 6 with 6 Window Panes
i provided a picture of the parts so you know what they look like.
I've been waiting for these parts for weeks now. and I really need these added soon i want to make a moc build of a aircraft using these.
if anyone would get these added or find them i would be happy. hope to hear back from someone soon thank you
...benefit from the fact that Rectifier "does not convert bordered rhombuses into rect primitives" by default.
...customise if Rectifier "does convert bordered rhombuses into rect primitives" by default.
...choose if Rectifier creates rect primitives with a shear or non-trivial rotation matrix.
...see a warning if the file is BFC CW certified instead of CCW.
...see a hint for "freezing the selection" when adding new objects ( I also implemented this for the next LDPatternCreator version ).
...use the old sphere mesh for CSG operations, too (CSG_ELLIPSOID2).
...use a "Concave/Convex Heatmap" mode which visualises convexity between surfaces (type 3 and 4, double-click on heatmap button).
...see the !PREVIEW meta with syntax highlighting.
The following critical issues are fixed:
The selection filter logic was not consistent.
[OpenGL 3.3] LDPE didn't switch to "special condline mode" when the user tried to add a condline.
The program was tested intensively with "real world" files.
However, something can go wrong in about 140.000 lines of code.
Installation on Windows:
Download and extract LDPartEditor_win32_x64.zip
Run LDPartEditor-1.8.91.msi
Start LDPartEditor from the start menu
Installation on Linux:
Download and extract LDPartEditor_linux_x64.zip
Install ldparteditor_1.8.91-1_amd64.deb
Start LDPartEditor from the menu or via launcher
Installation on Mac OS X:
Download and extract LDPartEditor_mac_x64.zip
Mount LDPartEditor-1.8.91.dmg
Drag LDPartEditor.app to the Applications folder
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
I listen carefully to your requests and possible complaints. Please leave me a message, with your thoughts and wishes to further improve the software.
LDPE is a 3D CAD application: The overall system requirements are higher. While I recommend to use a powerful 64-bit multicore system, it could be possible, to run LDPE on older machines as well.
System Requirements:
Minimum System Requirements:
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: 150 MB
Recommended Requirements:
Operating System (64bit): Windows 7,8,10,11, 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: 500 MB
For a faster start, LDPartEditor and the LDraw™ library should be installed on an SSD.
What are the current coplanarity settings on the PT submit checker? It claims the following lines are not coplanar, but they most definitely are. The two coordinates in y-z plane are {24,62} and {26.2713,62.4459}.
Extra spaces added for clarity in post only.
![[Image: 5500.png]](https://img.bricklink.com/ItemImage/PN/50/5500.png)
