 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi,
I encounter an error that does not make sense to me (I am using POV version
3.7.0.RC7.msvc10.win64 on a Win 7 64 bit OS with 32 GB RAM).
starts without any problem, but then after a few frames (and this number varies
randomly: sometimes 3, sometimes 9, etc.), it suddenly stops with the error
The *.pov file can be found here:
http://www.isi.uu.nl/People/Alexander/files/Scene_def.pov
The *.inc files (containing "mesh2" objects) can be downloaded here:
www.isi.uu.nl/People/Alexander/files/POV_inc_files.zip (370 MB)
FYI (1) - you need around 12 GB RAM to render this animation and with my i7 2.4
GHz quadcore it takes around 15 min to run one frame...
FYI (2) - in RC6, the same animation produced the error similar to
http://bugs.povray.org/task/257.
Any suggestions on how to tackle this problem? Or am I doing something wrong?
Kind regards,
Alexander
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
The "full" link to the *.inc files:
http://www.isi.uu.nl/People/Alexander/files/POV_inc_files.zip (370 MB)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Here you can find why - according to POV-Ray - the render failed:
http://www.isi.uu.nl/People/Alexander/files/Extra_info_error.pdf
Again - I do not understand this...
Many thanks in advance!
Cheers,
-A
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 23.02.2013 21:02, schrieb Alex:
> I encounter an error that does not make sense to me (I am using POV version
> 3.7.0.RC7.msvc10.win64 on a Win 7 64 bit OS with 32 GB RAM).
>
> starts without any problem, but then after a few frames (and this number varies
> randomly: sometimes 3, sometimes 9, etc.), it suddenly stops with the error
Uh-oh... this doesn't sound very encouraging.
> FYI (1) - you need around 12 GB RAM to render this animation and with my i7 2.4
> GHz quadcore it takes around 15 min to run one frame...
>
> FYI (2) - in RC6, the same animation produced the error similar to
> http://bugs.povray.org/task/257.
>
> Any suggestions on how to tackle this problem?
Yup: Please add a comment to http://bugs.povray.org/task/257; it sounds
to me like the issue hasn't been fixed for good yet.
> Or am I doing something wrong?
RAM shouldn't be the problem (you have more than enough, and even if it
wasn't sufficient you'd end up in Swap Hell instead of seeing the render
abort.
Render time shouldn't play a role either: No matter how long it takes,
once POV-Ray is convinced that the render threads have been started
successfully, it should wait patiently until they do finish (even if it
takes a lifetime) or the /user/ gets impatient and hits the "stop"
button. (In that case it may well happen that the render threads are so
deep into math that they take longer to respond than POV-Ray is willing
to wait /then/, but from what you describe you're not hitting any button
during the render.)
As for scene content or render settings, there's no conceivable way to
provoke the error message you're seeing.
So no, chances are very, very slim that we might be able to blame it on you.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 23.02.2013 21:44, schrieb Alex:
> Here you can find why - according to POV-Ray - the render failed:
> http://www.isi.uu.nl/People/Alexander/files/Extra_info_error.pdf
>
> Again - I do not understand this...
That's obviously POV-Ray hallucinating, after having suffered severe
brain injury. After all, I presume you didn't touch the .ini file during
the render, so why should it suddenly cease to work from one frame to
the next.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 23.02.2013 21:46, schrieb clipka:
>> Any suggestions on how to tackle this problem?
>
> Yup: Please add a comment to http://bugs.povray.org/task/257; it sounds
> to me like the issue hasn't been fixed for good yet.
One more thing: Please make a backup of the scene in its current state;
we currently don't know how common the issue is, so we might need your
scene (and you and your computer) as guinea pig once we come up with a
solution candidate.
If you can trim down the scene a bit while still reproducing the error,
that would be a great help as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Alex <ale### [at] hotmail com> wrote:
> The "full" link to the *.inc files:
> http://www.isi.uu.nl/People/Alexander/files/POV_inc_files.zip (370 MB)
I would like to see what happens on a the Mac version but the download
of this archive is extremely slow and stalls after a while.
Isn't it possible to put it somewhere else?
yvo
--
-----------------------------------
MegaPOV at: http://megapov.inetart.net
MacMegaPOV at: http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Yvo Smellenbergh <yvo### [at] cancel_This_gmxnet> wrote:
> I would like to see what happens on a the Mac version but the download
> of this archive is extremely slow and stalls after a while.
> Isn't it possible to put it somewhere else?
I finally managed to download the archive.
yvo
--
-----------------------------------
MegaPOV at: http://megapov.inetart.net
MacMegaPOV at: http://users.skynet.be/smellenbergh
E-mail: yvo(DOT)s(AT)gmx.net
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le 23/02/2013 21:02, Alex nous fit lire :
> In summary, I’m making an animation that consists of 360 frames (in the
> “povray.ini” file, I set “Initial_Frame = 1” and “Final_Frame = 360”).
It always
> starts without any problem, but then after a few frames (and this number varies
> randomly: sometimes 3, sometimes 9, etc.), it suddenly stops with the error
> message: “Operation timed out. Render failed.”
Should I presume +KFI0 +KFF360 +KI0 +KF1 ?
(361 frames, initial clock 0, final clock 1) ?
> FYI (1) - you need around 12 GB RAM to render this animation and with my i7 2.4
> GHz quadcore it takes around 15 min to run one frame...
The first frame (at clock 0) is full black here, is it normal ?
later frame are better.
parse time about 4 minutes, render time is futile (14 seconds on frame 2).
And the memory reported by top is rather 14.7 GB of virtual memory (on
64 bits) for the povray process.
(PS: 124 hard-coded paths of include, arghh... <3
I also got a warning on each inc, about a null normal vector)
)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
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
|
|
| |
| |
|
|
|
|
| |
