6426 - Super Cycle Center - Buggy

Attached Files

  6426 - Super Cycle Center - Buggy.ldr (Size: 1.67 KB / Downloads: 12)

Hello,
thanks a lot for the ldraw software tool: it's great.

Me and my colleaque thinking about writing a book about the new Lego mindstorms EV3 and now I am wondering how long it will take to have the new parts in ldraw? Any guesses? How long does it usually take?
Thanks, Christine

Following my first foray in uncharted texmap country, I made another try, this time using Eomer helmet.
The big problem is to create the image for texture map. The part is not flat, so despite rather good lighting, it's not uniform, and plenty of reflexions. Moreover, printing itself is full of smudges. So you have to redraw the image anyway...

So I tried to kill two birds with one stone, and use LDraw Patterns Creator to create the drawing. OK, LPC is certainly not the most handy vector drawing program, but with it I obtained "old style" triangle based texturing of the part for comparison (and usage with MLCad...)
The next step was to generate images from the LDraw model. Easy...
- Open it using LDView
- In LDView options, disable lighting and edge lines. Set the field of view to a very low angle value (0.1°).
- Save a snapshot from the directions you want to project, with a transparent background. Here from side:

- You may want to show all conditional lines and make another snapshot. This shows the facets limits and will help to properly crop the image.
- Using an image editor, remove all areas that use main color, and crop your file to the area needed for mapping. For the helmet, I used two projections, one from front, one from side.
Here is the compared result.

Front helmet is the textured one, back helmet is the triangle-based texturing. As you can see, the good point of texmap is that LDView can do its magic and give a nice, smooth result.
Out of curiosity, I generated another version of triangle textured subpart, this time with conditional lines everywhere to force smooth shading. Result is smoother, but not as good as texture map...


Now, texture maps have their own problems...
- I still find it very difficult to derive correct values for mapping parameters. Theoretically it's simple, practically it's another story (maybe it's just that I have not yet got the hang of it...). The method I use is to create helper triangles to materialize projection area and when they are right, copy the values in texmap meta:

- For some reason, LDView properly smooth texmapped mirrored subpart... but not the other side!

- Even though the images I used are relatively high resolution, edges are not so crisp, and there is a slight fringe effect. It seems that partial transparency causes some issue to LDView. Here is an enlarged snapshot, showing that areas in transition region is transparent, instead of merging with main color. I even tried to use completely hard edge around image (helmet2.dat in attached files), the transition area is reduced but still there.
.

Attached a zip file (renamed .txt to be able to post it here) containing the helmets...

Attached Files

  helmet.zip.txt (Size: 221.95 KB / Downloads: 3)

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