At:

http://suso.suso.org/visual/3d/neatobject7.mpg  (I discovered the 2MB 
posting limit.
 
Isn't that a bit ridiculous)

  is an animation I made of the object shown on the website:

http://www.f-lohmueller.de/pov_tut/csg/povcsg4e.htm

Basically I just wanted to determine how the object was made without 
reading his example code
and learn how to do morphing animations in pov-ray.  In the end, I 
started doing stuff with
camera movement radiosity and so on.  But I am having trouble getting 
the camera to track
to <0,0,0> as it moves.  Can anyone help me fix this problem?  Also 
attached is my pov
and ini files.

Thanks,
Suso

Post a reply to this message

Attachments:
Download 'us-ascii' (1 KB) Download 'us-ascii' (4 KB)

Suso Banderas <sus### [at] susoorg> wrote:
> But I am having trouble getting the camera to track
> to <0,0,0> as it moves.

  Either you want something else, or there's something which I don't get.

  Have you tried simply defining the look_at vector as <0,0,0> in all
camera definitions?

-- 
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -

Post a reply to this message

On Tue, 21 Jan 2003 17:18:35 +0000, Warp wrote:

> Suso Banderas <sus### [at] susoorg> wrote:
>> But I am having trouble getting the camera to track
>> to <0,0,0> as it moves.
> 
>   Either you want something else, or there's something which I don't get.
> 
>   Have you tried simply defining the look_at vector as <0,0,0> in all
> camera definitions?

Yes I have tried that.

For the camera move part, this is what I have:

    camera {
        location <-1.25, 1.25, -2>
        translate <1.25*clock2, -1.25*clock2, 0.75*clock2>
        look_at <0*clock, 0*clock, 0*clock>
    }

Originally I tried

    camera {
        location <-1.25, 1.25, -2>
        look_at <0, 0, 0>
        translate <1.25*clock2, -1.25*clock2, 0.75*clock2>
    }

 But then I read the part in the PovRay documentation that mentioned
that some coordinates might not be read repeatedly if they happen
before a translate, so I tried putting the look_at after the translate. 
But that didn't head so I tried using a 0*clock method, thinking that
maybe it wouldn't read the look_at line again unless it had the word
clock in it.

  All, I'm trying to do is make the camera look at the same point as it
moves through space.  A simple camera track.

Thanks for your help.

Post a reply to this message

Suso Banderas <sus### [at] susoorg> wrote:
>     camera {
>         location <-1.25, 1.25, -2>
>         translate <1.25*clock2, -1.25*clock2, 0.75*clock2>
>         look_at <0*clock, 0*clock, 0*clock>
>     }

  Instead of translating the camera, add the translation vector to the
location vector.

  And by the way, 0*clock = 0.

-- 
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}//  - Warp -

Post a reply to this message

On Tue, 21 Jan 2003 18:20:03 +0000, Warp wrote:
 
>   Instead of translating the camera, add the translation vector to the
> location vector.

  Cool, that worked:

    camera {
        location <-1.25, 1.25, -2> + <1.25*clock2, -1.25*clock2, 0>
        look_at <0, 0, 0>
    }

  you can check out the fixed version here:

  http://suso.suso.org/visual/3d/neatobject9.mpg

>   And by the way, 0*clock = 0.

  Yes, I know that.  What I was thinking when I did that is that
perhaps povray wasn't seeing the translate line unless I put a clock
variable there, so it wouldn't hurt anything to put one there since I
wanted the camera to look at 0,0,0 anyways.

thanks for your help

Post a reply to this message