Thanks everyone for the camera help.

I've given up on the panoramic camera though. No matter what I set angle to
I get identical results. I guess it's just me.  :(

Post a reply to this message

On Sat,  3 Aug 2002 21:41:04 EDT, "Mike" <nomail@nomail> wrote:

>Thanks everyone for the camera help.
>
>I've given up on the panoramic camera though. No matter what I set angle to
>I get identical results. I guess it's just me.  :(

Here's an example using the #version work around:

#version 3.1;

camera {
  location -20*z
  look_at 0
  angle 20
  orthographic
}

#version 3.5;

It should work exactly as it did in POV-Ray 3.1.

If you don't want to do this, please re-read section 6.4.2.2 of the
manual, specifically this paragraph:

> If, in a perspective camera, you replace the perspective keyword by
> orthographic and leave all other parameters the same, you'll get an
> orthographic view with the same image area, i.e. the size of the image is
> the same. The same can be achieved by adding the angle keyword to an
> orthographic camera. A value for the angle is optional. So this second mode
> is active if no up and right are within the camera statement, or when the
> angle keyword is within the camera statement.

Hope this helps.

Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message

Thanks, but I'm not trying to recreate 3.1's behavior. I was asking about
keyword order, but I understand now that it doesn't matter.

What I'm confused about is section 6.2.4.6 of the docs state "The angle
keyword is used to determine the viewing angle." when referring to the
panoramic camera type.

I have a simple scene here:
camera{
  panoramic
  location     <0,0,-10>
  angle 170
}

light_source{
  <5,10,-15>
  color rgb<1,1,1>
}

#declare My_Cyl=cylinder{ -80*y 80*y .2 pigment{color
rgb<1,0,0>}finish{ambient 1}}
cylinder{My_Cyl}
cylinder{My_Cyl rotate<0,0,45>}
cylinder{My_Cyl rotate<0,0,90>}
cylinder{My_Cyl rotate<0,0,135>}


Now, no matter what angle value I use in the camera statement(I used 170
above) the scene will not change in way I can see. Is this an error in the
docs or something I'm just not seeing?

Post a reply to this message

Mike wrote:
>Thanks, but I'm not trying to recreate 3.1's behavior. I was asking about
>keyword order, but I understand now that it doesn't matter.
>
>What I'm confused about is section 6.2.4.6 of the docs state "The angle
>keyword is used to determine the viewing angle." when referring to the
>panoramic camera type.
>

Mike,

Thanks to Peter Popov, who pointed out
>
>there have been substantial changes to the camera code in 3.5 to
>eliminate any dependence on the order of keywords. The only
>requirement is that camera type goes first.

I had a look to the sources. It is clearly not your
fault, panoramic camera ignores the angle.

See the message "Camera Parameters, esp. angle"
I posted a minute ago.

Hermann

Post a reply to this message

Ichthyostega wrote:
>I had a look to the sources. It is clearly not your
>fault, panoramic camera ignores the angle.

Thanks!  This was true in 3.1 as well, but somehow I always figured it was
something I was doing wrong! I tried looking at the source, but I'm not
that experienced a programmer and I honestly can't follow much of it.

I've been trying to figure out default values for many things, and the
source hasn't helped me much...like yesterday I was trying to find the
default distance value for a rainbow. I gave up trying, but I know from
experimenting that it is greater than 10,000.   :)

Any recommendations on how to find things like default values in the source?

Post a reply to this message

On Mon,  5 Aug 2002 17:32:22 EDT, "Mike" <nomail@nomail> wrote:

>Any recommendations on how to find things like default values in the source?

Yes - look into parse.cpp :)


Peter Popov ICQ : 15002700
Personal e-mail : pet### [at] vipbg
TAG      e-mail : pet### [at] tagpovrayorg

Post a reply to this message