tho### [at] trfde news:419e59df@news.povray.org

> If it really is a problem (I don't know), then a warning and
> auto-adjusting adc_bailout when not explicitly set might be a more
> "practical" solution for all those who do not read the documentation
> :-) 

I also have a better (probably) idea, and I hope not hard to implement,

1. ray that exceeded max_trace_level should return it current color (stop 
calculations) instead of returning black rgb 0,0,0  (by the way, not 
connected directly to this problem).

2. ray that hits motion_blur object that is too "small" i.e. rgb 0.001 to 
be noticed - just returns it current color (calculated so far). _but_ if 
the rgb 0.001 object is the _first_ object to be hit, then current color 
can not be returned, because no object had been hit yet. In that case - 
0.001 object is taken intoo account, and ray continues to go along, until 
hit solid surface or exceed max_trace_level, or until stoped by "to small" 
reflection (lower then adc_bailout)

3. they might be several types of adc_bailout
  reflection_adc
  refraction_adc
  transparent_adc
  motionblur_adc (with defaults to transparent_adc)
  and perhaps
  general_adc to quickly set all above.

Would it be hard to implement? If someone will implement it please inform 
me so I might assist.


-- 
http://www.raf256.com/3d/
Rafal Maj 'Raf256', home page - http://www.raf256.com/me/
Computer Graphics

Post a reply to this message