|
 |
"Doctor John" <joh### [at] home com> wrote in message
news:4a38c76a$1@news.povray.org...
> Chris B wrote:
>> You're placing the object into the scene then scaling, translating and
>> rotating it.
>> You then use the non-scaled, non-translated and non-rotated object in
>> the trace command and position spheres on that.
>>
>
> So what you're saying is that trace is looking at the
> #declare Terrain_Obj statement, rather than the object{ Terrain_Obj}
> statement.
Indeed it is. Indeed they both are.
The object {Terrain_Obj} statement is just **using** the object called
'Terrain_Obj', much in the same way that the 'trace' function is taking it
as input. It doesn't change it at all, it just adds an object to the scene
that uses the previously declared object as the starting point, so any
transformations within the object statement won't change the 'Terrain_Obj'
object (unless you explicitly assign the results back to it using another
#declare statement).
Chris B.
Post a reply to this message
|
|
