this topic is intended for sharing Classic Town sets

I'm drawing some of my mocs in MLcad, and i'd like to use the exact part number for each piece. But there are some parts that i cannot find but of which exists an almost identical part.
For example my moc contains part n 61252, but it doesn't exists in LDraw, so i used part 6019 instead.
Maybe the part has yet to be added to LDraw Part Library? Or is it something wanted?

It's a pity that i can't add the correct part as some sites like Rebrickable can calculate what MOC you can build with the pieces you have and this kind of things break the functionality.

Thanks

post Fabuland models below this topic

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.

• Update the LDraw file format version number to 1.1.0. Note: 1.1.0 was chosen instead of 1.0.2, as this change was thought to be too big for such a minor version number change.
  
• Add the following sub-section under the "Basic parsing / file content" sub-section of the "LDraw Files" section:
  

  Quote:Multi-Part Dat (MPD)
  Any LDraw file, no matter its file extension, may be a Multi-Part Dat file (file with other files wrapped inside). This is done using the MPD Language Extension.

• Change the "MPD Statements" sub-section of the "META Commands" section to be as follows:
  

  Quote:Support for the MPD Language Extension is required.

Quote:To reiterate: No other meta-commands (including the MPD meta-command) are allowed in official parts.

I'm still working on the flexable parts functionality, I'm currently trying to roundup / implement all needed options for a bendable part.

Thing is I might be overdoing it somewhat, so I was wondering what the experienced LSynth and or part authors might think.

Current meta/option processing allows for something like this:



This 'path' has two sets of options (one of which is displayed in the dialog) that describe how the segments must be placed etc.

The thing I might be obsessing over is the fact the chain links still don't bend 'naturally' in my opinion (because they are actually double jointed in real life), but I might be overdoing it quality wise

Anyone think there need to be additional options to solve this (e.g. possibility to include prev/next segment for cur segment placement in order to account for the double joint etc).

I think the current options are quite understandable, but I'm happy to explain them more if needed.

Just looking for some fresh perspectives

edit: some more examples:

Hello all,

I am looking for this part 64647: Minifig, Plume Feather Triple Compact / Flame / Water
http://www.bricklink.com/catalogItem.asp?P=64647
I know it exists because I had it once and used here
https://sites.google.com/site/workingwit...ons/cowboy
Anyone know what has happened to it?
I cannot seem to find it at the partstracker either.
Tnx!

Jaco

It seems that color code 82, metallic gold, was changed in latest ldconfig.ldr. It now looks dark and brownish (it could be a convincing copper color!). Is this intended? what color code should I use to get the right color in patterns or gold painted parts?
#DBAC34 -> #8C5C20

4838 - Mini Vehicles - Carrier and Car

Attached Files

  4838 - Mini Vehicles - Carrier and Car.mpd (Size: 5.19 KB / Downloads: 4)

is there some Javascript "tricking" done at the multiline textbox for posting here in the forums...?

As soon as a post uses more than 1 line, I am not able to use the normal cursor positioning mechanism gestures on my Android tablet's native browser to edit the posted text.
i especially cannot position the cursor after the last char of the last line once i have jumoed somewhere else.
this is extremely annoying because it forces me to never go back to the text beginning to correct something, because i will never again be able to continue writing at the end.
I suggest to search that Javascript magic and simply throw it away.
The textbox shiuld work and behave like any other textbox on the inet.
I suspect that the cursor once is allowed to be at the end, hut then some script kicks in and re-puts it to somewhere else.

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: PartDescription is the descriptive name of the part (limited to 64 characters). If the part is good enough for public use, but has some deficiencies that need to be addressed, the text " (Needs Work)" (without the quotation marks) can be added to the end of the description. Please note that the full description including " (Needs Work)" is limited to 64 characters, so this decreases the usable portion of the description to 51 characters. If the description includes "(Needs Work)", a comment must be added to the file immediately following the official header describing the work that needs to be done.