I don't know if it is proper to ask about this here, but I can't get POVRAY
to work anymore.
I was rendering, re-rendering, suddenly couldn't render. Nothing changed, it
just stopped working.
I rebooted, ran scandisk, norton AV, (no problems detected) tried again, ran
once then stopped.
I reinstalled over the current installation, didn't work.
Tried uninstalling and reinstalling, didn't work
Finally tried using a non-animated .INI and that seemed to work , but then
it wouldn't work when I went back to my animation.

Here's the error, I'm using POV 3.1 in Win98 on a PII400 with 128 ram,
thanks for any help, I'll be trying different things all night until it
works.

PVENGINE caused an invalid page fault in
module PVENGINE.EXE at 0177:00439e86.
Registers:
EAX=00000014 CS=0177 EIP=00439e86 EFLGS=00010216
EBX=01e8fbdc SS=017f ESP=01e8f6cc EBP=01e8fd20
ECX=00000001 DS=017f ESI=02110000 FS=0f9f
EDX=00000000 ES=017f EDI=01e8f96c GS=0000
Bytes at CS:EIP:
f2 a5 8a c8 80 e1 03 f2 a4 5f e9 25 f7 ff ff 8b
Stack dump:
01e8f95c 02d2c9e0 01e8f810 00000080 01e8f7f0 00000000 3ff00000 01e8f710
02d2c960 00000000 00000000 020dffa8 01edffd0 0045fbf0 020dffc0 020dffa8

Post a reply to this message

Bill DeWitt wrote:
> 
> I don't know if it is proper to ask about this here, but I can't get POVRAY
> to work anymore.
> I was rendering, re-rendering, suddenly couldn't render. Nothing changed, it
> just stopped working.
> I rebooted, ran scandisk, norton AV, (no problems detected) tried again, ran
> once then stopped.
> I reinstalled over the current installation, didn't work.
> Tried uninstalling and reinstalling, didn't work
> Finally tried using a non-animated .INI and that seemed to work , but then
> it wouldn't work when I went back to my animation.
> 
> Here's the error, I'm using POV 3.1 in Win98 on a PII400 with 128 ram,
> thanks for any help, I'll be trying different things all night until it
> works.

  The first and most obvious question that comes to mind is if you have
tried rendering other files than the one you are working on currently.
There are rare occassions where one particular Pov file will cause invalid
page faults and there is nothing you do to stop it until you change the
conditions that are causing the fault. Sometimes it's simple like a defect
in an image map other times it might even be a bug in Pov itself. If you
have already tried other scenes and you are still having the problem I don't
know what to say as it seems you have tried some of the biggies already. Have
you tried deleting your windows managed swap file. Sometimes stuff gets in
there that does not get purgred properly and the only way to get rid of it
is to delete the file. It's Titled win386.swp and can only be deleted when
in true dos mode. There is no harm in deleting it and Windows will happily
write a new one with whatever it likes keep hidden in there.

 If you do isolate it to your scene file and can't find the problem with it
send it this way and I'll kick it's tires for you and see if I can figure
out what is causing the problem for you.

-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message

Ken <tyl### [at] pacbellnet> wrote :
>
>   The first and most obvious question that comes to mind is if you have
> tried rendering other files than the one you are working on currently.
>

    Great. Now I feel silly. Thanks...

    No, really... thanks! That was the problem.

    I cubed a clock...
camera_location = (clock*clock*clock)* FinalRestingPlace
...and that seemed to be the problem I dropped it back to (clock*clock) and
life was good again. I really want that cubed acceleration, so I will try
cubing it in a declare and then using it.

    I hate weird things that happen for unknown reasons....

Post a reply to this message

Bill DeWitt wrote:
> 
> Ken <tyl### [at] pacbellnet> wrote :
> >
> >   The first and most obvious question that comes to mind is if you have
> > tried rendering other files than the one you are working on currently.
> >
> 
>     Great. Now I feel silly. Thanks...

Oh your welcome :)
 
>     No, really... thanks! That was the problem.
> 
>     I cubed a clock...
> camera_location = (clock*clock*clock)* FinalRestingPlace
> ...and that seemed to be the problem I dropped it back to (clock*clock) and
> life was good again. I really want that cubed acceleration, so I will try
> cubing it in a declare and then using it.
> 
>     I hate weird things that happen for unknown reasons....

  So I am GUESSING what is happening here, if you want to know why Pov
is crashing on you, is that you have your camera location at
(clock*clock*clock) and the scene is starting at clock = 0. This places
the camera then at xyz = 0.
  You end up with a divide by zero error when the camera location and the
look at are at the same location. Before you can get an error warning
from the program the system steps in and issues an invalid page fault
instead. You could avoid this with something like:

camera_location = (clock*clock*-0.000001+clock)* FinalRestingPlace

  That little amount of offset from the origin is enough to avoid the
divide by zero problem and everything becomes one with the universe
again.

  But then again I might have read one too many messages on this server and
I have gone totaly daft. You make the call.

-- 
Ken Tyler

mailto://tylereng@pacbell.net

Post a reply to this message