| Welcome, Guest |
You have to register before you can post on our site.
|
| Online Users |
There are currently 4 online users. » 0 Member(s) | 1 Guest(s) Baidu, Bing, Google
|
| Latest Threads |
[BUG] Ldraw set files dow...
Forum: General LDraw.org Discussion
Last Post: Orion Pobursky
6 hours ago
» Replies: 2
» Views: 87
|
Brickcraft - Building lik...
Forum: LDraw Editors and Viewers
Last Post: Fernando Cabiedes
10 hours ago
» Replies: 0
» Views: 74
|
I made 66219pr0001
Forum: Parts Authoring
Last Post: Willy Tschager
10 hours ago
» Replies: 1
» Views: 131
|
Technic 1994
Forum: Official Models
Last Post: Takeshi Takahashi
11 hours ago
» Replies: 39
» Views: 71,207
|
We have a problem, again
Forum: Parts Authoring
Last Post: Magnus Forsberg
Yesterday, 8:26
» Replies: 16
» Views: 10,736
|
Part 3659 update?
Forum: Part Requests
Last Post: Jacob Emcken
2026-10-17, 17:07
» Replies: 9
» Views: 891
|
Fire logos
Forum: Parts Authoring
Last Post: Chris Böhnke
2026-10-16, 21:52
» Replies: 5
» Views: 356
|
Part 8018 - Cockpit 3 x 6...
Forum: Part Requests
Last Post: Chris Böhnke
2026-10-16, 21:50
» Replies: 2
» Views: 268
|
Missing Ninja 1998 Minifi...
Forum: Part Requests
Last Post: Chris Böhnke
2026-10-15, 21:56
» Replies: 16
» Views: 3,457
|
Missing Adventurers Minif...
Forum: Part Requests
Last Post: Zack Uhlenhuth
2026-10-15, 21:47
» Replies: 5
» Views: 1,895
|
|
|
| 0 !NOSUBSTITUTE Meta Command |
|
Posted by: Max Murtazin - 2022-10-01, 21:55 - Forum: Official File Specifications/Standards
- Replies (3)
|
 |
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
|
|
|
| [LDPE] 1.8.63 Released (usability / custom line size / bug fixes) |
|
Posted by: Nils Schmidt - 2022-09-30, 21:21 - Forum: Parts Author Tools
- Replies (18)
|
 |
Hi,
this release will add five small improvements and fixes one bug regarding the "Save As..." button.
![[Image: attachment.php?aid=12753]](https://forums.ldraw.org/attachment.php?aid=12753)
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).
The following critical issues were fixed:
- "Save as..." removed sometimes a correct directory prefix (e.g. "48\") from the file header.
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.63.msi
- Start LDPartEditor from the start menu
Installation on Linux:
- Download and extract LDPartEditor_linux_x64.zip
- Install ldparteditor_1.8.63-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.63.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: 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.
|
|
|
| Complimentary Conds |
|
Posted by: Orion Pobursky - 2022-09-29, 20:41 - Forum: Official File Specifications/Standards
- Replies (22)
|
 |
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.
|
|
|
| Questions about the official library part number specification |
|
Posted by: Manfred Schaefer - 2022-09-26, 17:27 - Forum: Official File Specifications/Standards
- No Replies
|
 |
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
|
|
|
|