In article <3f4a6913@news.povray.org> , "J.Random Raytracer" 
<wyr### [at] hotmailcom> wrote:

>    in reply to 1, the scene does not have any objects that small and it
> renders just fine at hi-res without radiosity.

In that case, if you can create a minimum scene using only the
cutaway_textures object that reproduces the problem, it would help to
improve this.

>     in reply to 2, this kind of fully non-obvious error is nasty in the
> manner that it does not quite allow continuing the work since it gives
> little clue about what is wrong, and IMO it looks like one that should have
> been caught already in the parsing stage, and while it is not a total system
> crash or program error, it still very well qualifies as Abnormal End.

No, the termination is no abnormal.  It is simply unexpected for you, but it
is *not* an unintended program behavior to terminate at the given point.

Whether it should terminate where it does is a totally different issue, and
I agree that it should not terminate there *if* possible.

>     and to 3, if there are features that do not work in conjunction but are
> not documented incompatible (like cutaway_textures and radiosity appear now)
> then it's a bug. And at least 98% of the only cutaway_textured object is
> already rendered at that stage, although there is no way knowing where the
> radiosity pincushion might get its rays to.

I neither said nor inferred that it has to do anything with cutaway_textures
in conjunction with radiosity.  This is just some wild guess on your part!
As you have not provided a scene showing the problem you have with the
current behavior - which is, as I pointed out not nice but intentional
rather than random - there is no way of telling what actually happens.

    Thorsten

____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org

Post a reply to this message