> Hello
>
> Sorry for the delay. Using my TAG Member magic cap, here's the official
> answer.
>
> - The scene code for the entire scene and the close ups should be the same,
> so using different values for function based height fields is not allowed.
> Choose the maximum heightfield resolution you can afford for all renders.
> The close-ups must look good, but they do not have to look as good as the
> submitted image (for instance, in the http://www.povcomp.com/samples/ page,
> the first close up shows that the tree leaves lack definition).
>
> - You can write in the text that the resolution can be increased if enough
> ressources are available, and you can provide such "quality triggers" in the
> code. That way, it will be possible to produce an even better image if
> necessary.

Hi
Thanks For The Replys.
I have thought of a way round my original problem by using a calculation
that will calculate the complexity of the heightfields depending on the
image size. Since the code will modify itself I think this will make it
legal. Call me a perfectionist but I dont want my zoom ins to look just ok.
How is everyone doing? my job is really getting in the way. oh for the
unemployed life...
Peter