 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi, I have a problem:
I'm trying to render the last scene I made for the IRTC (El Ojo) at high
resolution (5763 x 3842) and the render stops about halfway, with this
message:
Returned from renderer due to stack overflow exception
POV-Ray finished
Any tip?
Txemi Jendrix
tji### [at] txemijendrix com
http://www.txemijendrix.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Txemi Jendrix <tji### [at] euskalnetnet> wrote:
> Returned from renderer due to stack overflow exception
> POV-Ray finished
> Any tip?
What is your max_trace_level?
--
#macro N(D)#if(D>99)cylinder{M()#local D=div(D,104);M().5,2pigment{rgb M()}}
N(D)#end#end#macro M()<mod(D,13)-6mod(div(D,13)8)-3,10>#end blob{
N(11117333955)N(4254934330)N(3900569407)N(7382340)N(3358)N(970)}// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
3d3228f9@news.povray.org...
> What is your max_trace_level?
255
I also get this window when I render it (sorry, couldn't copy it before):
The POV-Ray core rendering code caused an stack overflow exception.
It is STRONGLY RECOMMENDED that you save your work and exit the program
before attempting the render again.
(Note that if internal structures have been damaged POV-Ray may crash after
you click OK)
Anyway I will try to render again with low value.
Thanks.
Txemi Jendrix
tji### [at] txemijendrixcom
http://www.txemijendrix.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Now I'm using a Max_Trace_Level 125 and works fine.
Thank you for the quick tip.
Bye
Txemi Jendrix
tji### [at] txemijendrixcom
http://www.txemijendrix.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Txemi Jendrix <tji### [at] euskalnetnet> wrote:
> Now I'm using a Max_Trace_Level 125 and works fine.
> Thank you for the quick tip.
The maximum allowed max_trace_level was lowered in 3.5 in order to
avoid the stack overflow problem, but it seems that it didn't help after
all...
--
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
In article <3d3249eb@news.povray.org> , Warp <war### [at] tagpovrayorg> wrote:
> The maximum allowed max_trace_level was lowered in 3.5 in order to
> avoid the stack overflow problem, but it seems that it didn't help after
> all...
No, it does help, but it is still possible to find ways to exceed this
limit. Nobody ever said it would now never be exceeded. It only prevents
people from setting it to 100000 and place two perfect mirrors in a scene
and wait for the crash.
Of course, we could reduce the limit to 5 or 6 and it would always work, but
I doubt that would be in anybodies best interest...
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
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I wonder if it could be possible to add a check to the exception handler
which would print a note like "(perhaps a too high max_trace_level?)" when
this particular crash is caught.
--
#macro M(A,N,D,L)plane{-z,-9pigment{mandel L*9translate N color_map{[0rgb x]
[1rgb 9]}scale<D,D*3D>*1e3}rotate y*A*8}#end M(-3<1.206434.28623>70,7)M(
-1<.7438.1795>1,20)M(1<.77595.13699>30,20)M(3<.75923.07145>80,99)// - Warp -
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
3d33185c@news.povray.org...
> I wonder if it could be possible to add a check to the exception handler
> which would print a note like "(perhaps a too high max_trace_level?)" when
> this particular crash is caught.
Not bad idea. I checked the help file and there were no entries for 'stack'
and 'overflow'.
Bye
Txemi Jendrix
tji### [at] txemijendrixcom
http://www.txemijendrix.com
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
