 |
|
|
|
|
|
| |
| |
|
|
From: Warp
Subject: Request for confirmation about isosurface problems
Date: 1 Dec 2001 17:16:59
Message: <3c0956db@news.povray.org>
|
|
|
| |
| |
|
|
I have been experiencing strange and erratic problems with isosurfaces
in beta 8, in both the Windows and Unix versions. The symptoms include
POV-Ray crasing, going into an infinite loop or getting just black images
(when there should be a visible isosurface). The symptoms are really strange
and erratic because different people seem to get different problems with the
same code (or no problems at all!).
Please test isosurfaces with beta8 and forward a report to this article
if you find any kind of problem.
For starters, test with this simple scene at different resolutions (eg.
320x240, 512x384 and so on), with and without antialiasing, with and without
display, etc. If you get a problem, also test uncommenting the first line
to see if the problem disappears.
//#declare foo=function{0} // probable workaround for problems
camera { location -z*5 look_at 0 angle 35 }
light_source { <100,200,-300>, 1 }
isosurface
{ function { x^2+y^2+z^2-1 }
contained_by { sphere { 0,1 } }
pigment { rgb x }
}
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
320x240: POV-Ray traces a few lines then it crashes.
400x300 and higher: POV-Ray stops to trace when it reaches the iso, but
doesn't crash. The only thing I can do is to close POV.
Antialiasing did not have any effect in my tests.
Declaring any function makes it work, but only if it comes before the iso.
POV-Ray v3.5 b8 Windows Me Athlon
--
Jonathan.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
800x600 and 1024x768 make it crash too.
"JRG" <jrg### [at] hotmail com> ha scritto nel messaggio
news:3c0958d3$1@news.povray.org...
> 320x240: POV-Ray traces a few lines then it crashes.
> 400x300 and higher: POV-Ray stops to trace when it reaches the iso, but
> doesn't crash. The only thing I can do is to close POV.
>
> Antialiasing did not have any effect in my tests.
>
> Declaring any function makes it work, but only if it comes before the iso.
>
> POV-Ray v3.5 b8 Windows Me Athlon
>
> --
> Jonathan.
>
>
Post a reply to this message
|
|
| |
| |
|
|
From: JRG
Subject: Re: Request for confirmation about isosurface problems
Date: 1 Dec 2001 17:35:43
Message: <3c095b3f@news.povray.org>
|
|
|
| |
| |
|
|
Oops, forgot to mention that when it crashes this error message is
displayed: "Rendering Error: Maximum function evaluation recursion level
reached."
"JRG" <jrg### [at] hotmailcom> ha scritto nel messaggio
news:3c0958d3$1@news.povray.org...
> 320x240: POV-Ray traces a few lines then it crashes.
> 400x300 and higher: POV-Ray stops to trace when it reaches the iso, but
> doesn't crash. The only thing I can do is to close POV.
>
> Antialiasing did not have any effect in my tests.
>
> Declaring any function makes it work, but only if it comes before the iso.
>
> POV-Ray v3.5 b8 Windows Me Athlon
>
> --
> Jonathan.
>
>
Post a reply to this message
|
|
| |
| |
|
|
From: Christoph Hormann
Subject: Re: Request for confirmation about isosurface problems
Date: 1 Dec 2001 17:53:54
Message: <3C095F93.164D5E3E@gmx.de>
|
|
|
| |
| |
|
|
Warp wrote:
>
> I have been experiencing strange and erratic problems with isosurfaces
> in beta 8, in both the Windows and Unix versions. The symptoms include
> POV-Ray crasing, going into an infinite loop or getting just black images
> (when there should be a visible isosurface). The symptoms are really strange
> and erratic because different people seem to get different problems with the
> same code (or no problems at all!).
> Please test isosurfaces with beta8 and forward a report to this article
> if you find any kind of problem.
> [...]
Your sample scene does not crash, neither on K6 nor Athlon here, several
resolutions tried. But i experienced some quite strange things today, like
occasional crashes and wrong render results. They were not reproducible
and therefore very difficult to track.
Christoph
--
Christoph Hormann <chr### [at] gmxde>
IsoWood include, radiosity tutorial, TransSkin and other
things on: http://www.schunter.etc.tu-bs.de/~chris/
Post a reply to this message
|
|
| |
| |
|
|
From: Warp
Subject: Re: Request for confirmation about isosurface problems
Date: 1 Dec 2001 18:27:23
Message: <3c09675a@news.povray.org>
|
|
|
| |
| |
|
|
JRG <jrg### [at] hotmailcom> wrote:
: Declaring any function makes it work, but only if it comes before the iso.
Really? Now that's strange (in my experiments declaring the dummy function
at the beginning of the scene seemed to get rid of all problems, but if what
you say is true it's even more erratic than I thought).
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Warp <war### [at] tagpovrayorg> wrote in news:3c0956db@news.povray.org:
> Please test isosurfaces with beta8 and forward a report to this
> article if you find any kind of problem.
(Use monospaced font)
Tests on a P3-866 running WinME, without the workarond function
declaration:
Res AA Display Result
160x120 off on Try #1: Pov _disappears_ with no error message or trap
report.
Try #2: pvengine trap on 9th line of the image.
160x120 off off pvengine trap on 9th line of the image.
320x240 off on pvengine trap on the 17th line of the image.
320x240 off off pvengine trap on the 17th line of the image.
400x300 off on pvengine trap on 21st line of the image
400x300 off off pvengine trap on 21st line of the image
640x480 0.3 on Render thread appears to enter an infinite loop and
generates no more content after line 34 as indicated
on (lower) status bar. Title bar says 'line 1 of
480'. Alt-G/Stop icon has no effect. Pov must be
shut down in order to reset the renderer.
640x480 0.3 off As above.
800x600 0.3 on As above except render halts at line 43.
800x600 0.3 off As above.
The traps which occurred during low-resolution renders were at EIP=
0x0010CE10, caused because the processor attempted to execute move
[esi],edx while [esi] pointed into la la land. There was no regular
pattern to [esi]; null and other values were observed.
Tests on a Celeron 400 running Win2K, without the workaround function:
Res AA Display Result
160x180 off on Trapped in 2/2 attempts.
320x240 off on Renders in 8/10 attempts. Failed with function
division by zero error on fifth attempt. Error
message did not give either the correct file name or a
function name. Pvengine trapped on the tenth attempt.
400x300 off on Renders 8/10 times. Attempt 3 rendered very slowly (~
600 pps). Attempt six trapped.
400x300 off off Trapped 4/4 times at line 21.
640x480 0.3 on Renders 5/10 times. Function division by zero on
attempts 1 and 9; incorrect filename given on attempt
1. Rendered very slowly on attempts 5 and 6.
Rendered a completely black image on attempt 8.
640x480 0.3 off Renders 4/10 times. Trapped on attempt 4; fell into an
infinite loop @ line 34 on attempts 5 and 7-10.
800x600 0.3 on Renders 6/10 times. Division by zero on attempts 4, 5
and 9; correct filename only given on attempt 4.
Trapped on attempt 7.
The scene renders without incident at all resolutions with all combinations
of aa and preview display on both PCs when the workarond function
declaration is included.
Post a reply to this message
|
|
| |
| |
|
|
From: R Suzuki
Subject: Re: Request for confirmation about isosurface problems
Date: 2 Dec 2001 06:07:55
Message: <3c0a0b8b@news.povray.org>
|
|
|
| |
| |
|
|
The below is my result. I have experienced such bug once (or twice)
during the isosurface patch development. I think there are several
other bugs relating isosurface core code. Now I can take some time
for POV-Ray for a while (maybe a few months) and can help POV-Team
if the source code is available.
CPU OS Compiler
Celeron Windows Me : Intel : It crashes.
Celeron Windows Me : VC : It crashes.
Athron Windows 2000 : Intel : No plobrem.
Athron Windows 2000 : VC : No plobrem.
Pentium III Windows 2000: Intel : It crashes.
Pentium III Windows 2000: VC : It does not crash but Fatal error.
R. Suzuki
Post a reply to this message
|
|
| |
| |
|
|
From: Thorsten Froehlich
Subject: Re: Request for confirmation about isosurface problems
Date: 2 Dec 2001 07:40:41
Message: <3c0a2149@news.povray.org>
|
|
|
| |
| |
|
|
As discussed in p.p-b I know there are problems, but there is no pattern for
those is available because they are memory/pointer related. So everybody
will see different problema nd at this time there is no fix possible.
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: Warp
Subject: Re: Request for confirmation about isosurface problems
Date: 2 Dec 2001 07:47:36
Message: <3c0a22e8@news.povray.org>
|
|
|
| |
| |
|
|
Thanks for your exhaustive testing.
Now I can be sure that it's not just me, but something weird is really
happening.
The seemingly random nature of the problem may indicate that some illegal
memory section or an already freed memory section is being read, or something
similar. Perhaps also an unitialized variable or table might cause this kind
of erratic behaviour.
--
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
