The Persistence of Vision Raytracer (POV-Ray).
This is the Bug Tracking System for the POV-Ray project. Before opening a new task, please read How to make a Bug Report
Please do not issue bugs reports against versions earlier than 3.6.
FS#158 - Antialias Gamma reporting error
Attached to Project:
POV-Ray
Opened by Jim Holsenback (jholsenback) - Tuesday, 20 July 2010, 23:36 GMT
Last edited by Jim Holsenback (jholsenback) - Sunday, 26 September 2010, 00:51 GMT
Opened by Jim Holsenback (jholsenback) - Tuesday, 20 July 2010, 23:36 GMT
Last edited by Jim Holsenback (jholsenback) - Sunday, 26 September 2010, 00:51 GMT
|
Details
value is erroneously clipped to the range 0..1 before being displayed |
This task depends upon
Closed by Jim Holsenback (jholsenback)
Sunday, 26 September 2010, 00:51 GMT
Reason for closing: Fixed
Sunday, 26 September 2010, 00:51 GMT
Reason for closing: Fixed
fixed with change #5071
pulled and tested #5071 (works ok fine) ... danke
As a follow-up: was struggling with some AA issues with my current project. While trying to trouble-shoot the cause I noticed a behavior I can't explain. The reporting now works just fine (reports my command-line settings properly), however when I try to specify Antialias_Gamma=off it doesn't parse, but WILL pass the -AG option (no nag) while STILL reporting that it's on at my specified value. Was it intended to have AG on all the time, when any AA is used (at the default or user specified value) ... shouldn't I be able to turn this option off if I wish?
"Neutral" behaviour can be achieved with Antialias_Gamma=1.0; I'm not sure why -AG doesn't give a warning. Maybe it should be changed so that Antialias_Gamma=0.0 (or =off, or -AG) is interpreted as Antialias_Gamma=1.0.
Displayed value is now 2.5 for benchmark. Looks good.
(beta 39 from sources (via perforce))
I would like to suggest to close.