### Appendix A.7
Conditions for Distribution of Custom Versions

The user is granted the privilege to modify and compile the source code for their own personal use in any fashion they see fit. What you do with the software in your own home is your business.

If the user wishes to distribute a modified version of the software, documentation or other parts of the package (here after referred to as a custom version) they must follow the provisions given below. This includes any translation of the documentation into other languages or other file formats. These license provisions have been established to promote the growth of POV-Ray and prevent difficulties for users and developers alike. Please follow them carefully for the benefit of all concerned when creating a custom version.

No portion of the POV-Ray source code may be incorporated into another program unless it is clearly a custom version of POV-Ray that includes all of the basic functions of POV-Ray.

All executables, documentation, modified files and descriptions of the same must clearly identify themselves as a modified and unofficial version of POV-Ray. Any attempt to obscure the fact that the user is running POV-Ray or to obscure that this is an unofficial version expressly prohibited.

You must provide all POV-Ray support for all users who use your custom version. You must provide information so that user may contact you for support for your custom version. The POV-Ray Team is not obligated to provide you or your users any technical support.

Include contact information in the DISTRIBUTION_MESSAGE macros in the source file optout.h and insure that the program prominently displays this information. Display all copyright notices and credit screens for the official version.

Custom versions may only be distributed as freeware. You must make all of your modifications to POV-Ray freely and publicly available with full source code to the modified portions of POV-Ray and must freely distribute full source to any new parts of the custom version. The goal is that users must be able to re-compile the program themselves and to be able to further improve the program with their own modifications.

You must provide documentation for any and all modifications that you have made to the program that you are distributing. Include clear and obvious information on how to obtain the official POV-Ray.

The user is encouraged to send enhancements and bug fixes to the POV-Ray Team, but the team is in no way required to utilize these enhancements or fixes. By sending material to the team, the contributor asserts that he owns the materials or has the right to distribute these materials. He authorizes the team to use the materials any way they like. The contributor still retains rights to the donated material, but by donating, grants unrestricted, irrevocable usage and distribution rights to the POV-Ray Team. The team doesn't have to use the material, but if we do, you do not acquire any rights related to POV-Ray. The team will give you credit as the creator of new code if applicable.

Include a copy of the povlegal.doc document.

### Appendix A.8
Conditions for Commercial Bundling

Vendors wishing to bundle POV-Ray with commercial software (including shareware) or with publications must first obtain explicit permission from the POV-Ray Team. This includes any commercial software or publications, such as, but not limited to, magazines, cover-disk distribution, books, newspapers, or newsletters in print or machine readable form.

The POV-Ray Team will decide if such distribution will be allowed on a case-by-case basis and may impose certain restrictions as it sees fit. The minimum terms are given below. Other conditions may be imposed.

* | Purchasers of your product must not be led to believe that they are paying for POV-Ray. Any mention of the POV-Ray bundle on the box, in advertising or in instruction manuals must be clearly marked with a disclaimer that POV-Ray is free software and can be obtained for free or nominal cost from various sources.
* | Include clear and obvious information on how to obtain the official POV-Ray.
* | You must provide all POV-Ray support for all users who acquired POV-Ray through your product. The POV-Ray Development Team is not obligated to provide you or your customers any technical support.
* | Include a credit page or pages in your documentation for POV-Ray.
* | If you modify any portion POV-Ray for use with your hardware or software, you must follow the custom version rules in addition to these rules.
* | Include contact and support information for your product.
* | Include a full user package as described above.

### Appendix A.9
Retail Value of This Software

Although POV-Ray is, when distributed within the terms of this agreement, free of charge, the retail value (or price) of this program is determined as US $20.00 per copy distributed or copied. If the software is distributed or copied without authorization you are legally liable to this debt to the copyright holder or any other person or organization delegated by the copyright holder for the collection of this debt, and you agree that you are legally bound by the above and will pay this debt within 30 days of the event.

However, none of the above paragraph constitutes permission for you to distribute this software outside of the terms of this agreement. In particular, the conditions and debt mentioned above (whether paid or unpaid) do not allow you to avoid statutory damages or other legal penalties and does not constitute any agreement that would allow you to avoid such other legal remedies as are available to the copyright holder.

Put simply, POV-Ray is only free if you comply with our distribution conditions; it is not free otherwise. The copyright holder of this software chooses to give it away free under these and only these conditions.

For the purpose of copyright regulations, the retail value of this software is US $20.00 per copy.

### Appendix A.10
Other Provisions

The team permits and encourages the creation of programs, including commercial packages, which import, export or translate files in the POV-Ray Scene Description Language. There are no restrictions on use of the language itself. We reserve the right to add or remove or change any part of the language.

"POV-Ray", "Persistence of Vision", "POV-Ray Team" and "POV-Help" are trademarks of the POV-Ray Team.

While we do not claim any restrictions on the letters "POV" alone, we humbly request that you not use POV in the name of your product. Such use tends to imply it is a product of the POV-Ray Team. Existing programs which used "POV" prior to the publication of this document need not feel guilty for doing so provided that you make it clear that the program is not the work of the team nor endorsed by us.

### Appendix A.11
Revocation of License

VIOLATION OF THIS LICENSE IS A VIOLATION OF COPYRIGHT LAWS. IT WILL RESULT IN REVOCATION OF ALL DISTRIBUTION PRIVILEGES AND MAY RESULT IN CIVIL OR CRIMINAL PENALTY.

Such violators who are prohibited from distribution will be identified in this document.

In this regard, "PC Format", a magazine published by Future Publishing, Ltd. in the United Kingdom, distributed incomplete versions of POV-Ray 1.0 in violation the license which was effect at the time. They later attempted to distribute POV-Ray 2.2 without prior permission of the POV-Ray Team in violation the license which was in effect at the time. There is evidence that other Future Publishing companies have also violated our terms. Therefore "PC Format", and any other magazine, book or CD-ROM publication owned by Future Publishing is expressly prohibited from any distribution of POV-Ray software until further notice.

### Appendix A.12
Disclaimer

This software is provided as is without any guarantees or warranty. Although the authors have attempted to find and correct any bugs in the package, they are not responsible for any damage or losses of any kind caused by the use or misuse of the package. The authors are under no obligation to provide service, corrections, or upgrades to this package.

### Appendix A.13
Technical Support

We sincerely hope you have fun with our program. If you have any problems with the program, the team would like to hear about them. Also, if you have any comments, questions or enhancements, please contact the POV-Ray Team on the CompuServe Information Service in the GO POVRAY forum or check us out on the internet at http://www.povray.org or ftp.povray.org. The USENET group comp.graphics.rendering.raytracing is a great source of information on POV-Ray and related topics.

License enquiries should be made via email and limited technical support is available via email to:

       Chris Young
       POV-Ray Team Coordinator
       CIS: 76702,1655
       Internet 76702.1655@compuserve.com

The following postal address is only for official license business and only if email is impossible.

We do not provide technical support via regular mail, only email. We don't care if you don't have a modem or online access. We will not mail you disks with updated versions. Do not send money.

       Chris Young
       3119 Cossell Drive
       Indianapolis, IN 46224 U.S.A.

The other authors' contact information may be found in section "Authors" (see also "Postcards for POV-Ray Team Members").

### Appendix B
Authors

Following is a list in alphabetic order of all people who have ever worked on the POV-Ray Team or who have made a note-worthy contribution. If you want to contact or thank the authors read the sections "Contacting the Authors" and "Postcards for POV-Ray Team Members".

    Claire Amundsen
    (Tutorials for the POV-Ray User Guide)

    Steve Anger
    (POV-Ray 2.0/3.0 developer)
    CIS: 70714,3113
    Internet: sanger@hookup.net

    Randy Antler
    (IBM-PC display code enhancements)

    John Baily
    (RLE targa code)

    Eric Barish
    (Ground fog code)

    Dieter Bayer
    (POV-Ray 3.0 developer and docs coordinator)
    CIS: 104707,643

    Kendall Bennett
    (PMODE library support)

    Steve Bennett
    (GIF support)

    Jeff Bowermaster
    (Beta test)

    David Buck
    (Original author of DKBTrace)
    (POV-Ray 1.0 developer)

    Chris Cason
    (POV-Ray 2.0/3.0 developer, POV-Help, Windows port)
    Internet (preferred): povray@mail.oaks.com.au or Chris.Cason@povray.org
    CIS: 104706,3166

    Aaron Collins
    (Co-author of DKBTrace 2.12)
    (POV-Ray 1.0 developer)

    Chris Dailey
    (POV-Ray 3.0 developer)
    CIS:

    Steve Demlow
    (POV-Ray 3.0 developer)
    CIS:

    Andreas Dilger
    (POV-Ray 3.0 developer)
    Internet: adilger@enel.ucalgary.ca
    WWW: http://www-mddsp.enel.ucalgary.ca/People/adilger/

    Joris van Drunen Littel
    (Mac beta tester)

    Alexander Enzmann
    (POV-Ray 1.0/2.0/3.0 developer)
    CIS: 70323,2461
    Internet: xander@mitre.com

    Dan Farmer
    (POV-Ray 1.0/2.0/3.0 developer)
    CIS: 74431,1075

    Charles Fusner
    (Tutorials for the POV-Ray User Guide)

    David Harr
    (Mac balloon help and palette code)

    Jimmy Hoeks
    (Help file for Windows user interface)

    Terry Kanakis
    (Camera fix)

    Kari Juharvi Kivisalo
    (Ground fog code)

    Adam Knight
    (Mac beta tester, Mac Apple Guide developer)
    CIS:

    Lutz Kretzschmar
    (IBM-PC display code [SS24 truecolor], part of the anti-aliasing code)
    CIS: 100023,2006

    Charles Marslett
    (IBM-PC display code)

    Pascal Massimino
    (Fractal objects)

    Jim McElhiney
    (POV-Ray 3.0 developer)
    CIS:

    Robert A. Mickelsen
    (POV-Ray 3.0 docs)
    CIS: 71042,751
    Internet: ram@iu.net
    WWW: http://www.websharx.com/ kahuna

    Mike Miller
    (Artist, scene files, stones.inc)
    CIS: 70353,100

    Douglas Muir
    (Bump maps, height fields)

    Joel NewKirk
    (Amiga Version)
    CIS: 102627,1152

    Jim Nitchals
    (Mac version, scene files)

    Paul Novak
    (Texture contributions)

    Dave Park
    (Amiga support, AGA video code)

    David Payne
    (RLE targa code)

    Bill Pulver
    (Time code, IBM-PC compile)

    Anton Raves
    (Beta tester, helping out on several Mac thingies)
    CIS: 100022,2603

    Dan Richardson
    (Docs)
    CIS:

    Tim Rowley
    (PPM and Windows-specific BMP image format support)
    Internet: trowley@geom.umn.edu

    Robert Schadewald
    (Beta tester)
    CIS:

    Eduard Schwan
    (Mac version, mosaic preview, docs)
    CIS: 104706,3276 or POVRAYMAC or ESPSW
    Internet: povraymac@compuserve.com or espsw@compuserve.com
    WWW: http://ourworld.compuserve.com/homepages/povraymac

    Robert Skinner
    (Noise functions)

    Erkki Sondergaard
    (Scene files)
    CIS:

    Zsolt Szalavari
    (Halo code)
    Internet: zsolt@cg.tuwien.ac.at

    Scott Taylor
    (Leopard and onion textures)

    Timothy Wegner
    (Fractal objects, PNG support)
    CIS: 71320,675
    Internet: twegner@phoenix.net

    Drew Wells
    (POV-Ray 1.0 developer, POV-Ray 1.0 team coordinator)

    Chris Young
    (POV-Ray 1.0/2.0/3.0 developer, POV-Ray 2.0/3.0 team coordinator)
    CIS: 76702,1655

### Appendix C
Contacting the Authors

The POV-Team is a collection of volunteer programmers, designers, animators and artists meeting via electronic mail on Compuserve's POVRAY forum (GO POVRAY).

The POV-Team's goal is to create freely distributable, high quality rendering and animation software written in C that can be easily ported to many different computers.

If you have any questions about POV-Ray, please contact

      Chris Young
      POV-Team Coordinator
      CIS: 76702,1655
      Internet: 76702.1655@compuserve.com

We love to hear about how you're using and enjoying the program. We also will do our best try to solve any problems you have with POV-Ray and incorporate good suggestions into the program.

If you have a question regarding commercial use of, distribution of, or anything particularly sticky, please contact Chris Young, the development team coordinator. Otherwise, spread the mail around. We all love to hear from you!

The best method of contact is e-mail through CompuServe for most of us. America On-Line and Internet can now send mail to CompuServe, also, just use the Internet address and the mail will be sent through to CompuServe where we read our mail daily.

Please do not send large files to us through the e-mail without asking first. We pay for each minute on CompuServe and large files can get expensive. Send a query before you send the file, thanks!

### Appendix D
Postcards for POV-Ray Team Members

If you want to personally thank some of the POV-Ray Team members you can send them a postcard from wherever you are. To avoid invalid addresses from floating around (in case some of us move) the addresses listed below (in alphabetical order) are only valid until the given date.

      Dieter Bayer
      Taeublingstr. 26
      91058 Erlangen
      Germany                                    (until 31. March 1998)

      Chris Cason                                (Windows version)
      PO Box 407
      Williamstown
      Victoria 3016
      Australia                                  (until 31. December 1998)

      Joel NewKirk
      255-9 Echelon Rd
      Voorhees, NJ, USA, 08043                   (until ---)

      Eduard Schwan                              (Macintosh version)
      1112 Oceanic Drive
      Encinitas, California, USA, 92024-4007     (until 30. June 1998)

You should also be aware that we do not answer any questions asked by regular mail or phone, we only reply to e-mails. Send any questions you have to the e-mail address mentioned in section "Contacting the Authors".

### Appendix E
Credits

Credits for providing contributions to the user documentation go to (in alphabetical order):

    Charles Fusner
    (Blob, lathe and prism tutorial)

### Appendix F
Tips and Hints

### Appendix F.1
Scene Design Tips

There are a number of excellent shareware CAD style modelers available on the DOS platform now that will create POV-Ray scene files. The online systems mentioned elsewhere in this document are the best places to find these.

Hundreds of special-purpose utilities have been written for POV-Ray: data conversion programs, object generators, shell-style launchers and more. It would not be possible to list them all here, but again, the online systems listed will carry most of them. Most, following the POV-Ray spirit, are freeware or inexpensive shareware.

Some extremely elaborate scenes have been designed by drafting on graph paper. Raytracer Mike Miller recommends graph paper with a grid divided in tenths, allowing natural decimal conversions.

Start out with a boilerplate scene file, such as a copy of basicvue.pov, and edit that. In general, place your objects near and around the origin with the camera in the negative z-direction, looking at the origin. Naturally, you will break from this rule many times, but when starting out, keep things simple.

For basic, boring, but dependable lighting, place a light source at or near the position of the camera. Objects will look flat, but at least you will see them. From there, you can move it slowly into a better position.

Next Section
Table Of Contents