Steffen has requested that the 64-character limit for part titles be dropped from the official library.

Alex has further suggested there be no limit.

Since I use dynamic-length strings everywhere, this certainly isn't a problem for me. Any other opinions?

Allen

hello, where to find Power Fonctions "M motor.dat" ?
Part 58120c01

Bricksmith 2.6 adds the following features:

• Supports planar textures (LDraw TEXMAP language extension)
  
• Select multiple parts by dragging a rectangle around them
  
• Part Browser improvements:
  • Source-list UI
    
  • Part Browser search scope buttons for choosing all parts or selected category
    
  • Improved text-matching algorithm for search
    
  • Recognizes and searches !KEYWORDS in parts
    
  • Identify and categorize alias parts, and exclude them from searches
    
• New option for turntable-style model spinning (in which the model can't be rolled on its side)
  
  
• Substantial improvements to the handling of neighboring file references
  • Referenced neighbor files can be opened and edited; changes seen in parent document
    
  • Submodels in neighboring files will be drawn correctly
    
• New duplicated parts are inserted into last step instead of current one
  
• Document autosave
  
  
• Option-wheel (or just wheel) to zoom
  
• Command-Shift-C for color palette
  
• Removed nonstandard Officiality setting for models
  
• Speed improvements for models with many submodel references
  
• Speed improvements while hovering mouse over model
  

• Fixed crash on 10.7+ when closing windows or viewports
  
• Step display won't change the view rotation unless the step specifies it
  
• Pan-dragging is not affected by perspective distortion
  
• Zooming gesture locked in when view is orthographic; no interspersed rotations are permitted (prevents view from changing to perspective)
  
• Allow leading whitespace in any line
  
• Fixed primitives failing to be drawn in new submodels
  
• Fixed certain hang situations
  
• Avoid accessing Address Book to avoid scare dialog on 10.8
  

Hi all,

I'm trying to put together a Princess Leia minifigure. I've found the bun hair part (30409.dat) and the head (3626bp08.dat), but I'm struggling to find a torso piece. It seems that there are 3 possible Princess Leia torso parts:
973px411 - Hoth Jacket Pattern
973px303 - Brown Shirt Pattern
There is also a new Princess Leia minifigure featured in the set 7965 Millennium Falcon. This one is called "Princess Leia Organa minifigure"

Is anyone working on any of these parts, or could help me locate them.

BTW, I've recently added a Chewbacca Minifigure and Superman Minifigure to my website.

Thanks


Reuben
[email protected]
=====================================
Download 3D Lego models and other resources from:
http://www.pearse.co.uk/lego
=====================================

This came as a bit of a surprise to me, the official Lego part 89762 exists in neither the official parts list, nor in the parts tracker. I have several models that use this part that I want to use in my Lego CGI project. Is this because the part is too rounded to render in animation without hesitation? Are their not enough primitives to support this part? Is the part not selling physically?

Whatever the reason, unless I have the part, my Lego CGI project will be at a standstill. Please digitize this part, we want a complete library, right?

Oh, and yes, this is probably my first post, I'd like to be welcomed, unless I already posted before.

did you know...
...THIS?

http://twitter.com/schwarzblond/status/2...16/photo/1

I just noticed that the official parts restrictions document has a list restrictring what meta-command can be used in official parts:

http://www.ldraw.org/article/512#meta

Since !TEXMAP and !: aren't on that list, they aren't yet officially allowed. I realize that the parts tracker isn't yet ready to accept files with !TEXMAP. Should the restrictions document be updated before the tracker, or the other way around?

Almost all official and unofficial meta-commands that I've seen are written in all-caps (the exceptions being 'Name' and 'Author', presumably for historical reasons). I can't find anything which specifies that this is mandatory when defining new metas, so does anyone know:

- is it in fact mandatory, or just convention?
- should parsers be case-sensitive or case-insensitive when dealing with metas?


(As an aside, 'meta' is not an acronym, so should not be written as 'META' as it seems to be throughout the specs...)

I'm seeing the following:

/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1593 - trigger_error
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1415 - _fetch_resource_info
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1261 - _compile_resource
/usr/www/users/peeron/ldraw/files/plugins/function.global_content.php:22 - fetch
/usr/www/users/peeron/ldraw/files/tmp/templates_c/67^%%70^707^707A8977%%content%3Acontent_en.php:114 - smarty_cms_function_global_content
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1263 - include
/usr/www/users/peeron/ldraw/files/plugins/function.content.php:121 - fetch
/usr/www/users/peeron/ldraw/files/tmp/templates_c/%%B2^B23^B2322195%%tpl_top%3A28.php:9 - smarty_cms_function_content
/usr/www/users/peeron/ldraw/files/lib/smarty/Smarty.class.php:1263 - include
/usr/www/users/peeron/ldraw/files/index.php:268 - fetch
string(63) "Smarty error: unable to read resource: "globalcontent:BadLinks""


It appears just after the list of meta-commands.

Please vote on the proposal below. Please modify the Subject to include your name and vote, in addition to giving your vote in the text.

Quote:This texture will remain in effect until:

• An END is given within the current file
  
• The file in which the START is located ends
  
• A STEP command is reached
  

The texture will remain active when processing an included file unless overridden within that file.

Quote:The END command stops using the current texture and restores the previous texture to current status. This means that nested commands with START will form a stack of textures and the END command will pop those textures. However, END cannot appear in a different file from START. If an END command is given in a sub file without a START having been given in that same file, the END stops the use of a texture specified in a calling file, then that texture will be restored to use when the sub file is exitedhas no effect.