Tim Nikias wrote:

> This is the minimum scene-file Thorsten Froehlich requested to
> check the bug. When tracing with focal-blur, objects get
> cut in half or vanish, depending on which object you use
> to be translated by vnormalize(<0,0,0>).

  Oh... well, if you use vstr() with vnormalize(<0,0,0>), you will se it 
returns a vector <nan,nan,nan>. If you look also at the docs, the 
description for vnormalize() "criptically" states that "vnormalize(<0,0,0>) 
will not give a usefull result". This sounds more like an undesired side 
effect than a bug... and from the docs wording I can supose there is no 
easy solution for the problem. Note this sentence was not on the 3.1 docs, 
so I suspect it was discussed on a previous bug report...
 
  Anyhow, if your using vnormalize inside loops, you can test for the 
"special case" to replace it with the apropiate value (if it makes sense at 
all).

  Hope this helps! 


-- 
Jaime Vives Piqueres

La Persistencia de la Ignorancia
http://www.ignorancia.org

Post a reply to this message