| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 5,425
» Latest member: Abbondio
» Forum threads: 6,247
» Forum posts: 52,243
Full Statistics
|
| Latest Threads |
Technic 1990
Forum: Official Models
Last Post: Takeshi Takahashi
3 hours ago
» Replies: 15
» Views: 18,837
|
LDConfig.ldr problem with...
Forum: Official File Specifications/Standards
Last Post: Orion Pobursky
Today, 2:18
» Replies: 9
» Views: 205
|
Creator 2024
Forum: Official Models
Last Post: Marc Belanger
Yesterday, 22:04
» Replies: 11
» Views: 29,563
|
The colour of textures in...
Forum: Parts Authoring
Last Post: Sylvain Sauvage
Yesterday, 19:37
» Replies: 12
» Views: 395
|
Move to question
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
Yesterday, 1:51
» Replies: 1
» Views: 86
|
Sorting by date
Forum: Website Suggestions/Requests/Discussion
Last Post: Peter Blomberg
2025-11-06, 22:41
» Replies: 7
» Views: 625
|
Keywords and invalid 0 li...
Forum: Parts Tracker Discussion
Last Post: Orion Pobursky
2025-11-03, 22:17
» Replies: 6
» Views: 346
|
Minifigure Head MINI HEAD...
Forum: Part Requests
Last Post: Bailey Meyer
2025-11-03, 20:37
» Replies: 5
» Views: 535
|
Friends 2025
Forum: Official Models
Last Post: Philippe Hurbain
2025-11-02, 19:24
» Replies: 1
» Views: 674
|
Parts request , spider we...
Forum: Part Requests
Last Post: Peter Grass
2025-10-31, 11:23
» Replies: 1
» Views: 254
|
|
|
| Does any friend know how to classify the parts in the CustomParts folder of the studi |
|
Posted by: Jack - 2025-10-14, 12:08 - Forum: Help
- Replies (4)
|
 |
Hello everyone, I'm a beginner. While using Studio, I've added many custom parts, but all of these parts are placed in the CustomParts folder. If I categorize the files in the CustomParts folder, the parts won't display properly in the Studio software. I'd like to ask you amazing netizens if there's a way to organize them into categories. Right now, all the parts are mixed together, making it hard to find what I need. Thank you all in advance!
|
|
|
| Unit Conversion Ratios |
|
Posted by: Hageta - 2025-10-11, 18:10 - Forum: LDraw File Processing and Conversion
- Replies (3)
|
 |
I am currently working on this issue that involves unit conversion to LDraw (currently all units are first converted to mm and then to ldu).
And I came up with the following conversion ratios:
[Micron/Micrometer(μm): 400μm * 0.0025ldu/μm = 1ldu]
Millimeter(mm): 0.4m * 2.5ldu/mm = 1ldu
Centimeter(dm): 0.04m * 25ldu/cm = 1ldu
[Decimeter(dm): 0.004m * 250ldu/dm = 1ldu]
Meter(m): 0.0004m * 2500ldu/m = 1ldu
Inch(in, ″): 1/64in * 64ldu/in = 1ldu
Foot(ft, ′): 0.001312336ft * 762ldu/ft ~ 1ldu
Please take a look if I got everthing right.
* everthing in [] is just here for completness, allthough micron is actually a valid unit in 3mf files.
|
|
|
| Vertex precision |
|
Posted by: Peter Blomberg - 2025-10-09, 15:14 - Forum: Official File Specifications/Standards
- Replies (4)
|
 |
For free-form stand-alone vertexes, one decimal is usually enough. However, when a vertex is defined by a circular primitive, rotated subparts or the intersection of slanted surfaces, then more decimals are needed. I've tried working with three decimals, but tools like Edger2 will not always recognize the presence of a cond line rounded to three decimals. Similar results with overlap- and gap-finding tools.
The official parts library specifications state "In general, three decimal places are sufficient for parts, subparts, and primitives representing portions of parts that are not intended to be scaled (for example, studs, pegs, peg-holes, clips, hinge ends, etc.). Four decimal places should be used for high-res primitives and any primitives designed to be scaled (for example, cylinder sections, boxes, rectangles, discs, edges, etc.) as this allows such primitives to be scaled by a factor of ten while still preserving three decimal places of accuracy.".
I'd like to amend this by allowing 4 decimal places to be used for - vertexes on a rotational plane of symmetry (e.g. 30, 45, and 72 degree planes),
- intersections calculated by isecalc,
- any vertex that is defined by a scaled primitive.
The first one because this will avoid gaps/overlap when multiple similar subfiles are put together in a larger assembly.
The second one to have an accurate edge line where two surfaces intersect each other.
The third one to avoid gaps/overlap next to any scaled primitive. This is also needed for all cond lines that have a point or a control point on such a vertex.
If we all agree, can this be made official?
|
|
|
| Cylindrical polygons |
|
Posted by: Peter Blomberg - 2025-10-08, 6:33 - Forum: Official File Specifications/Standards
- No Replies
|
 |
Currently, we have cylindrical polygons with 8, 16, and 48 sides. So, if a part needs a 1-6 sweep, we are forced to use the 48-sided polygon. For very large radii, even 48 sides is not enough. We have 84-sided polygons on the tracker. When we need a cylinder with the number of faces divisible by 5, a custom 50-sided polygon becomes used. What if 16 points are too coarse and 48 points are too dense?
I'd like to solve these by introducing 12, 24, 60, and 84-sided cylinders. The 12-sided is a nice replacement for the 8-sided because three segments make much nicer corners than 2 segments. The 24-sided is perfect when 48 is too much and 16 too little. Both allow 1-6 sweeps. The 60-sided cylinder is more usable than the 50-sided cylinder in that it is divisible by both 3 and 4. The point of the 84-sided cylinder is that the vertexes are distributed differently (divisible by 4, but not by 8) than any multiple of 48, thus allowing vertex optimization at large radii.
The 60-sided cylinder would be used at radii above 36.
The 84-sided cylinder would be used at radii from 80 to 120.
Here's a table showing the segment length for different radii and polygons. Below are recommendations for minima and maxima (radii and segment length) for each polygon optimized for segment length.
The polygon "4" is just a corner made out of one quad at a 45 degree angle.
|
|
|
| List of Moved To's that point to Moved To's |
|
Posted by: Orion Pobursky - 2025-10-08, 0:33 - Forum: Parts Tracker Discussion
- No Replies
|
 |
Moved To's shouldn't point to Moved To's. Here's a list of the current parts that do that:
(Note: I didn't vet every part here. There may be false positives or some reason not to untangle the redirects but the default should be that Moved To's should point correctly)
parts/100.dat, http://library.ldraw.org/parts/180
parts/134.dat, http://library.ldraw.org/parts/558
parts/138.dat, http://library.ldraw.org/parts/623
parts/148.dat, http://library.ldraw.org/parts/741
parts/149.dat, http://library.ldraw.org/parts/742
parts/179.dat, http://library.ldraw.org/parts/1166
parts/193.dat, http://library.ldraw.org/parts/1468
parts/197.dat, http://library.ldraw.org/parts/1576
parts/240.dat, http://library.ldraw.org/parts/2192
parts/2455.dat, http://library.ldraw.org/parts/2476
parts/249.dat, http://library.ldraw.org/parts/2540
parts/252.dat, http://library.ldraw.org/parts/2605
parts/256.dat, http://library.ldraw.org/parts/2721
parts/275.dat, http://library.ldraw.org/parts/3075
parts/2909c01.dat, http://library.ldraw.org/parts/3305
parts/291.dat, http://library.ldraw.org/parts/3306
parts/3010p20w.dat, http://library.ldraw.org/parts/3921
parts/3068p101.dat, http://library.ldraw.org/parts/4997
parts/3068p50.dat, http://library.ldraw.org/parts/5002
parts/3149c.dat, http://library.ldraw.org/parts/5432
parts/321.dat, http://library.ldraw.org/parts/5570
parts/32133c01.dat, http://library.ldraw.org/parts/5585
parts/3324a.dat, http://library.ldraw.org/parts/5968
parts/34.dat, http://library.ldraw.org/parts/6043
parts/3626-4t.dat, http://library.ldraw.org/parts/6331
parts/3660p03.dat, http://library.ldraw.org/parts/6690
parts/4.dat, http://library.ldraw.org/parts/7485
parts/405.dat, http://library.ldraw.org/parts/7553
parts/407.dat, http://library.ldraw.org/parts/7628
parts/408.dat, http://library.ldraw.org/parts/7637
parts/415.dat, http://library.ldraw.org/parts/7846
parts/4265c.dat, http://library.ldraw.org/parts/8450
parts/432.dat, http://library.ldraw.org/parts/8539
parts/48.dat, http://library.ldraw.org/parts/9622
parts/480.dat, http://library.ldraw.org/parts/9623
parts/4865p02.dat, http://library.ldraw.org/parts/9745
parts/5.dat, http://library.ldraw.org/parts/9829
parts/553.dat, http://library.ldraw.org/parts/10176
parts/56.dat, http://library.ldraw.org/parts/10225
parts/577.dat, http://library.ldraw.org/parts/10317
parts/590.dat, http://library.ldraw.org/parts/10416
parts/6.dat, http://library.ldraw.org/parts/10479
parts/605.dat, http://library.ldraw.org/parts/10655
parts/680c01.dat, http://library.ldraw.org/parts/11998
parts/7.dat, http://library.ldraw.org/parts/12048
parts/73696.dat, http://library.ldraw.org/parts/12344
parts/73696c00.dat, http://library.ldraw.org/parts/12345
parts/73697.dat, http://library.ldraw.org/parts/12350
parts/73697c00.dat, http://library.ldraw.org/parts/12351
parts/810.dat, http://library.ldraw.org/parts/12728
parts/91.dat, http://library.ldraw.org/parts/13418
parts/95.dat, http://library.ldraw.org/parts/14049
parts/99.dat, http://library.ldraw.org/parts/15065
|
|
|
| File naming convention for part 87079? |
|
Posted by: Peter Grass - 2025-10-07, 5:17 - Forum: Parts Authoring
- Replies (2)
|
 |
The naming convention for part 87079 seems to start off being hexadecimal and then kinda goes random but there are gaps like there is no 87079PC or PD, PE, PJ to L etc. So what number am I supposed to use? Should I just fill one of the gaps?
|
|
|
| Duplo hitches |
|
Posted by: Peter Blomberg - 2025-10-06, 10:05 - Forum: Parts Authoring
- Replies (8)
|
 |
Now that more duplo trains and cars are modeled, we should think about the primitives for the hitches aka tow pins, tow loops, and tow clips. Duplo hitches come in many types and variants. However, when minor differences are ignored, it boils down to a handful tow pins and tow hooks.
Long unreinforced tow pin
Suggested archetype: 4883a in LDraw
The classical tow pin has a long neck and no topside reinforcement.
4559, 4580 (Corrected), 4883a, 4883b, 53053, 31300 (Corrected), 59273a (Rebrickable)
Long fully-reinforced tow pin
Suggested archetype: 22307 in Rebrickable
The classical tow pin with long neck and full topside vertical reinforcement.
31507 (Corrected), 22307 (Rebrickable), 59273b (https://www.ebay.com/itm/365018516343)
Short unreinforced tow pin
Suggested archetype: 2312 in LDraw
This tow pin has short neck, no topside reinforcement.
2312, 31300a, 4580b, 6505
Clasped tow pin
Suggested archetype: 52071 in Rebrickable
This tow pin has short neck and horizontal triangle covering the topside
1326, 2034, 18520, 52071, 54007
Short fully-reinforced tow pin
Suggested archetype: 11248 in LDraw
This tow pin has short neck and full topside vertical reinforcement.
11248, 31300b, 15313, 15314, 31174, 95462, 98214, 58234, 53899, 4354
Short half-reinforced tow pin
Suggested archetype: 28759
This tow pin features a curved topside reinforcement.
28759, 28743, 2092
Tow loop
Suggested archetype: 4883a in LDraw
Features a closed tow loop/hook
4883a
Rectangular tow clip
Suggested archetype: 53053
Features an open tow clip/hook on a triangular rectangular support.
2320, 6505, 53053
Rounded tow clip
Suggested archetype: 2312&11248 in LDraw
Features an open conically-tapered tow clip/hook on a rounded support.
2312, 11248, 31174, 52071
Untapered tow clip
47450
Trailer tow clip with wheel, horizontal
18520, (87657), (87658), (89198)
Trailer tow clip with wheel, angled
14923
This list is not exhaustive. Some additional cases were omitted.
4883b reinforced clip/hook (https://www.ebay.com/itm/186383419871)
4820 reinforced trailer clip/hook
All movable clips/hooks
|
|
|
|