Ok, let me explain one thing before you start stoning me: I am not a
programmer. Last time I touched source code I programmed data bases with
Clipper, this was centuries ago. So, my question might go completely in the
wrong direction. Now:

I have a problem with a current scene, where I get the error message "too

anything helpful. My own topic still remains un-answered after weeks, which


Naive, but fearless, I downloaded the source, expecting to find somewhere a
block with all the text strings for the error messages - this was very




Now, is anybody here who can say me either where these error messages are
stored (or how they can be found) or who can say what exactly has to happen
before this message is displayed? The latter would be better, I think,
because I doubt I would understand the code even If you would point me to
the exact line.

TIA for any help

S.

Post a reply to this message

Steely wrote:
> I have a problem with a current scene, where I get the error message "too

> anything helpful. My own topic still remains un-answered after weeks, which


The error message is clear and simple: Your scene is defective. Searching in
the source code, especially if you don't understand the source code (as you
admit yourself) will be a huge waste of your time. Fix your scene by nesting
fewer textures and you are done.

> Naive, but fearless, I downloaded the source, expecting to find somewhere a
> block with all the text strings for the error messages 

How could this possibly work? Error messages need to contain text based on
the context of your scene. As such, there is no central place where they
could be stored, nor can they all be stored (the context information comes
from your scene), nor is it prudent software design to store all strings in
a single location within the source code (either use GUI design tools or
don't attempt an international interface - for POV-Ray the later is
appropriate as the scene description language is not translatable either).

As such, you have to search in the source code for the string. Any
reasonable text editor as well as IDE will do it for you.

	Thorsten

Post a reply to this message

Moin, moin, Thorsten!

As always, I am thankfull for your help, but not happy about the
presumptions ;-)

Thorsten Froehlich <tho### [at] trfde> wrote:

> The error message is clear and simple: Your scene is defective.

No, it is not. I have dozens of objects in the scene, each textured the same
way. None of them but one results in this error message.

> Fix your scene by nesting
> fewer textures and you are done.


while-loop. However, the loop itself is ok.

To avoid looking like a complete idiot (which I am sometimes, of course;-)):
- the scene is perfectly fine
- the texturing is perfectly fine
- the loop is perfectly fine
- when placing the object in question (a tree) outside the loop, the scene
renders perfectly fine
- when placing another object, for example simple spheres, inside the loop
(instead of the trees) the scene renders perfectly fine

So, my conclusion is:
If the program gives an error message about nested textures, where no


S.

Post a reply to this message

Steely wrote:
> So, my conclusion is:
> If the program gives an error message about nested textures, where no


No, as you can nest textures by nesting objects with textures ;-) Create one
texture around the whole union and you are done.

	Thorsten

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:
>
> Create one
> texture around the whole union and you are done.


possibility to texture them in any other way as I am used to, but I will
give it a try as soon as the machine is free.

However, to understand the problem better: by what exactly is it caused? I
have made thousands of loops over the years, and never, never, never I came
across this message. And this one is one of my smaller loops with < 100
items, I have made them far bigger without problems.

S.

Post a reply to this message

Steely wrote:
> However, to understand the problem better: by what exactly is it caused?

Usually by directly or indirectly creating textures that "inherit" other
textures.

	Thorsten

PS: Remember that this limitation only exists up to POV-Ray 3.5!!! If you
are not using POV-Ray 3.6.1 yet (which does not have a limitation on nested
textures), note that you may just wait a few more days for POV-Ray 3.6.2,
which addresses most of the current known problem with POV-Ray 3.6.1 that
have prevented people from upgrading to 3.6. Of course, you can use 3.6.1
now, as it also solves your problem already.

Post a reply to this message

Thorsten Froehlich <tho### [at] trfde> wrote:

> PS: Remember that this limitation only exists up to POV-Ray 3.5!

Hehe, but I am running 3.5 as I had some strange behaviours with 3.6 under
Win 2000 and have ATM no Linux machine running. Thanks anyway.

S.

Post a reply to this message