I tried to create it with LDPC, but i don't know how. I saw tutorial, but i didn't understand it.
I project to XY part i want to pattern, but when i export it back to xy it became planar.
Maybe someone has template of minifig head?
When I uploaded my Superman head I asked this question.
Quote
I think that we should find a nomenclature for the twosided heads.
I can find five previous parts:
3626bpq0.dat "Minifig Head Mummy Face 2-Sided with 2 Eyes / 1 Eye Pattern"
3626bpq1.dat "Minifig Head Mummy Face 2-Sided with 2 Eyes / Gold Death Mask"
3626bph4.dat "Minifig Head with Gregory Goyle/Harry Potter Pattern"
3626bph5.dat "Minifig Head with Vincent Crabbe/Ron Weasley Pattern"
3626bpsc.dat "Minifig Head with SW Grey Eyebrows & Implant Pattern"
I would like to add the word "2-Sided". But where, and how should it be written? Or not?
End quote
My suggestion now, when perhaps the 64-character ban is lifted, all two-sided heads must end with ".....2-Sided Pattern".
Hej,
I'm still reworking the official library.
Just a few minutes ago I opened 206b.dat. As I can see, this part is no longer used in any parts. It is more or less replaced by a newer one, but the dimension is a little bit different. What should I do, with this part? Create a "moved to" or mark it as obsolete or or or...
Christian Neumann created almost all parts from this theme and I think hi will create all patterns, bat I do not see any model made from them. I think it is unfairly to ignore such hard work.
I Created 7305. It is not OMR, but if some one want you can fix it.
I think it would be really nice to have a meta command to indicate the end of the official part header information (especially) but also headers in general. Just something simple like:
Code:
0 !ENDOFHEADER
That way codes like LDMakeList of LDFind can know which comments are useful notes for the header (eg. in a needs work file) and which are just separators of the different part components (eg. 0 // Studs).
Of all the meta commands ever this one (hopefully) should be the easiest
eg.
The ENDOFHEADER meta-command indicates that the header has ended, and that any software that processes the header can stop looking. It is not required.
Code:
0 Brick 1 x 4
0 Name: 3010.dat
0 Author: James Jessiman
0 !LDRAW_ORG Part UPDATE 2003-02
0 !LICENSE Redistributable under CCAL version 2.0 : see CAreadme.txt
0 BFC CERTIFY CW
0 !HISTORY 2001-10-26 [PTadmin] Official Update 2001-01
0 !HISTORY 2002-05-07 [unknown] BFC Certification
0 !HISTORY 2002-06-11 [PTadmin] Official Update 2002-03
0 !HISTORY 2002-12-12 [hafhead] New subparted version
0 !HISTORY 2003-08-01 [PTadmin] Official Update 2003-02
0 !HISTORY 2007-06-06 [PTadmin] Header formatted for Contributor Agreement
0 !HISTORY 2008-07-01 [PTadmin] Official Update 2008-01
0 // This file has been updated often
0 !ENDOFHEADER
0 // Include the sub file
1 16 0 0 0 1 0 0 0 1 0 0 0 1 s\3010s01.dat
0 // Add a quad on top
4 16 -40 0 -10 40 0 -10 40 24 -10 -40 24 -10
0
Is there a requirement for official parts that all edges of a part be 'coated' with a line or conditional line?
I read that some programs use the presence or absence of lines to determine which mesh vertices should be smoothed across triangles, but I didn't see anything in the part authoring spec about the requirement that lines be present.
Is having lines on the edges something so basic and obvious to everyone that it didn't need to be stated? :-)
I have created an MPD file and can't import it into MLCAD. Changing the extension to LDR doesn't seem to help.
My basic problem is that I have sub-assemblies that depend on other sub-assemblies (3 levels of nesting; the main model .LDR at the top level needs to include a .MPD file which itself is composed of two LDR files). As soon as I do "Multipart->Import model" it won't let me save as LDR. :-( I have to save that sub-assembly as MPD.
I need to save as LDR so that I can import the created LDR into the main model! Hope it's clear.
For a long time I've wanted there to be an .xml version of parts.lst containing not only the part and description, but also additional meta data. When Michael posted his fine looking LDFind today I had my final motivation to do something about it. Because a good Parts.xml would make searching so much easier.
As such LDMakeList 1.0 will make Parts.lst in the usual way, but will also make Parts.xml with a very simple format. I'd like some ideas of what should and shouldn't go into this format. Right now I'm wavering on 'License' for example.