POV-Ray : Newsgroups : povray.beta-test : Bug in PovRay 3.7 RC7 ?! : Re: Bug in PovRay 3.7 RC7 ?! Server Time
29 Apr 2024 17:54:54 EDT (-0400)
  Re: Bug in PovRay 3.7 RC7 ?!  
From: Dave Downing
Date: 24 Feb 2013 05:56:24
Message: <5129f1d8$1@news.povray.org>
On Sun, 24 Feb 2013 10:27:12 +0100, Le_Forgeron wrote:

I too am running this on the linux RC7 version to try to narrow down the 
issue. In my case:

CPU: Intel i7-3770K Quad Core Overclocked to 4.5GHz (I love saying that!)
RAM: 16GB
OS:  Fedora 18 x86_64

 
> Should I presume +KFI0 +KFF360 +KI0 +KF1 ?
> (361 frames, initial clock 0, final clock 1) ?

Line 625 is the start of a series of #if's for each frame starting at 1. 
The clock variable is not referred to at all.

I used:
povray +w1920 +h1080 +KFI1 +KFF360 Scene_def.pov
 
> (PS: 124 hard-coded paths of include, arghh... <3 I also got a warning
> on each inc, about a null normal vector)
> )

I had the same warnings as you.

I did a search and replace to make the path to the include files 
relative, no other changes to the source.

Still running after over 20 hours, but no errors so far.
160 frames generated of what looks like to be a wonderful animation.

Is the bug limited to the Windows version?

-- 
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
Dave Downing,  Somerset U.K.
No bytes were harmed in the making of this message.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.