This is probably caused by a slight misuse of the cutaway_texture feature.

The syntax of cutaway_textures allows you to create a situation where the
texture is undefined for a surface in the CSG object.  Unfortunately, POV
won't know this until render time, because POV doesn't pre-compute CSG
operations.  If POV were to decompose the CSG object into a mesh, for
example, it would be able to determine this situation before render-time.
When a Ray in POV hits a surface with an undefined texture at runtime, this
error message is generated.

The solution would be to carefully review the texture definitions and
applications for your objects that use the cutaway_textures feature.
Remeber that the default texture might not be applied for some objects
within the CSG object (otherwise cutaway_textures wouldn't work).  Make sure
every surface of your object will have a texture defined.

-Nathan


"J.Random Raytracer" <wyr### [at] hotmailcom> wrote in message
news:3f48b52d@news.povray.org...
> 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