Ouch.

Dozens of hours into rendering of this nice, complex scene, with radiosity
and AA turned on, continuing after one BSOD and one power failure, POV
(official release) blurts out this...

'Rendering Error: No textures in multi-texture CSG object.'

WTH? The scene renders at lower res (320x200) just fine, so the scene itself
should be pretty much all right. But even that takes about four hours, so I
guess the 1024x768 one would have been... um, forty hours. But there's no
way to continue after this kind of error, so I'm left with a three-quarter
image.

Could anybody enlighten me about how this can happen and if there's any way
to avoid it? I know it's not memory, I got 512M and POV took some 12M.

-- Me

ps. No, I won't attach the scene file. Not only is it taking ages to render,
it also has several MB of stuff in mesh #includes and imagemaps and such.

Post a reply to this message

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

> The scene renders at lower res (320x200) just fine

Because the object causing this error simply isn't visible then...?

    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

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

> Ouch.
>
> Dozens of hours into rendering of this nice, complex scene, with radiosity
> and AA turned on, continuing after one BSOD and one power failure, POV
> (official release) blurts out this...
>
> 'Rendering Error: No textures in multi-texture CSG object.'

Please note: This is *not* a crash.  Your subject line it totally
misleading.  This is a simple error message!

Please use the correct terminology in the future.  A crash is an abnormal
termination of the program, not any error the program displays and lets you
continue to work with it.

    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

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

> Could anybody enlighten me about how this can happen and if there's any way
> to avoid it?

I would try to remove all cutaway textures.

    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

Well,

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

    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.

    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.

But I'll try it anyway. It's not a big change. Thankx.

    'J.R.R'

Post a reply to this message

news:3f48b52d@news.povray.org...

> POV took some 12M.

Are you sure of that figure ? It seems very low for a radiosity scene
requiring 40 hours to render and using several MB of meshes, image_maps and
such.  I know that in the past, POV-Ray running out of memory gave me some
strange errors.

G.


-- 
**********************
http://www.oyonale.com
**********************
- Graphic experiments
- POV-Ray and Poser computer images
- Posters

Post a reply to this message

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

Try to see how much virtual memory pov has been using?

Post a reply to this message

"Gilles Tran" <git### [at] wanadoofr> wrote in message
news:3f4a7e3b@news.povray.org...

> news:3f48b52d@news.povray.org...
>
> > POV took some 12M.
>
> Are you sure of that figure ? It seems very low for a radiosity scene
> requiring 40 hours to render and using several MB of meshes, image_maps
and
> such.  I know that in the past, POV-Ray running out of memory gave me some
> strange errors.
>

Well, it certainly was under 20M... I just restarted a continue of the scene
with a slightly modified scene to get rid of the cutaways. (fingers crossed)
And the several MB of meshes is just the file size on disk; in memory they
certainly should be much smaller!

And, getting a scene that takes lots and lots of hours to render is easy if
you're an isosurface freak like me, and put in enough many complex big glass
objects with interiors and fresnel reflections and other fun stuff. :-)
There's only 1200 frame level objects, so it's not that complex as scenes
go.

    'J.R.R'

Post a reply to this message

"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3f490af2$1@news.povray.org...
> In article <3f48b52d@news.povray.org> , "J.Random Raytracer"
> <wyr### [at] hotmailcom> wrote:
>
> > Could anybody enlighten me about how this can happen and if there's any
way
> > to avoid it?
>
> I would try to remove all cutaway textures.
>
>     Thorsten
>

Well, that did it. Slightly mangled pic in p.b.i. Whee. Thanks again.

    'J.R.R'

Post a reply to this message