Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 4,955
» Latest member: L.T
» Forum threads: 5,957
» Forum posts: 50,508
Full Statistics
|
Online Users |
There are currently 575 online users. » 2 Member(s) | 569 Guest(s) Applebot, Baidu, Bing, Google, L.T, Orion Pobursky
|
|
|
2566 Plant Tree Palm Top |
Posted by: Sylvain Sauvage - 2024-11-14, 19:48 - Forum: Parts Authoring
- Replies (9)
|
 |
Seems strange because the part is in LDraw since 1998 but it seems 2566 is wrong: the body is too long (24 LDU instead of 20 LDU) and the bottom bar too short (16 LDU instead of 24 LDU).
There’s no alternate ID so it shouldn’t be a variation. Am I missing something?
Source and pic.
|
|
|
Torso shortcut naming |
Posted by: Orion Pobursky - 2024-11-12, 22:15 - Forum: Parts Tracker Discussion
- Replies (15)
|
 |
Currently we're naming the torso shortcut with the same suffix as the torso (e.g. 973p02 -> 76382p01). As I've come up on torsos that are used more than once I've been using suffixes from obsolete torsos (e.g. 973p01 -> 76382p01 and 76382p11) or a suffix used by a different numbered shortcut (e.g. 973p1r -> 76382p1r and 76382p0v since 973p0v uses 16360, the dual mould arm shortcut).
Since I want to ensure that all 973pXX(X) torsos have at least one torso shortcut with the same suffix, when we run out of these overlaps I don't want to simply use the first available suffix.
Therefore, I proposed that if there is no appropriate and available suffix to take, a torso shortcut will use the pNNNN suffix using the first unused number in sequence.
|
|
|
Studio library inconsistencies |
Posted by: N. W. Perry - 2024-11-10, 23:58 - Forum: LDraw Editors and Viewers
- Replies (5)
|
 |
Thinking again about this post (from Philo) about Studio:
(2024-06-21, 8:24)Philippe Hurbain Wrote: Is it possible to create an MPD embedding ALL official and unofficial parts? My use case is to render (or create BIs) a model with Studio without fiddling with all part incompatibilities, libraries not in sync causing missing subparts and so on...
The complete scenario would be to embed all parts, add a prefix to avoid any conflict with existing Studio parts, extract these parts from MPD with MPDwizard, and place them in Studio CustomParts folder. After that, the model _should_ import flawlessly in Studio.
There are so many of these inconsistencies that when you have a really big build (like the Notre Dame cathedral I just finished), it can take quite a long time to adapt an LDraw model to Studio.
Remind me again, what's to prevent me from simply copying my entire LDraw folder in place of the one that comes with Studio, so that it always has the full library every time?
Or would it truly be better to try and embed all parts in an MPD, as Philo suggests?
|
|
|
|