|
![](/i/fill.gif) |
"Thorsten Froehlich" <tho### [at] trf de> wrote in
news:3c596886@news.povray.org:
>> silly winpov bug
>> (Double clicking the title bar on some machines causes "text selection
>> not supported")
>> http://news.povray.org/3c3b7a3f@news.povray.org
>
> Wasn't this fixed in beta 10 or said to be fixed in beta 11?
Still present in beta 10. The behavior of this bug appears to depend on
the position of the Pov window and can be reliably repeated on all Win2K
systems I checked.
>> max_trace_level affects radiosity recursion_limit
>> ((beta 10) max_trace_level sets an upper bound on recursion_limit)
>> http://news.povray.org/3BE40295.6C3D54DE@engineer.com
>
> Has not been confirmed. No example provided either.
Confirmed in <Xns### [at] 204 213 191 226>
Code used:
box {<-4,0,-4> <4,4,4> pigment {rgb 0.5} hollow}
box {<3.75,1,-3> <4,3,3> pigment {rgb 1} finish {ambient 10}}
sphere {y,1 pigment {rgb 0.5}}
light_source {y*3.99 rgb 1}
camera {location <0,2,-3.5> look_at <0,2,0>}
global_settings {
max_trace_level 1
radiosity {
recursion_limit 10
pretrace_start 0.08 pretrace_end 0.04 count 35 nearest_count 5
error_bound 1.8 low_error_factor .5 gray_threshold 0.0
minimum_reuse 0.015 brightness 1 adc_bailout 0.01/2
}
}
>> Media visible container line in front of object
>> (a visible whitish line appears at the edge of a transparent container
>> box for media)
>> http://news.povray.org/3bf45a3d@news.povray.org
> The example scene is too complex and it hasn't been confirmed either.
Confirmed in <Xns### [at] 204 213 191 226>
>> [win gui] line with error highlighted but render finished succesfully
>> http://news.povray.org/va2tvt4tuitd67ik5t9ps334sbg6205bt3@4ax.com
>
> Isn't the highlighted error simply a text selection? Either way, the bug
> has not been confirmed.
Confirmed in <Xns### [at] 204 213 191 226> The problem is not a
text selection but rather that the error highlight bar is not always
cleared even after a successful render.
>> media & fog bug?
>> http://news.povray.org/3c1379e0$1@news.povray.org
> This is not confirmed and there is even disagreement noted in the
> thread if this is a bug at all!
Confirmed in the original thread and in
<Xns### [at] 204 213 191 226>.
Ken Tyler was the only person who asserted that the behavior described
should not be fixed. His rationale was that this bug shouldn't be fixed in
3.5 because it existed in 3.1g.
Bob H ultimately agreed with Kevin Ellis that "the box container object
itself does seem to cast a shadow when it should not be."
Post a reply to this message
|
![](/i/fill.gif) |