 |
|
|
|
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: [Bug] Output of too many evaluations cause strange behavior
Date: 8 Oct 2001 17:08:03
Message: <3bc215b3@news.povray.org>
|
|
|
| |
| |
|
|
Hi!
If you have too many iso-evaluations, the message pane goes "blank" after
the first few ones, the "time to parse"-Box in the lower left statusbar
shows weird things (15388d 11h 41m 37s f.e.), and if you try another render,
the render window disappears and won't come back until a restart.
In addition: If you try to stop the "render" while Pov displays the Messages
(evalutations), Pov crashes (if you stop while the message pane is already
blank -> page fault) or does not react at all.
It may well be, that this occurs with other warnings, too, I didn't test
that.
Marc-Hendrik
PII450, Win 98, 128 MB, Pov 3.5-beta-5
Testscene:
camera
{
location <0, 1.7, 20.0>//
angle 40
look_at <0, 5.7, 0.00001>
}
union{
#declare Reihen=0;
#while (Reihen<150)
isosurface
function { abs(x)
}
max_gradient 4
evaluate 1,10,0.99
accuracy 0.01
contained_by{box {<-0.15,-0.2,-0.2>,<0.15,0.2,0.20>}}
texture{pigment{rgb 0.1}}
}
#declare Reihen=Reihen+1;
#end
}
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: [Bug] Output of too many evaluations cause strange behavior
Date: 8 Oct 2001 17:13:30
Message: <3bc216fa@news.povray.org>
|
|
|
| |
| |
|
|
In article <3bc215b3@news.povray.org> , "Marc-Hendrik Bremer"
<Mar### [at] t-online de> wrote:
> #declare Reihen=0;
> #while (Reihen<150)
It might well be that this is caused by the #while-bug. or did the same
happen with beta 4 as well?
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
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Re: [Bug] Output of too many evaluations cause strange behavior
Date: 8 Oct 2001 17:21:51
Message: <3bc218ef$1@news.povray.org>
|
|
|
| |
| |
|
|
Thorsten Froehlich schrieb in Nachricht <3bc216fa@news.povray.org>...
>In article <3bc215b3@news.povray.org> , "Marc-Hendrik Bremer"
><Mar### [at] t-onlinede> wrote:
>
>> #declare Reihen=0;
>> #while (Reihen<150)
>
>It might well be that this is caused by the #while-bug. or did the same
>happen with beta 4 as well?
I don't think so. I don't have beta 4 installed anymore. But if you remove
the "evaluate", anything works as expected.
And the code parsed and rendered without problems with two nested
while-loops resulting in more than 1900 isos - until I added the "evaluate".
This is just a simplified version.
Hope that helps,
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Wasn't it Thorsten Froehlich who wrote:
>In article <3bc215b3@news.povray.org> , "Marc-Hendrik Bremer"
><Mar### [at] t-onlinede> wrote:
>
>> #declare Reihen=0;
>> #while (Reihen<150)
>
>It might well be that this is caused by the #while-bug. or did the same
>happen with beta 4 as well?
A quick check shows that beta 4 also fails, but in a very different way.
The 150 eval results start to stream up the message pane, but after a
while the shapes of the characters become distorted. A while later the
colour of the characters changes from white to dark grey. Finally
PVENGINE crashes with "an invalid page fault in module <unknown>".
Sometimes other running programmes also get knocked over.
POV 3.5b4, W98se, AMDK6-2 500, 128 Mb
POV 3.5b5 behaves as described by Marc-Hendrik.
It's just a wild guess, but perhaps there's some limitation to the
amount of text that can be displayed on the message pane after rendering
has completed. Each of the 150 evaluates causes 7 lines of text and two
horizontal separators to be displayed on the message pane.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Sidenote: Too many nested objects (Re: [Bug] Output of too many evaluations cause strange behavior)
Date: 9 Oct 2001 04:26:42
Message: <3bc2b4c2$1@news.povray.org>
|
|
|
| |
| |
|
|
BTW: If I remove the camera-statement from the posted scene, I get (after
parsing): "Rendering error: Too many nested objects." That not correct, is
it?
Marc-Hendrik
Marc-Hendrik Bremer schrieb in Nachricht <3bc215b3@news.povray.org>...
>PII450, Win 98, 128 MB, Pov 3.5-beta-5
>
>Testscene:
>union{
> #declare Reihen=0;
> #while (Reihen<150)
>
> isosurface
>
> function { abs(x)
> }
>
> max_gradient 4
> evaluate 1,10,0.99
>
> accuracy 0.01
> contained_by{box {<-0.15,-0.2,-0.2>,<0.15,0.2,0.20>}}
>
>
> texture{pigment{rgb 0.1}}
> }
> #declare Reihen=Reihen+1;
> #end
>}
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
From: Slime
Subject: Re: Sidenote: Too many nested objects (Re: [Bug] Output of too many evaluations cause strange behavior)
Date: 9 Oct 2001 12:07:44
Message: <3bc320d0$1@news.povray.org>
|
|
|
| |
| |
|
|
Looks to me like the scene is missing a '{' after "isosurface". (On the
other hand, I'd think that would generate a different error, such as "'}'
found where object or directive expected" or something.) Maybe I just
overlooked something stupid.
- Slime
[ http://www.slimeland.com/ ]
[ http://www.slimeland.com/images/ ]
"Marc-Hendrik Bremer" <Mar### [at] t-onlinede> wrote in message
news:3bc2b4c2$1@news.povray.org...
> BTW: If I remove the camera-statement from the posted scene, I get (after
> parsing): "Rendering error: Too many nested objects." That not correct,
is
> it?
>
> Marc-Hendrik
>
> Marc-Hendrik Bremer schrieb in Nachricht <3bc215b3@news.povray.org>...
>
> >PII450, Win 98, 128 MB, Pov 3.5-beta-5
> >
> >Testscene:
> >union{
> > #declare Reihen=0;
> > #while (Reihen<150)
> >
> > isosurface
> >
> > function { abs(x)
> > }
> >
> > max_gradient 4
> > evaluate 1,10,0.99
> >
> > accuracy 0.01
> > contained_by{box {<-0.15,-0.2,-0.2>,<0.15,0.2,0.20>}}
> >
> >
> > texture{pigment{rgb 0.1}}
> > }
> > #declare Reihen=Reihen+1;
> > #end
> >}
> >
> >
> >
>
Post a reply to this message
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Re: Sidenote: Too many nested objects (Re: [Bug] Output of too many evaluations cause strange behavior)
Date: 9 Oct 2001 12:42:02
Message: <3bc328da@news.povray.org>
|
|
|
| |
| |
|
|
Slime schrieb in Nachricht <3bc320d0$1@news.povray.org>...
>Looks to me like the scene is missing a '{' after "isosurface".
No, that is not the case.
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
From: Mike Williams
Subject: Re: Sidenote: Too many nested objects (Re: [Bug] Output of too many evaluations cause strange behavior)
Date: 9 Oct 2001 19:58:36
Message: <imejUOA8t0w7EwyK@econym.demon.co.uk>
|
|
|
| |
| |
|
|
Wasn't it Marc-Hendrik Bremer who wrote:
>
>Slime schrieb in Nachricht <3bc320d0$1@news.povray.org>...
>>Looks to me like the scene is missing a '{' after "isosurface".
>
>No, that is not the case.
I assumed that it was just an error in your posting. I had to add the
'{' when I reproduced the original problem under 3.5b4. And I have to
add it to reproduce the 'too many nested objects' warning. There are
certainly more '}'s than '{'s in what you posted, so if 3.5b5 is
accepting it, it's a new bug.
--
Mike Williams
Gentleman of Leisure
Post a reply to this message
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Re: Sidenote: Too many nested objects (Re: [Bug] Output of too many evaluations cause strange behavior)
Date: 10 Oct 2001 04:13:30
Message: <3bc4032a@news.povray.org>
|
|
|
| |
| |
|
|
Oh ... my fault. Of course there has to be a { after "isosurfaces". In my
testscene it's still there I must have deleted it after pasting it in the
post (made some minor changes to shorten the code a bit). No
"parenthesis"-bug. I misread the post of Slime, too (thought of a missing
"}"). Sorry!
But you were able to reproduce the 'too many nested objects' warning, too?
Those two bugs are probably not the top priority though, as they occur only
in very special cases.
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
From: Marc-Hendrik Bremer
Subject: Re: [Bug] Output of too many evaluations cause strange behavior
Date: 28 Oct 2001 18:00:23
Message: <3bdc8e07@news.povray.org>
|
|
|
| |
| |
|
|
I made another test.
This script
#while(true)
#declare X=0
#end
passed for about 7 minutes without problems while generating hundreds of
Warning messages. So there seems not to be a limit in the message pane
itself, but the problem might really be caused by the "evaluation"-messages.
Out of curiosity: Are they generated and stored while rendering or generated
after the render is complete?
Marc-Hendrik
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
