In article <3a0d4139@news.povray.org>, Warp <war### [at] tagpovrayorg> 
wrote:

>   Why not? Wouldn't it be possible to apply the inverse transformation to
> the testing ray, exactly as with objects?

Currently, the transformation matrix is not stored in the glow. Adding 
it will slow rendering slightly(because of the additional evaluation of 
a transformation) and increase memory consumption by 32 doubles.


>   AFAIK pov3.5 will use some C++.

Which is why I said "yet". :-)


> : Besides, I still hate templates.
> 
>   Why? They are extremely useful.
...
>   What's so bad about templates?
>   The only bad thing I can imagine about them is that you get sometimes
> quite long error messages, but that's all.

Let me clarify: I have nothing against the idea of templates. I just 
think they could be done better in C++ than they were, perhaps by 
extending the existing preprocessor instead of adding another 
"meta-language".


> : Though I can't imagine why one would want to perform a binary search on 
> : glows, or what characteristics they would be sorted by...
> 
>   Location with respect to the camera?
>   It doesn't help with reflections and refractions, but when the glow is
> directly seen from the camera, if all the glows are sorted you could use
> some binary search to find the correct glows to test a lot faster.

A lot of work with a little gain that you only get some of the time. 
Most glows are "infinite", and the gain by "bounding" is pretty minor. 
Moving to a dynamically allocated array will probably give a bigger 
speed boost.

-- 
Christopher James Huff
Personal: chr### [at] maccom, http://homepage.mac.com/chrishuff/
TAG: chr### [at] tagpovrayorg, http://tag.povray.org/

<><

Post a reply to this message