Relevant parts:
https://www.ldraw.org/cgi-bin/ptdetail.c.../83496.dat
http://www.ldraw.org/parts/official-part...rtid=11203
https://www.ldraw.org/parts/official-par...rtid=35459

There's inconsistency in the library between plate or tile on the description of these parts. Our general rule would say use "Plate" since the studs are up. Everyone else, including LEGO, calls these Tiles.

In this case think we should use Tile as it more aligns with usage and the community.

Relevant part:
https://www.ldraw.org/cgi-bin/ptdetail.c...84ad01.dat

I think we have a gap in our spec. STAMP shortcuts are not allowed per the spec but placement of this sticker on a model is a nontrivial endeavor without a weird origin.

I see 2 solutions:
- Allow STAMP shortcuts
- Allow cases where the sticker may extend past the edge of the single part used.

I think the latter is the least complex and "better" solution.

Hello! I was wondering if I could get parts 
98154pb03 https://www.bricklink.com/v2/catalog/cat...3#T=C&C=89
98140pb11 https://www.bricklink.com/v2/catalog/cat...9#T=C&C=89
41202 https://www.bricklink.com/v2/catalog/cat...=41202#T=C
49588pb01 https://www.bricklink.com/v2/catalog/cat...88pb01#T=C
All requested. Sorry if they are a little complex

Hello all,

I just noticed you can't (cleanly) inline 2838c01 (9V motor) because it has a couple of loose quads.

imho it should just have type 1 lines so you can inline it in order to animate the drive axle.

adjusting 2839a might also fix the need for those quads?

Hello together,

first post here - so first of all: Thanks for the great efforts, people put into LDraw library - this is just amazing!

To contribute a little back, I wrote myself a web-based tool which gives one the posibility to search and download specific parts as one single zip-file out of the LDraw library which just includes all sub assemblies which are needed for the part of choice.

The zip-files' folder structure is prepared to be included into Studios' customParts folder (I know, we are in the LDraw forums here - so nevertheless, the tool might still be useful for some people in non-Studio-scenarios).

URL: https://www.reum.it/ldraw-to-studio-exporter/

Examples as direct-download Links:

• https://www.reum.it/ldraw-to-studio-expo...t=47373-f1 
  
• https://www.reum.it/ldraw-to-studio-expo...t=47373-f2
  

Hey Guys  ! I was looking for the Rock Raiders torso and head parts, but I was not able to find them. I would like to request them if possible:

Chief
3626bpr0106 🔴
973d35pr0012 🔴

Bandit
973c22h01pr0025 🔴
3626bpr0312 🔴

Docs
973c08h01pr0070 🔴
3626bpr0330 🔴

Sparks
973c34h01pr0090 🟡
3626bpr0345 🔴

Axel
973c03h01pr0143 🔴
3626bpr9956 🔴

Jet
973c28h01pr0044 🟢
3626bpr0104 🔴

Hi there,

as written in our core group, I would like to suggest to create primitives for the sticker backsides, which are rectangular and have rounded corners (formed and unformed) So they can be used for different stickers.
For now we the same backside several times with different subfile names.

I made a little Excel sheet. Which is linked 
  Sticker Bottom List.xlsx (Size: 11.26 KB / Downloads: 6) to this post. Please note that sometimes the same sticker backside is mixed up with X and Z coordinates. This needs to be fixed in any case before the release. (Do we have rule, that stickers should be made in a way that Z x X contains a X value which is always equal or greater than Z (as we do for most of our bricks)?

Suggestion for the name:

flat sticker backsides: stickbs[Z]x[X]r[Radius of Corners]
Means: StickerBackSide[Z]by[X]radius[Radius of Corners]

formed sticker backsides: stickbsf[Z]x[X]r[Radius of Corners]p[Matching part without file extension]
Means: StickerBackSideFormed[Z]x[X]Radius[Radius of Corners](Matching)Part[Matching part without file extension]

Any thoughts on this?

/Max

I created a circle with' templates --rubber band 'and changed the name to 3024.dat, but the 3024 parts are interspersed

Quote:0 FILE main.ldr
0 Author: LDraw
1 179 60 -136 -120 1 0 0 0 1 0 0 0 1 rubberBandSquare-2.ldr
0 FILE rubberBandSquare-2.ldr
0 Author: LDCad
0 !CATEGORY technic
0 !KEYWORDS flexible, band
0 !LDCAD CONTENT [type=path] [addFallBack=default] [looped=true] [displayKind=mm] [curveStep=0] [displayLenCor=0]

0 !LDCAD PATH_POINT [type=circle] [posOri=0 0 0 1 0 0 0 1 0 0 0 1] [prevCPDist=25] [nextCPDist=25] [cirR=69.5] [cirDir=xyCW] [prevYRoll=0] [nextYRoll=0]

0 !LDCAD PATH_SKIN [donCol=16] [donOri=1 0 0 0 0 1 0 -1 0] [donPart=3024.dat] [donYSize=100%] [donCen=absCen] [donCenYOfs=0] [donFinScale=fitDon2Seg] [donPlace=refsStat] [donYAlign=0] [donInline=false] [segSize=100%] [segSizeTol=0] [segsCnt=0] [segsGrp=0] [segsMaxMerge=0] [segsMrgAng=0] [segsMrgRollAng=0] [segsEdgeDelKind=keepFirstLeft]

As I am working on some train related stickers, I asked myself the question, is it better to re-use existing stickers or make aliases that correspond to the correct sheet.

Prominent examples would be the train logos, i.e. similare logos on the 164575, 164585, 168265, where 164585 can be complete doen with stickers from 164565.

Modern samples are the Andreas Crossing 2x2 Sticker that appears on multiple sheets.

Should those be added as aliases or shall we skip them? When skipping them, it might be difficult to locate the replacement, So IMHO, I would rather add them...

Opinions?

Pattern descriptions on stickers are often in need of a Left/Right qualifier.
I think we are maybe using it very differently among the part authors.
I find it odd that I often feel I have to correct the descriptions on stickers intended for vehicles.

There is a definition of Up in the sticker specs.
"The sticker should be oriented such that the top of the pattern aligns with the +Z axis."
But how about Left and Right?

Imagine a vehicle with an arrow pattern on the right hand side pointing backwards.

  arrow.png (Size: 71.02 KB / Downloads: 25)
The description should be "Sticker ...  with Arrow Left" but it should be placed on the right hand side of the vehicle.
How do I describe that pattern?   "Sticker ...  with Arrow Left Right"
On the opposite side it would become the opposite, "Sticker ...  with Arrow Right Left"

We have a qualifier (Formed) on formed sticker.
Maybe there needs to be a (Right) qualifier for stickers intended to be on the RHS (right hand side) of a vehicle?
And of course (Left) on the LHS.