Render Field of View is stuck at 65.5 no matter what I change
it to in Moray 3.3a...I COULD go in and edit the POV file,
but I change something and test-render it, I don't want to
have to keep jumping back and forth to the text editor every
2 seconds. ^_^;

-- 
Tim Cook
http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

"Timothy R. Cook" wrote:
> 
> Render Field of View is stuck at 65.5 no matter what I change
> it to in Moray 3.3a...

Use POV-Ray v3.1 until we get the behaviour fixed in 3.5. There is not
much Lutz can do about it at the moment.

-- 
Ken Tyler

Post a reply to this message

Ken wrote:
> Use POV-Ray v3.1 until we get the behaviour fixed in 3.5. There
> is not much Lutz can do about it at the moment.

I'd much rather deal with being restricted to one FOV than stop
using 3.5...I'm addicted, you see...I can't quit anytime I want.

-- 
Tim Cook
http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

Hi Timothy R. Cook, you recently wrote in moray.win:

> Render Field of View is stuck at 65.5 no matter what I change
> it to in Moray 3.3a...
Hmmm, I don't quite understand. If you change the angle number in the
POV script, it does use a different FOV? Have you actually looked at
the generated POV file and Moray always writes the same number behind
the angle word, no matter what you do in Moray? I don't really see how
that can happen.....

- Lutz
  email : lut### [at] stmuccom
  Web   : http://www.stmuc.com/moray

Post a reply to this message

Lutz Kretzschmar wrote:
> Have you actually looked at the generated POV file and Moray
> always writes the same number behind the angle word, no matter
> what you do in Moray? I don't really see how that can happen.....

Moray writes the angle I set in the FOV box, but POV 3.5b10
doesn't pay attention to it.  This might be because of the
changed camera syntax in b10...dunno.

-- 
Tim Cook
http://personal.lig.bellsouth.net/lig/z/9/z993126

-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GFA dpu- s: a?-- C++(++++) U P? L E--- W++(+++)>$
N++ o? K- w(+) O? M-(--) V? PS+(+++) PE(--) Y(--)
PGP-(--) t* 5++>+++++ X+ R* tv+ b++(+++) DI
D++(---) G(++) e*>++ h+ !r--- !y--
------END GEEK CODE BLOCK------

Post a reply to this message

From: "Timothy R. Cook" <tim### [at] scifi-fantasycom>
> Moray writes the angle I set in the FOV box, but POV 3.5b10
> doesn't pay attention to it.  This might be because of the
> changed camera syntax in b10...dunno.

The reason is that angle keyword must be after look_at keyword in the new
camera syntax made by beta10.

The only way to make it work right in the beta10 is to edit manually the pov
file generated by Moray, though there are two ways:

1.- Put this before your camera statement: #version 3.1 and this after:
#version 3.5.
2.- Cut the line that holds the angle keyword and paste it after the look_at
keyword (this is the one I use).

The solution would be to change the way Moray exports the camera statement
in the pov file, so the angle keyword went at the end of it, even though the
camera statement may change in future betas (or so I've heard).

Hope this helps.

Bye

Txemi Jendrix
tji### [at] euskalnetnet
http://www.geocities.com/txemijendrix

Post a reply to this message