|
 |
Thanks for that bit of important info. If one were to go by just the
statistics after a render every max_trace_level shows a change if the number
is different in the script.
Back to the merge thing...
I didn't look at it too well first time. Then I realized the textures were
added differently for the pair of boxes and pair of spheres. The boxes have a
shared texture in the merge statement. The spheres have independent textures.
The spheres also have a shadow showing the supposedly merged surface area
which should be gone, and it is labeled as "correct". The boxes labeled
"incorrect" have no shadow of the merged surfaces even when they are changed
to have non-coincident surfaces by scaling the z of one slightly larger. Plus
the anti-merge (or whatever) effect is gone this way too.
So, now what?
Message <366b26cd.0@news.povray.org>, Thorsten Froehlich typed...
>
>In article <366b1ef6.0@news.povray.org> , ver### [at] aol com (=Bob) wrote:
>
>>I don't know what's going on there but I tried putting a global_settings
>>{max_trace_level 20}, out of habit, into the script and got a same-surface
>>looking effect at the center of the cross. No other obvious changes. Then
>>--another strange thing-- I tried 2 instead of 20 and no change *back* to
the
>>first look (difference?), even tried to comment it out; no return to
previous
>>state. So I shut POV off, restarted it, ran the scene again (global_settings
>>still commented out) and it then returned to the first example: center
>>removed.
>
>Yes, this is a know problem of POV-Ray, max_trace_level is stored in a global
>variable, and it is no (always?) updated/installized except at startup. This
bug
> only
>exists for the GUI versions of POV-Ray (Win and Mac) as they are not
terminated
> and
>restarted for each render.
>
>
> Thorsten
>
>
>For all who want to know, the value of max_trace_level is stored in the
global
>Max_Trace_Level in render.c.
--
omniVERSE: beyond the universe
http://members.aol.com/inversez/POVring.html
=Bob
Post a reply to this message
|
|
