I just found this tool and wanted to share it with you, quoting from its Google Code page:

• A rich, WYSIWYG UI editor, which provides a fully interactive preview window along side a drag & drop-enabled navigation tree, to help organize and layout your book.
  
• Automatically divide your model into steps. Add a list of parts needed for each step, and auto-layout multiple steps per page for a best fit. Auto-generate a title page and part list pages.
  

After over 1 year of development, a beta build of LDForge 0.3 is out with massive changes and improvements. Release highlights:

• multi-document support
  
• various optimizations that make LDForge a LOT faster than before
  
• able to download parts off the PT if desired
  
• circle tool with ring finder algorithm makes adding rings to parts mostly trivial, can also be used for edge circles and discs
  
• magic wand tool for easier group selection
  
• support for logoed studs
  
• support for direct colors
  
• auto-subfiler! just select and fire!
  
• various little new features, improvements and bug fixes
  

• Download (7th of September)
  
• Changelog (also bundled with download)
  

I'm looking fot the 53404
Thanks a lot.

Attached Files

Thumbnail(s)
   

I'm looking fot the 53407 part, if someone can do it.

Thanks a lot.

Attached Files

Thumbnail(s)
   

I'm looking fot the 60128 part, if someone can do it.

Thanks a lot.

Attached Files

  60128.jpg (Size: 92.13 KB / Downloads: 6)

I'm trying to get to grips with LPUB. Specifically I'm trying to show separate subfiles in an MPD file to show a bigger assembly size than the main (complete) model. So far I have found the metacommand for assembly size is 0 !LPUB ASSEM MODEL_SCALE GLOBAL 1.0000 (=100%), but I have not found a way to make local changes for a single step or for subassemblies.

I have looked for a complete list of metacommands for LPUB, but the best I've come up with is this
https://sites.google.com/site/workingwit...tacommands
and that still looks incomplete - the precise metacommand I found in my LPUB file for assembly size includes the word GLOBAL, which makes me suspect there might be a LOCAL version too. (I've tried "LOCAL" and it didn't work for me)

Can anyone point me in the right direction?

I'm trying to finish the kolhii stick part 44811 but I just cannot get Pathtruder to generate the proper shape.

My dev files: https://dl.dropboxusercontent.com/u/6605...rcurve.zip
My commandline:

http://peeron.com/inv/parts/54200
Peeron Title:"Slope Brick 31 1 x 1 x 2/3"
LDraw Title:"Slope Brick 31 1 x 1 x 0.667"

http://peeron.com/inv/parts/85984
Peeron Title:"Slope Brick 33 1 x 2 x 2/3"
LDraw Title:"Slope Brick 31 1 x 2 x 0.667"

Both above .dat files internally use a slope gradient of 12/20 which is 30.96°, close enough to 31°.

I can't find a photograph of these two aligned together, so can anyone confirm that they are both using the exact same slope angle and that LDraw is correct and the Peeron title is wrong?

Moving here a discussion started on PT

Steffen, reviewing 96484.dat Wrote:I think this should be renamed to become a normal minifig accessory.
In fact, there is no real difference between a minifig or friends or fabuland accessory.
Maybe we should rename the whole category from "minifig accessory" to
"figure accessory"........?

Steffen, reviewing 96482.dat Wrote:I don't see the necessity for the "Friends" theme in the title.
Isn't this simply a normal minifig accessory?
Arent't all accessories theme-inspecific?
this hairdryer could be used by a Friends figure, a Fabuland figure
or a minifig figure. Thus maybe we should rename the whole
category "Minifig Accessory" to "Figure Accessory".........?

Arezey Wrote:If we need to rename Minifig Accessory for generalization, I suggest just dropping the 'Minifig' and rename the category to Accessory.

Is it correct that DATHeader should warn me when I scan a "Unofficial_Shortcut Physical_Colour"?

It tells me that:
"ERROR Description for Physical_Colour parts should mention the used colors", but I'm not scanning a "part".
I'm scanning a "shortcut".

The header specification says:

Physical_Colour
The purpose of the Physical_Colour qualifier is to identify a part which is encoded as a specific colour of a part (e.g. 70770)
A part file with the Physical_Colour qualifier will typically, but not necessarily, contain only one sub-file reference (line type 1) entry, where the entry has a specific colour value and not colour 16.

It says nothing about the Shortcuts