![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Hello,
I toiced in menay scenes that using radiosity often leads o crash of
PovRAY. Am I the only one here with some problems ?
For every scene using radiosity - it either render succesfully, or crash
just after end of rendering (probalby deallocation).
Crash means :
- MsgBox iforming about problems, and suggesting to restart PovRAY
- after closing box sometimes pov is working fine, sometimes it starts to
print messages in [probably] endless loop :
objects.cpp line 887
NULL object removed
and almost always print (instead Win98 report - PovRAY has performed
illegal operaiton ...) :
Returned from renderer due to access violation exception
I tested about 5 radiosity scenes (including 1 from include menu) and all
have problems. About 1 of 10..20 renders crashes.
I have Athlon 1,7 256 RAM Win98 SE
Maybe I can run this radiosity scene in some debug mode ?
--
#macro g(U,V)(.4*abs(sin(9*sqrt(pow(x-U,2)+pow(y-V,2))))*pow(1-min(1,(sqrt(
pow(x-U,2)+pow(y-V,2))*.3)),2)+.9)#end#macro p(c)#if(c>1)#local l=mod(c,100
);g(2*div(l,10)-8,2*mod(l,10)-8)*p(div(c,100))#else 1#end#end light_source{
y 2}sphere{z*20 9pigment{function{p(26252423)*p(36455644)*p(66656463)}}}//M
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
"Rafal 'Raf256' Maj" <raf### [at] raf256 com> schrieb im Newsbeitrag
news:Xns### [at] 204 213 191 226...
> Hello,
> I toiced in menay scenes that using radiosity often leads o crash of
> PovRAY. Am I the only one here with some problems ?
Well, you don't see this group full of such reports, do you? ;-)
No, seriously, it is really hard to tell without a scene, but could it be
that you are testing with some glass objects, low adc_bailout, high
radiosity recursion level, or something similar? If so try to increase the
max_intersections global setting.
Or did you overclock your system and/or memory? Or do you have an unuaual
amount of memory banks in use, i.e. all banks with double-sided DIMM modules
(that is with chips on both sides of the modules)? Do you have occasional
8every day or two) crashes with other programs as well? In that case, clock
your system to a normal rate, make sure the RAM settings are conservative,
and if you have all banks full, remove one module.
Thorsten
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
On 12 Sep 2002 03:13:30 -0400, "Rafal 'Raf256' Maj" <raf### [at] raf256 com> wrote:
> Hello,
> I toiced in menay scenes that using radiosity often leads o crash of
> PovRAY.
Usually my English is bad but this time I don't undesrtand so much.
> Am I the only one here with some problems ?
If I understand first sentence that you have crash on every radiosity scene I
can't notice anything like this on my system.
> For every scene using radiosity - it either render succesfully, or crash
> just after end of rendering (probalby deallocation).
> Crash means :
> - MsgBox iforming about problems, and suggesting to restart PovRAY
> - after closing box sometimes pov is working fine, sometimes it starts to
> print messages in [probably] endless loop...
Since POV suggested you to exit it can be responsible for further behaviour.
> I tested about 5 radiosity scenes (including 1 from include menu) and all
> have problems. About 1 of 10..20 renders crashes.
IIRC some days ago somebody suggested to you it can be hardware problem. Have
you checked this ? Is your system overclocked or something ?
> I have Athlon 1,7 256 RAM Win98 SE
I have a Pentium II 233 128 RAM NT4
> Maybe I can run this radiosity scene in some debug mode ?
Sure. Just recompile POV in debug mode and use debugger.
ABX
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Thorsten Froehlich wrote:
> Or did you overclock your system and/or memory? Or do you have an unuaual
> amount of memory banks in use, i.e. all banks with double-sided DIMM
> modules
> (that is with chips on both sides of the modules)? Do you have occasional
> 8every day or two) crashes with other programs as well? In that case,
> clock your system to a normal rate, make sure the RAM settings are
> conservative, and if you have all banks full, remove one module.
Can I add "check the CPU temperature"? And I speak here as experienced
cpu-burner... :(
--
Jaime Vives Piqueres
La Persistencia de la Ignorancia
http://www.ignorancia.org
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |