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: 24)
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.

I would like to request the following parts if possible:

- 70694
- 40145
- light-up lightsaber Minifigures. This link might help: YouTube deconstruction
- 3262
- 2142
- 77257
- 77258
- 2148
- 73764
- 73763
- 3156
- 2601

Thanks in advance! This is also a list for myself to keep track of new/updated parts. I know the new worm screw is in works already, but when it is on the PT, I will delete if from the list.

I just noticed you can not use (your own) attachments from previous posts in a new one.

I wanted to reuse the LDCad Alpha 2 picture for the Alpha 2a release, but it just prints the

Hello all,

I've solved all the reported Alpha 2 issues and made a new version.

Besides bug fixes I've also added 2 new minor features to the part bin:
- Hiding of zero count items during count down mode is now optional.
- Negative searching using the '!' character, eg: "1x1 !round" to get all 1x1 parts except the round ones.




So be sure to make backups of your work before changing them with this Alpha version.

The new version can be downloaded here:
http://www.melkert.net/LDCad/nextVer

Town sets released in 1992 (Split from 1980's and 1990's Thread)
The topics of this year are:
* IN:  Paradisa subtheme, along with pink and light-green bricks
* IN:  Octan brand (fictional petroleum company in Lego world)
* IN: Plastic sails for surfboards and sailboats
* IN: Minifig heads other than standard grin
* OUT: Roman sans-serif police logo


Updated: Added stickers, used official parts, corrected misplaced and obsoleted parts


  6346 - Shuttle Launching Crew.mpd (Size: 26.34 KB / Downloads: 14)
   

Currently not OMR compliant (unofficial stickers not inlined)
Missing items: none

What our feeling about 3rd party patterns from places like Citizen Brick and EclipseGraphics?

Hi,
   Would like assistance with parts from the new Optimus Prime set (10302):

1762 / 67421 Slope 33 2x3 double / inverted (It is in mecabricks though.   I didn't now how to export it.)
53029 Hinge Brick 2x2 Locking with 2 Fingers Vertical and Cross Style Axle Hole, 7 Teeth There is a dat file in github but doesn't load properly in Part Designer
73304 Power Burst Figure Pedestal 5x5 x 2/3.  Not in Github
3660 / 76959 Slope, Inverted 45 2x2 with Hollow Round Bottom Tube.  Also on Mecabricks

Thanks for the great work you do

George

Hello all,

I've repacked the 1.6d version to include the newest shadow file.

This will prevent potential problems loading models while using the latest LDraw library.
http://www.melkert.net/LDCad/download

Wanted to do this a month ago, but totally forgot


The only change over 1.6d is the shadow, no binary changes.

Therefore you could also just update the shadow.sf file
http://www.melkert.net/action/download/shadow.sf

After discussion with our "numbers" admin, this zero should be omitted. While he is unsure of the prior precedent, he's fairly certain this has occurred before. Additionally, electronic info for the part is stored by LEGO without the zero. If there is a conflict with an existing number then we can revisit this issue.

Should all the parts that use Swiss 720 font be required to use the handful of primitives we have already added to the library (before we decided that doing so wasn't desired)? I thought we settled this debate as "No" but the issue has cropped up again.

My stance is that it is at the option of the author and lack of use does not constitute a "Hold". This will be the official guidance on the matter unless consensus takes us in a different direction.