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

Hi people.

As promised in another topic, I share with you my last little program:
JLDraw (on SourceForge).

Presentation topic on Eurobricks

Enjoy! (...and let me know what you think ;-) )

Mario

The following guidelines are in place concerning the requesting of parts:

Research the part you want

• Look up the part at Rebrickable and Bricklink for the part number/description.
  
• Do a search of the Official Library and Parts Tracker to see if the part you want already exists.
  
• Some parts have been released in digital form by LEGO (e.g. LDD, Unity). Please search this page digital-bricks.de for the part number. The part is available in raw, unprocessed LDraw format if there is a "DAT" link at the end of the line for the part number. If the line is green or yellow, it's already official or on the Parts Tracker and you may have missed it when searching above.
  
• Printed part codes (the suffix after the part number, e.g. p0004, pb004) do not match between reference sites. Keep this in mind when you are searching.
  

• LDraw.org is a loosely run, volunteer only project.  This means that while our parts authors are very competent, they have real lives and real commitments that must come before this project.  This also means that the part you request may take a while to be created (read months/years, not days) especially if the part is large, complex, and/or came out pre-building instruction app.
  
• Please consider authoring the part yourself, especially if you are under some kind of time constraint.
  

Not sure this is a request or just an observation.

But I noticed when you using the NXT plugs they look wrong when they are in their sockets.

In real life both the clip on the plug and the copper wires inside the socket will bend when accepting each other.

So maybe we need two versions of both?

Hi (again) all, people.

I'm still working on a simple Java renderer for LDraw models, and now I'm a little confused about part/filename/subfile/"0 FILE" MPD extension/etc. for case sensitivity.

- In "File Format 1.0.2" there are no statements about case-sensitivity for file names or line type "1". Only in "Direct color" ("hex values must be uppercase") and "File Type" (case insensitive).

- In "File Format Restrictions for the Official Library" under "LDraw Files/File Name" it states "While both upper and lower case letters are permitted in filenames, filenames are case-insensitive. Currently, all official parts are issued with upper-case only names." But in "complete.zip" official library all part/subpart/primitive names are lower-case!

- Zip files are case sensitive (and so are developer libraries to access Zip files), and when extract files in a case-sensitive file system use original-case filenames. Search file names in ZIP file is case sensitive, so it is important to know how a part/subpart/primitive file is named in official library: 3070b.DAT, 3070B.dat or 3070B.DAT are different.

- Looking at "MPD Language Extension", filename case isn't specified. But in a forum message (here) it is clearly stated that "And MPD file lookup probably shouldn't be case-sensitive, because no other filename lookups in LDraw files are case-sensitive".

So, my questions:
- Can I assume that in MPD-type file all internal references to sub-file can be case insensitive?
- Can I assume that part/subpart/primitives file names in Official library are all lowercase?
- LDR-type file with external reference to sub-file needs to be case-sensitive, because now almost all filesystem are case-sensitive. So, can I consider external referenze to sub-file are case-sensitive?

Thank you for your great work on LDraw libraries!

Mario
PS: when my Java viewer is ready I'll share it with you.