In article <3C4### [at] skynetbe> , Fabien Mosen 
<fab### [at] skynetbe>  wrote:

> And, given the number of potential broken scenes, isn't it more
> of a potential support problem than anything else ?

Yes, the bugs reported as job000208 and job000196.

job000196:

When "angle" keyword within camera statement appears after "panoramic"
keyword it is ignored. Report:
http://news.povray.org/povray.beta-test/19868/129184/

Solution: It appears the code was never designed to use "angle" for the
"panoramic" camera. With 3.5 the camera type (see job 208) is now enforced
and "angle" is always ignored. If this is not the desired behavior, change
the parsing code of "angle" to make direction adjustments for the
"panoramic" camera type as well.


job000208:

with orthographic camera objects disappear when "angle" keyword is used

Reported: http://news.povray.org/povray.beta-test/19674/

Solution: It turns out this never was a bug. 'angle' works exactly as
advertised in the manual.  The problem is the user specified the camera type
after the angle, which assumed it was applied to a perspective camera and
consequently changed the direction vector length, which makes it look like
the object disappears. Now, with version 3.5 specified the camera type has
to be the first thing in a camera statement. The default (which obviously
does not need to be specified) is still perspective, of course.


And there have been other problems with the unpredictable nature of camera.
Of course, there need to be further changes, but as nobody seems to know all
the possible combinations of keywords and their order, it is a rather
difficult task without breaking anything.  I still hope to come up with a
complete solution for beta 11, which will basically allow one order to fit
all needs, which should be possible.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message