On 06/11/2017 11:34, Kenneth wrote:
> "cbpypov" <nomail@nomail> wrote:
> 
>>
>> Hey Kenneth! Somehow I do not exactly know what you are talking about :) With my
>> small fixes SharkD's code works perfectly for me and it does just fine in
>> keeping e.g. text fixed in front of the camera while moving it. But somehow, I
>> do not see your point: (1) in a single POV-Ray render the camera is always
>> static, right? (2) SharkD's code doesn't make _any_ assumption about the camera
>> position, so how should it *know* where the camera is? Since it is agnostic, it
>> _must_ work in an animation, too ... did I miss something?
> 
> Hmm; I think I'm beginning to see your point (and correct me if I'm wrong): An
> animation with a moving camera is still just a series of discrete static images
> strung together, each with its own 'static' camera position for that frame-- and
> the code does work successfully on individual images with a 'static' camera
> (which is the *only* camera position being rendered at the moment.) So the code
> apparently doesn't need to know or even care about where the *camera* will be
> for the next frame.
> 

Going from memory. You are right. The parameters for the macro are 
calculated each frame.

StephenS devised a method to return them in Bishop3D. So they could be 
used in additional code.


-- 

Regards
     Stephen

Post a reply to this message