Warp <war### [at] tagpovrayorg> wrote:
> If some data is modified during rendering (ie. it's not read-only),
> sharing it between threads introduces problems. The 3.7 code tries to
> avoid this as far as possible: Most of the scene data, once parsed and
> created, is read-only, ie. is not modified during rendering (with some
> parts of the code it actually required some rewriting for this to be so
> because they needlessly used eg. temporary buffers which were modified
> during rendering).

I see... and i guess it points out the very cause for 2 bugs still present
in 3.7.beta6, namely web.429167334ebdfea56a3607400@news.povray.org
(isosurface contained by a sphere randomly mangling the balance of the
scene) and web.428f943986c60abc6a3607400@news.povray.org (black opaque
sphere carved out of a semi transparent box giving artifacts on the back
side of the box). In both cases it looks like some data that is supposed to
be read-only is actually modified during rendering - especially in the first
case, the first square or first 2 squares to actually contain the
isosurface are ok, but the balance of the scene doesn't make sense.

JYR
---------------------------------------------------
Windows XP HomeEdition//AMD Athlon XP 2800+1 MB RAM

Post a reply to this message