For some background, I've been looking at using the LDraw parts catalog as a starting point for 3d printing a few missing parts from some of my original 1970s space lego sets I kept from when I was a kid - set 924 for example. I could just buy the pieces of course, but trying to print them myself seems like a lot more fun :-).
I know the caveats around measurements in the LDraw catalog being approximations of the real physical dimensions, and being optimised for on-screen rendering, etc, so please say something if I'm stirring up old discussions and maybe just point me in the direction of those so I can read them.
Having said that, while I've been experimenting I've found some general inconsistencies between similar primitives in LDraw parts catalog and was I hoping someone could help me understand if they're "by design" or just historical drift between individual files, and whether there'd be any interest (or not) in trying to iron them out if they're not expected. Some of the parts haven't been modified for over a decade so I appreciate it might just be better to let sleeping dogs lie at this point :-).
There's a bunch of different types of inconsistencies I've found - I won't go into all the details unless there's some positive value to the community, but as a single example the control points for the conditional lines on the ends of part "p/1-4cyli.dat" look like the green lines in this screenshot and they appear to work as intended when the model is rotated (Note: I've attached the screenshots as well in case the Imgur posts get deleted):
but the control points for the conditional lines at the ends of "p/2-4cyli.dat" look like this and don't really show the conditional outline on the end edges correctly when the model is rotated:
I'm kind of new here (only been lurking for a couple of weeks), so there might be a legitimate reason for these odd-looking control points, in which case I'd be interested in what that is so I can understand it better.
In any case, if this kind of feedback is useful please let me know. And if it's not, please say so as well and I'll avoid spamming the forum with lots of irrelevant glitches :-)
Some help please i been trying to join the sections i have circled but now doing my head in no matter what i can not get right is there a easy way or a short cut to help me starting to do my head in thank you
This part seems to need some fixing. The flanges should be 1 LDU thicker and the channel 2 LDU thinner, in order to properly fit the tires it goes with.
Here's my proposed fix, but it brings up some other issues, like the visible edge lines where the side supports meet the backside disc. (I tried a fix, but it messes up prim sub.) And what about the origin??
It's looking like the next update will happen around the weekend of the 7th. I'd like to have the axle fix finished so that gives us 2 weeks to take care of the items on this list: https://www.ldraw.org/cgi-bin/ptreviewsu...xleholefix
and address any items on the focus list that can be done.
this version fixes many bugs and supports "invisible subparts".
It is not required to uninstall the previous LDPartEditor version, before installing version 1.8.55.
LDPE uses now a very modern technology stack and does not need a Java installation anymore.
...to see a warning for subpart references with no content. You can also transform empty subparts and "see" them as a single vertex in the 3D editor.
...use "Show Selection in Text Editor" to show the first line that uses that vertex, when you selected a vertex (or the next lines when you repeat the function).
...benefit from a better contrast of hidden lines in the text editor.
The following critical issues were fixed:
Empty primitives couldn't be selected/rotated (e.g. 1-16chrd's)
The zoom value for newly created files was not the default value (3D Editor)
When the user did not wanted to save the file in the text editor it was still displayed in the 3D editor.
"Show selection in 3D View" did not select the vertices from subfiles.
When you used separate text and 3D windows and created a new file, a new text window was opened, instead of using a new tab in the already opened text window.
If you used "save as", a new file was created, but no text window or tab was created, although the sync tabs button was active.
"Sync. 3D Editor Tabs with Text Editor" setting was sometimes deactivated.
(back-ported to 1.8.54) LDPartEditor 1.8.54 won't start on Linux (because of a classpath error)
Minor IO error regarding the "(no file selected)" tab.
The program was tested intensively with "real world" files.
However, it is still a beta version and 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.55.msi
Start LDPartEditor from the start menu
Installation on Linux:
Download and extract LDPartEditor_linux_x64.zip
Install ldparteditor_1.8.55-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.55.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
Please note that this software is in the beta stage. Although, this version was tested, there are already known issues for this release. There is a potential risk of data loss.
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: 100 MB
Recommended Requirements:
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.