|
 |
On 9/14/20 12:35 PM, William F Pokorny wrote:
> On 9/14/20 4:42 AM, Ton wrote:
>> Hello everybody,
>>
>> when I use am3 (stochastic anti-aliasing) in the latest version
>> (10064738), it
>> is about 5 times slower then in uberpov:
>>
>> Persistence of Vision(tm) Ray Tracer Version
>> 3.8.0-x.10064738.unofficial (g++ 7
>> @ x86_64-pc-linux-gnu)
>> Render Time:
>> Photon Time: No photons
>> Radiosity Time: No radiosity
>> Trace Time: 0 hours 20 minutes 4 seconds (1204.944 seconds)
>> using 4 thread(s) with 4542.093 CPU-seconds total
>>
>> UberPOV Raytracer Version 1.37.1.0-beta.10 (g++ 7 @ x86_64-pc-linux-gnu)
>> Render Time:
>> Photon Time: No photons
>> Radiosity Time: No radiosity
>> Trace Time: 0 hours 3 minutes 52 seconds (232.382 seconds)
>> using 4 thread(s) with 907.615 CPU-seconds total
>>
>> Command line is:
>> povray +d +p +q9 +am3 +a0.1 +ac0.9 +r6 AntiAliasingTest.pov
>> uberpov +d +p +q9 +am3 +a0.1 +ac0.9 +r6 AntiAliasingTest.pov
>>
>> Does anybody have a clue why povray is so much slower?
>>
>> Cheers
>> Ton
>>
>
> Are the results more or less similar?
>
> I know uber differs in code structure. I've myself run across an am3
> case in v3.8 where the run time - on a solid color change - increased
> 100x. Not yet dug into the latter. Beyond that, no idea.
>
> If the AntiAliasingTest.pov scene is relatively small and self
> contained, could you post a copy? I'll at least put it in my issues
> directory, though who knows when I might take a look at it.
>
> Bill P.
i've been using the am3 anti-aliasing in POV-Ray 3.8.0-alpha.10064268 in
conjunction with area lights... i'm able to use adaptive 0 then use am3
to cleanup edges etc... so i'd appreciate you finding /some/ time to see
if some speed gains can be found
Post a reply to this message
|
 |