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 577 online users. » 2 Member(s) | 571 Guest(s) Applebot, Baidu, Bing, Google, L.T, Orion Pobursky
|
|
|
Arrange pieces of a set |
Posted by: Fredo - 2024-11-09, 3:30 - Forum: LDraw Editors and Viewers
- Replies (1)
|
 |
Hi,
I have a CSV with list of parts. I imported the CSV to LeoCAD, Stud.io. LDCad but as I didnt use any x y z reference all pieces are in the same coordinate.
Is there a way in any of the programs to select all pieces and automatically arrange separated one from other?
Thanks!
|
|
|
Organizing the parts library |
Posted by: Peter Blomberg - 2024-11-08, 21:30 - Forum: Official File Specifications/Standards
- Replies (6)
|
 |
The present LDraw library is divided into primitives, subparts, and parts. Each part can be assigned to a category and have zero or more keywords to aid searching. However, there is not yet any coherent structure for organizing similar parts.
Patterned versions of parts are primarily identified by a part number extension, while distinct underside reinforcements may be indicated with a letter (a, b, c...), a different part number, or some other extension to the part number. How would a prospective digital builder known which version to use without getting lost in the jungle of similar parts?
I propose using an ontology where the different versions of a brick are organized in a hierarchical manner. It could for example be possible to define a 'generic' brick and all its known variants of underside reinforcements in a consistent manner. This ontology could then be used to filter the library to produce different official subsets of the library for different stakeholders.
Reusing dat files is an efficient way of constructing complex structures out of modular subunits while maintaining editability on all levels without redundancy. However, each additional subpart requires its own review and approval on the parts tracker before becoming eligible for inclusion into the library. The low number of part reviewers effectively limit the realistic number of subunits of a part, thus hindering adequate reuse of subunits in different bricks. Consequentially, subunits tend to be large and highly specialized, thus of little use in other parts. Additionally, I would prefer having access to box primitives where the origin is at the end of the box rather than the middle and understud primitives with the origin at the bottom end of the primitive rather than the top to simplify scaling and placement.
The above can be achieved in at least two approaches; 1. allowing subparts within a file and 2. by expanding the 'primitives' library with structures that are repeatedly constructed in part after part. Examples of the latter include boxjcyl, a halfway truncated stud8, and all-edge versions of some boxes.
Solution 1 would enable more consistent parts as modular intermediates can be constructed in a "for this part only" manner. Solution 2 would enable more broader reuse of modular subparts. Neither excluding the other.
I would also prefer more standardized naming of parts, consistent part orientation, regularized primitive sizes, and circular segments other than those starting from a 0 or 90 degree angle.
|
|
|
Minimum angle of a quad or triangle |
Posted by: Peter Blomberg - 2024-11-07, 1:48 - Forum: Parts Authoring
- Replies (2)
|
 |
I'm working on part 35965 and it has an underside periferal wall of thickness 4 LDU and multiple perpendicular branches. At worst, the 4 LDU side branch is 160 LDU away from the corner, thus making the sharp angle 0.0349 degrees (0.0006 radians). This is larger than the minimum angle of 0.025 degrees specified in the official requirements, but it is really long and narrow triangle!
How accurate/tested is this minimum specification?
What makes something work having the 4 LDU side branch up to 189 LDU away from the corner, but suddenly stops working at 190 LDU from the corner?
Can I as a part author choose to allow T-junctions when the sharp angle is less than 1.43 degrees? This corresponds to a 4 LDU high object 160 LDU away from the corner. Interestingly, that angle is 0.025 radians!
|
|
|
Are underside reinforcements relevant? |
Posted by: Peter Blomberg - 2024-11-06, 7:25 - Forum: General LDraw.org Discussion
- Replies (7)
|
 |
Dear LDraw community,
Part moulds change over time as LEGO improves their designs. This leads to parts having relatively minor differences in their shapes. Sometimes this affects functionality, but often not.
When it comes to underside reinforcements, is it a detail that can be ignored or would you like to see all individual variants for the same part modeled in LDraw? Is it sufficient for you to have one variant in your digital part library or would you like to have all variants?
|
|
|
Curvature of duplo parts 98252 98224 11169 |
Posted by: Peter Blomberg - 2024-11-05, 15:56 - Forum: Parts Authoring
- Replies (1)
|
 |
The curvatures of parts 98252, 98224, and 4198 (bottom) should be the same and match perfectly with 11169.
duplo stacked.png (Size: 149.34 KB / Downloads: 36)
The real parts do match, but their digital replicas don't. 98224, 98252, and 4198 (bottom) uses a 40x48 48\1-4edge, while 11169 uses a 47x48.3 48\5-24edge with additional padding.
To make things worse, none match the curvatures of parts 2302, 98223, 4198 (top), and 18652 having a 40x48.8 48\1-4edge with padding. However, there is almost no difference between the 47x48.3 48\5-24edge in 11169 and the 40x48.8 48\1-4edge in 2302/98223.
Finally, to prove having done my research this time, I attach two real world test cases, for which I photographed the joined parts and counted pixels. The spread of dots is due to the uncertainty of establishing the exact boundary between two surfaces of equal height. I placed a dot where I thought the main color of the part started to become darker (the real parts have rounding near the edges and that rounding causes darkening of their color in a photo).
case1.png (Size: 6.87 KB / Downloads: 36)
case 2.png (Size: 8.15 KB / Downloads: 36)
|
|
|
|