This group is for the reporting of verifiable bugs. It is not for
general discussion about POV-Ray bugs - please take that to
povray.general. We would like to keep the volume of traffic here down.

Are you using the latest version of POV-Ray available for your platform?
There is a list of bug fixes for the most recent versions of POV-Ray
posted in the povray.announce.frequently-asked-questions group.

You may place properly-worded bug reports here (make sure you include
all relevant material AND ensure that you read the group first, to make
sure it's not already reported).

Do not expect a reply from the POV-Team.

The minimum information to include in your bug report is:

The version number of POV-Ray you are using, such as v3.1e, v3.1g, etc.
You can see this by selecting About from the Help Menu (in POV-Ray for
Windows).

Your operating system. It is surprising how many people fail to provide
this basic piece of information. We need to know what version of
Windows, Mac, or unix variant you are running.

Your computer; what processor and how much memory.

A complete description of the problem and what led up to it. It will
make it a lot easier to track down if you can include a scene file that
will cause the problem. Please remove non-essential parts until you have
the minimum scene file that will reproduce the problem (but do include
your camera and light source!).


-- 
Alan
--------------------------------------------------------------------
http://www.povray.org - Home of the Persistence of Vision Ray Tracer
news.povray.org - where POV-Ray enthusiasts around the world can get
together to exchange ideas, information, and experiences with others
--------------------------------------------------------------------

Post a reply to this message

This post is very relevant since it seems to be a trend that whenever
someone doesn't know why something doesn't work like he wants, he thinks it
must be a bug and posts an article here.
  When something doesn't work, please post an article to povray.general
first. If it was just a mistake or a known feature (like the coincident
surfaces problem, which is not a bug) you will not be overloading this
group.
  Only after a discussion in .general and after making the conclusion that
it really is a bug, you can post a proper bug report here.

-- 
main(i,_){for(_?--i,main(i+2,"FhhQHFIJD|FQTITFN]zRFHhhTBFHhhTBFysdB"[i]
):5;i&&_>1;printf("%s",_-70?_&1?"[]":" ":(_=0,"\n")),_/=2);} /*- Warp -*/

Post a reply to this message