Here are the models contained in the 8841 set. It's unfinished because some parts (particularly in the 8841+8700 model) are missing or unofficial. Includes flexible parts modeled with LSynth, could change that in the future.













8841+8700 attached in reply

Attached Files

  8841-1 - Desert Racer.mpd (Size: 70.91 KB / Downloads: 5)
  8841-2 - Desert Racer - Tractor.mpd (Size: 34.74 KB / Downloads: 4)
  8841-3 - Desert Racer - Chassis.mpd (Size: 3.62 KB / Downloads: 5)
  8841-4 - Desert Racer - Balance.mpd (Size: 3.24 KB / Downloads: 4)
  8841-5 - Desert Racer - Buggy.mpd (Size: 5.99 KB / Downloads: 4)

This forumis very anitquated it could use updating. May I suggest phpBB?

Hi,

I'm trying to compile LeoCAD ong GNU/Linux but I keep getting the following error:

/usr/bin/ld: obj/linux/system.o: undefined reference to symbol 'XQueryKeymap'
/usr/bin/ld: note: 'XQueryKeymap' is defined in DSO /usr/lib/libX11.so.6 so try adding it to the linker command line
/usr/lib/libX11.so.6: could not read symbols: Invalid operation
collect2: error: ld returned 1 exit status

What do I do?

Is this the famous LEGO design software?
http://www.youtube.com/watch?list=TLt8Ij...jupc#t=27s
Or is this just used to create the funny animation film with the firetruck?

When parts are used in assemblies (provided as such by LEGO, and impossible to separate in normal use) their description begins with ~ so they don't appear in part tree. LDraw user should use assembly shortcuts instead.

It seems that things are not completely clear, as discussions around this come up from time to time on PT. Here is my opinion about this.

• For assemblies without moving parts, it's simple: all parts composing the assembly are ~, and an assembly shortcut is provided (several shortcuts may be needed to account for different color combinations). Example: NXT light sensor 55969 shortcut, composed of ~parts 54732, 55972, 55816, 55970, 55966.
  
• For assemblies with moving parts, a shortcut should be provided for each mechanical entity. This way the LDraw user can compose its own assembly in any position. An overall assembly is provided as well, to simplify user life when default position is OK, and for bill of materials usage. Example: NXT motor has a case assembly 54715c01, and an axle hub assembly 54725c01. Case assembly 54715c01 is made of ~parts 54714, 54715, 54716, 54717 and 54732. Hub assembly 54725c01 is made of two 54725 ~parts. Complete motor assembly 53787 is made of 54715c01 + 54725c01
  
• In case one of the moving assemblies is reduced to a single part (eg. axle hub of PF motors), the description of this part is not tilded, so that the user can pick it easily to create his own position combination. For example, the small linear actuator has 3 sections moving independantly:
  - the body, assembly 92693c01, composed of ~parts 92693 and 92697
  - the rotating axle, single part not tilded 92695.
  - the piston, single part not tilded 92696.
  Two complete assemblies are provided, contracted and extended (92693c02 and 92693c03)
  

i can find no similar part. is it avaiable somehow?

bad robot arm

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.