|
![](/i/fill.gif) |
Well, I just got home and there'd been another crash, about 15% of the way
through the actual render. Here's the error:
MEGAPOV caused an invalid page fault in
module <unknown> at 0000:a325d27e.
Registers:
EAX=019aeae0 CS=016f EIP=a325d27e EFLGS=00010282
EBX=01c19eb8 SS=0177 ESP=019aeac8 EBP=01bf37c0
ECX=00000000 DS=0177 ESI=005252d8 FS=2137
EDX=bfef1750 ES=0177 EDI=019aeaf8 GS=0000
Bytes at CS:EIP:
Stack dump:
0041c4e7 01c19eb8 019aeae0 019aeb38 00520180 00520180 bf3a4e40 bfef1750
00000000 3ff80000 9c619538 3fdd69d8 00417656 a325d27e 005252d8 00505c30
The image renders fine so long as radiosity is not on. Here's my current
set of radiosity settings:
radiosity {
count 200
distance_maximum 300
error_bound 0.4
minimum_reuse 0.025
nearest_count 8
recursion_limit 1
}
I've tried it with a number of various settings, including having just
count and distance_maximum; count has been variously 100, 150, and the
above 200; distance_maximum has been as low as 50, no higher than the
above 300; error_bound has been as high as 0.8, all in various
combinations.
Other things that might be of use in deciphering the problem:
There are two light-sources in my image, both point lights; I have tried
commenting out one or the other, and it doesn't help.
I am using media in the image, but taking it out doesn't solve the
problem.
There is one fairly highly reflective surface in the image but it's far
'down' in the image and the render gets nowhere near it.
Lastly, hardware and software:
pII 400 mhz, 128M RAM, ATI Rage Pro Turbo 2X 8MB card
Win98 4.10.2222 A
WinMegaPov 0.7, recently downloaded (last few weeks)
[Has also crashed under Win MegaPov 0.5, but I've experimented less under
that version.]
If no one has any idea why this might be happening I'll probably start
taking the code apart and rendering it piece by piece to see if I can
figure out if there's something specific in my code that could cause this.
-- Tina (Who wants to guess what I do for a living, btw?)
Post a reply to this message
|
![](/i/fill.gif) |