I'd like to ask if we could drop the 64 chars par title limit, please.

Which ancient software relies on that?

The current force of this limit leads to the effect that important keywords
of the title must be abbreviated, so they cannot be grepped properly anymore,
or left out completely.

All modern software should be able to treat a first line in the file of arbitrary length, IMHO.

I'd like to ask the LSC for a drop of this limit, please.

Hey,

Here is the new LPC 1.3.4.


Please uninstall older versions of this software before installing a new version.
Your configuration won't be deleted if you have already version greater than 1.3.1 installed on your machine.

Change log:

New features:

• The program imports subfiles of primitives
  
• The projection data import now parses linetype 2 and 5
  
• DAT filenames with spaces are supported
  
• You can press the Ctrl+C/X/V or Del key to change the text displayed in on-screen textboxes
  
• It is impossible to group triangles which are adjacent to an existing group
  
• The subfile import does inline all required subparts/primitives of the subfile
  
• The highlight around a selected triangle that exactly match a template triangle is shown
  
• Vertices from projection data remain locked
  

• LPC crashes if the user sets a custom colour in the toolbar which is not defined in LDConfig.ldr
  
• LPC crashes if the user makes excessive use of the "Merge to nearest line" functions.
  
• The undo/redo functions crash the application under certain circumstances and deform a pattern.
  
• It is possible to group triangles which are adjacent to an existing group (misfeature).
  

We currently have a numbering problem on the PT, and the more I think over it, the more complicated it gets.

Can we find a solution together?

LEGO itself has produced variants of their own bricks: "Mursten" and "Minitalia".

"Mursten" predates the bricks of today. For example, the 2x4 Brick existed in several "slotted" variants, e.g.
http://www.ldraw.org/cgi-bin/ptdetail.cg...3001mc.dat
The word "Mursten" is composed of the 2 danish words "mur" (meaning "wall") and "sten" (has the same origin as "stone",
but of course means "brick" here). Thus "mur sten" are "bricks to build a wall".



"Minitalia", as I learned today, was a variant of LEGO in the 1970's, which they had created to circumvent
importing rules of Italy at that time:
http://www.lucajuventino.altervista.org/...lia_EN.htm
http://lego.wikia.com/wiki/Minitalia
http://www.brickset.com/browse/themes/?theme=Minitalia



Both variants have differences in the appearance of the parts.
No problem for us, we can model them:
http://www.ldraw.org/cgi-bin/ptscan.cgi?q=mursten
http://www.ldraw.org/cgi-bin/ptscan.cgi?q=minitalia
We already also have "Minitalia" primitives - no problem so far.

However, we currently _have_ a problem with the part numbers:

For the "mursten" variant, the current status quo on the PT is to take the "normal" part number, append an "m" and then
"something else". Example: for the normal 2x4 brick (3001.dat), the parts tracker currently carries the mursten variants
3001ma.dat
3001mb.dat
3001mc.dat
3001md.dat
3001me.dat
, cf. http://www.ldraw.org/cgi-bin/ptscan.cgi?q=3001m

But for the "minitalia" variant, just an "a" gets appended:
3001a.dat
, cf. http://www.ldraw.org/cgi-bin/ptscan.cgi?q=minitalia

That's reasonable, because the "minitalia" variant 3001a.dat in fact is just a moulding variant of the 3001.dat.
If you see it this way, things could just stay as they are now.

But on the other hand, for LEGO most probably these parts never carried the number 3001,
because both required completely separate moulds.

I now see the numberings
3001.dat
3001ma.dat
3001a.dat
clashing. The "m" for example could mean "mursten" or "minitalia". I don't understand why "mursten" gets its "m",
and "minitalia" does not.

We have several opportunities here, as
- we have u.....dat numbers
- we don't have a 8.3 filename restriction anymore.
Thus, we have several solution alternatives:

(SOLUTION A)
leave things as they are now, i.e.:
"mursten" is "normal part number plus m plus something else"
"minitalia" is "normal part number plus a,b,c,d,e, ... moulding variant suffix"

(SOLUTION B)
use separate, new u.......dat numbers for "mursten" and "minitalia" parts

(SOLUTION C)
use long filenames and make e.g.
3001.dat
3001-minitalia.dat
3001-mursten-a.dat
3001-mursten-b.dat
3001-mursten-c.dat

My problem is: each day I think this over, I favor a different solution :-(((((
solution A is very simple
solution B is very systematic
solution C is very easy to understand

what should we do?
Is there a solution D which I forgot? Which one do you favor?

With the (currently 7 x 16) new minifig torsos in the Collectable Minifig series, the existing 973pXX naming convention cannot cope.

Please use 973pc[series : 1-7][sequence : 1-9,a-f].dat for these.

Hi Everyone. We started on eurobricks.com spreading the word about our idea of MinuteBot. But now we are much further than just spreading the word. We want to share the fun of building with the Base even before it is out, so we set up a design challenge. We call for all creative forces to join in the quest. To give a foretaste of the MinuteBot Base the last update was issued together with a set of 3 .dat files to use in LDraw (thanks to great deal of help we received through this forum). To prove it is not a commerial project everyone that submits a project, no matter how simple or advanced, is rewarded with a double up on the amount of Bases one pledged for. The challenge is for everyone, so please feel free to post and share the file with whoever interested.
Please see the details of the Happy Design Week and join in!
Get the file and share your design on http://www.kickstarter.com/projects/3780...sts/217507

Please spread the news.
Cheers!

I'm trying to recreate all Star Wars Models (except the ugly Technic and Mindstorms stuff) from 1999 till today. All models should be OMR compliant, some, like the Snowspeeder, need work since they require functions I haven't learned yet, like repositioning a part from one step to another, for example. If there are any errors, please tell me, so I can correct them.

Each Model will be posted in a separate posting inside this topic. The pictures shown may contain parts that differ from what you'll see, when you open the model. These are officially available parts which I rewrote and which are still, or soon will be, on the PT. So there's no need to add these to the model itself.

Due to a bug, the files are not working in LPub. In order to make them work you need to open them in a texteditor and search/replace

0 !LDRAW_ORG Unofficial_Model

with

0 whatever

if you want to replace it again when you're through with LPub, if not, just delete these lines.

Not LDraw based (yet), but pretty interesting: http://www.mecabricks.com/en/workshop/
See also discussion on Eurobricks

I found these parts in a lot of LEGO I bought used. The colors match Trans Neon Green and Trans Neon Red, but I didn't find them on bricklink etc.

Hello all i have made some files that contain custom Lsynth parts, and woundered if there is any way of adding a measurement/size of part to the instruction step of that part and also to the parts list?

Can someone also tell me if the new Ldraw installer has the new small turntable and the technic mini linear actuator part's in it?

I have attached a quick Lsynth file above.

Attached Files

  string 2.mpd (Size: 13.36 KB / Downloads: 0)

Maybe you'd like to look at some images
which I had used during the 12V train parts creation for parts update 2012-01.
I finally also got myself a brickshelf folder...





















play well
Steffen