Hi,

Concerning bracket 1x2 - 2x2 down

A mysterious question, perhaps not at all that relevant, but I found


- 44728 has two supports underneath
- 92411 has three

In LDraw 86644, 92411 and 44728 look all the same and have 2 supports.

- 86644 is the number for transparent pieces.

I even found there supposed to be a 21712.

I don't mean to nitpick, but should we add the 3rd support to 92411?
Does the 3rd support have a function on certain models?

And should there be yet another alias 21712?

Just wondering....

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!

The 11090 in BI has a longer interior bar hole than the current 11090 part on the tracker and there does seem to be a newer version of the part as mentioned in this reddit post to confirm there needs to be a variant made.

https://www.reddit.com/r/lego/comments/1...ants_with/

Attached Files

Thumbnail(s)
   

  11090.dat (Size: 46.96 KB / Downloads: 1)

This is the list of all currently missing Torsos and Legs for Castle related Minifigs from the BrickLink Catalog, excluding the Viking models from Fantasy Era.
Id love to see these added in the future. Especially the Fantasy Era and Kingdoms. 


  Fantasy Era

• Torso Castle Fantasy Era Scale Mail Crown on Collar Pattern - Item No 973pb0437
  
• Torso Female Dress with Medium Blue Decorations and White Squared Collar with Gold Dots Diamond Brooch Yellow Chest Pattern - Item No 973pb0568
  

• Slope 65 2 x 2 x 2 with Bottom Tube with Minifigure Dress Skirt Robe Gold and Medium Blue Trimmed Pattern - Item No 3678bpb016
  

  Kingdoms

• Torso Dark Brown Apron with Silver Buckles Pattern - Item No 973pb0892
  
• Torso Castle Kingdoms Gold Dragon Head and Chain Belt on Sand Green and Dark Green Quarters Pattern - Item No 973pb0681
  
• Torso Castle Kingdoms Armor Breastplate with Gold Lion Head Belt Front and Back Pattern - Item No 973pb0682
  
• Torso Castle Kingdoms Female Corset with Gold Trimmed Front and Rectangular Neckline Pattern - Item No 973pb1032
  
• Torso Castle Kingdoms Gold Chain with Cross and Fur Trim Pattern - Item No 973pb0959
  
• Torso Female Corset with Ruffled Collar, Red Side Panels and Light Bluish Gray Filigree, Necklace with Round Jewel Yellow Neck Pattern - Item No 973pb0698
  
• Torso Castle Kingdoms Gold Trimmed Vest with Purse and Belt Pattern - Item No 973pb1033
  
• Torso Castle Kingdoms Peasant Vest over Light Bluish Gray Shirt Pattern - Item No 973pb0913
  
• Torso Castle Kingdoms Female Corset with Brown Apron Pattern - Item No 973pb0915
  
• Torso Castle Kingdoms Peasant Shirt with Brown Collar and Shoulder Bag Pattern - Item No 973pb0914
  
• Torso Castle Kingdoms Dark Silver Scale Mail Armor with Dark Green Collar Dark Brown Belt with Gold Buckle Chain Pattern - Item No 973pb0691
  

• Hips and Light Bluish Gray Legs with Chain Mail Pattern - Item No 970c86pb02
  
• Slope 65 2 x 2 x 2 with Bottom Tube with Minifigure Dress  Skirt  Robe Apron with Pocket and Belt Pattern - Item No 3678bpb035
  
• Slope 65 2 x 2 x 2 with Bottom Tube with Minifigure Dress Skirt Robe Layered with Dark Green Panel and Gold Belt Pattern - Item No 3678bpb041
  
• Hips and Red Legs with Gold Belt and Lion Head Charm Pattern - Item No 970c05pb04
  
• Hips and Legs with Dark Brown Apron Pattern - Item No 970c00pb0112
  
• Slope 65 2 x 2 x 2 with Bottom Tube with Minifigure Dress Skirt Robe Red Panel Pattern - Item No 3678bpb019
  

  Knights Kingdom I

• Torso Castle Knights Kingdom Scale Mail Brown Pattern - Item No 973px119
  
• Torso Castle Knights Kingdom Bull's Head on Brown Shield Pattern - Item No 973px120
  
• Torso Castle Knights Kingdom Plate Armor Silver Pattern - Item No 973px115
  
• Torso Castle Knights Kingdom Vest Shield and Lion Head Pattern - Item No 973px118
  
• Torso Castle Knights Kingdom Bulls Head Studded Armor, Red Collar Pattern - Item No 973px137
  

• Hips and Legs with Castle Knights Kingdom Leg Armor Green and Silver Belt Pattern - Item No 970c00pb0014
  
• Hips and Light Gray Legs with Red and Yellow Belt Blue Surcoat Ends with Scalloped Edges Pattern - Item No 970c09pb01
  

  Knights Kingdom II

• Torso Castle Knights Kingdom II with Jayko Pattern - Item No 973pb0355
  
• Torso Castle Knights Kingdom II Lion with Crown Pattern - Item No 973pb0346
  
• Torso Castle Knights Kingdom II with Scorpion Pattern - Item No 973pb0347
  
• Torso Castle Knights Kingdom II with Rascus Pattern - Item No 973pb0352
  
• Torso Castle Knights Kingdom II with Amulet and Vest Pattern - Item No 973pb0353
  

Friends sets released in 2015

The missing parts are listed here:
https://forums.ldraw.org/thread-24146.html

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.

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.
  

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.

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

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?