 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On ubuntu amd64, with "povray --benchmark"
Parse Warning: gamma_correction not specified or inferred so is turned
off for
compatibility with this pre POV-Ray 3.7 scene. See the documentation
for more
details.
May be the benchmark scene can be updated to avoid that warning ?
Trace time on amd3500+ (old!): 9 minutes 29 seconds (569.449 seconds)
with 4 threads. (548.117 CPU-seconds total)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/06/2010 04:57 PM, Le Forgeron wrote:
> On ubuntu amd64, with "povray --benchmark"
>
> Parse Warning: gamma_correction not specified or inferred so is turned
> off for
> compatibility with this pre POV-Ray 3.7 scene. See the documentation
> for more
> details.
>
>
> May be the benchmark scene can be updated to avoid that warning ?
>
> Trace time on amd3500+ (old!): 9 minutes 29 seconds (569.449 seconds)
> with 4 threads. (548.117 CPU-seconds total)
just so we don't end up stepping on each others toes ... i'll go ahead
and look into this one
Post a reply to this message
|
|
| |
| |
|
|
From: Chris Cason
Subject: Re: povray --benchmark on linux from source
Date: 6 Dec 2010 17:28:37
Message: <4cfd6395@news.povray.org>
|
|
|
| |
| |
|
|
On 7/12/2010 09:22, Jim Holsenback wrote:
> just so we don't end up stepping on each others toes ... i'll go ahead
> and look into this one
It's worth keeping in mind that the benchmark code has a fair bit of stuff
disabled (back from the early days of the beta). It might be worthwhile
starting out with a fresh copy of the benchmark file from 3.6 and only
changing the minimum necessary to make it work well with 3.7.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/06/2010 04:57 PM, Le Forgeron wrote:
> On ubuntu amd64, with "povray --benchmark"
>
> Parse Warning: gamma_correction not specified or inferred so is turned
> off for
> compatibility with this pre POV-Ray 3.7 scene. See the documentation
> for more
> details.
Done ... for those who have access I'd appreciate a sanity check ...
change #5249
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/08/2010 02:32 PM, Jim Holsenback wrote:
> On 12/06/2010 04:57 PM, Le Forgeron wrote:
>> On ubuntu amd64, with "povray --benchmark"
>>
>> Parse Warning: gamma_correction not specified or inferred so is turned
>> off for
>> compatibility with this pre POV-Ray 3.7 scene. See the documentation
>> for more
>> details.
>
> Done ... for those who have access I'd appreciate a sanity check ...
> change #5249
btw:
Render Time:
Photon Time: 0 hours 0 minutes 0 seconds (0.308 seconds)
using 5 thread(s) with 0.367 CPU-seconds total
Radiosity Time: No radiosity
Trace Time: 0 hours 2 minutes 58 seconds (178.175 seconds)
using 2 thread(s) with 354.943 CPU-seconds total
opensuse11.2 amd athlon x2 250 4gb
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Le Forgeron <jgr### [at] free fr> wrote:
> On ubuntu amd64, with "povray --benchmark"
Btw, when I try the benchmark like that (on OpenSuse 11.3), it fails to
render with the message:
File '/tmp/pov7021.pov' line 141: Possible Parse Error: Cannot find file
'functions.inc', even after trying to append file type extension.
If I #include "functions.inc" in a regular file and render it with
POV-Ray 3.7, it finds it ok, so it's not a problem in configuration.
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/08/2010 05:47 PM, Warp wrote:
> Le Forgeron <jgr### [at] freefr> wrote:
>> On ubuntu amd64, with "povray --benchmark"
>
> Btw, when I try the benchmark like that (on OpenSuse 11.3), it fails to
> render with the message:
>
> File '/tmp/pov7021.pov' line 141: Possible Parse Error: Cannot find file
> 'functions.inc', even after trying to append file type extension.
>
> If I #include "functions.inc" in a regular file and render it with
> POV-Ray 3.7, it finds it ok, so it's not a problem in configuration.
>
hmmm ... i never saw that ... before OR after #5249
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Jim Holsenback <jho### [at] povrayorg> wrote:
> before OR after #5249
I have no idea. It has been a really long time since I last tried.
Note that I didn't *install* povray. I just compiled it and moved the
executable to my home directory bin directory. It works ok like that
(when I configure ~.povray/3.7/povray.ini properly). I don't know if
that's the source of the problem. (The benchmark should definitely work
regardless.)
--
- Warp
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
