######
     ###      ########   ####     ####   #      #
     # #      #      #  #    #   #    #  # #### #
     # #      # ###### #  ##  # #  ##  # # #  # #
     # #      # #      # #  ### # #  # # # ###  #
     # #      # ####   # #      # #  # # # #  # #
     # #      #    #   # # #### # #  # # #      #
     # #      # ####   # # #  # # #  # #  ######
     # #      # #      # # ## # # #  # #
     # ###### # ###### #  ##  # #  ##  #
     #      # #      #  #    #   #    #
     ######## ########   ####     ####

LEGO POV-Ray include readme file  --David Fontaine
Unzips to approx. 5 to 6 Megs.

[ DISCLAIMER ]

I would like to point out that I did not originally intend to release
these files, and as such, they may be a little sloppy and take some
"getting used to".

Note that many of these were modelled in hard-code POV while I was still
learning the basics. As such, there may be inconsistencies or glitches
in some of the pieces. Inconsistencies would be like pieces that aren't
rounded off on the edges and whatnot. Measurement-wise, however, all the
pieces should fit together properly. Glitches would be like coincident
surfaces, interior surfaces, etc. Also note that some of the very fancy
decorative pieces, I.E. crossbow, hat-feathers, etc, are not very
accurate, so don't complain that they should be .01 wider or that they
look bad up-close. I try to get as close as possible, but a few pieces
(like my forest-man hat) need a lot of work. Maybe someday when I'm not
so cheap or lazy I'll register a good modeller and learn how to use it.

[ FILE USAGE ]

I have tried to divide the pieces into categories with seperate files,
but beware I did this as I went along making each piece, later to find
that they have many other uses I overlooked. This means you may find a
boat piece in the castle file or something. Each file has a
table-of-contents thing at the top, so if you can't find a piece you're
looking for, check a different file. Also, I have nowhere near all the
pieces modelled. I did this because a file containing all known LEGO
pieces would never parse.

If you use my piece definitions, please give me credit in the text
accompanying your image (newsgroup post, readme file, etc). Remember
that LEGO is a registered trademark and should be spelled in all capital
letters.

I recommend you make a seperate directory under POV to unzip this into.

[ PIECE/SIZE/COLOR NOTATION ]

In my definitions, one LEGO unit is equal to one POV unit. A LEGO unit
being the spacing of the interlocking "bumps". Remember LEGO height
units have a 6:5 ratio with width units, so pieces are normally 1.2
POV-units high. Color brightness is adjusted so that normal indoor
lighting would be about White*1.5 total lightsource brightness in a
scene file.

To find the orientation of a piece, use the included LEGOTEST.POV scene
file and render in a low resolution.

Many of the image_map files (mostly just torso) are 24-bit bmps, so they
have no transparency. The areas where the color should show thorugh are
set to exactly the color in the texture definition. If you change colors
around you must change the bmp. Other image_map files are stored as GIF
and can be transparent.

Image_map file notation:
files starting with st_ are torso scans
files starting with fs are forest_man torso scans
files starting with sd_ are shield scans
files starting with fl_ are flag scans
files starting with cw_ are castle window scans
files starting with ct_ are octagonal-tower piece scans
any other scans have no special prefix

Image maps are made so that scaling it to the size of the surface of the
piece where it's to be applied (or slightly smaller) will give the
desired result. Use the LEGOTEST.POV to play around with image_maps
until they fit.
Note that many pieces using image_maps are predefined.

[ BUG/ERROR REPORTS ]

If you find a serious error in this file or any of the included files,
reply to this post. That way you can CHECK THAT OTHER PEOPLE HAVEN'T
REPORTED THE SAME THING. Keep in mind I have already explained these
files are in no way perfect. I do not want to hear "this piece looks
ugly". Bugs worth reporting would be like pieces that render
incorrectly. As for piece requests, I suppose you can send them if you
want, but I make no guarantee that I will, or even can, send you a
definition.

Post a reply to this message

Attachments:
Download 'us-ascii' (6 KB)