OTOY Forums

just tried the 2.0 Demo: benchmark scene render speed is 2/3 of v 1.2.....

PolderAnimation wrote: 'This is the price of all new feature. Unfortunately every new feature slows down gpu code even if it is not used. Not sure we can improve the speed anytime soon.'

'We have seen a slow down in the range 10-20% compared to 1.5, maybe 25%,..'

Will it still be possible to use vs. 1.5 if I upgrade to vs. 2.0? (I would also have to be able to use the Blender plugin vs. 1.5.)

Speed is more important to me than the new features in some cases.

justavisitor wrote: Will it still be possible to use vs. 1.5 if I upgrade to vs. 2.0? (I would also have to be able to use the Blender plugin vs. 1.5.)

Speed is more important to me than the new features in some cases.

It seems that the answer is Yes. I use both. For 2.0 I export alembic from blender via 1.5.

aLeXXtoR wrote:

justavisitor wrote: Will it still be possible to use vs. 1.5 if I upgrade to vs. 2.0? (I would also have to be able to use the Blender plugin vs. 1.5.)

Speed is more important to me than the new features in some cases.

It seems that the answer is Yes. I use both. For 2.0 I export alembic from blender via 1.5.

Yep,

Just a little question, I tried export curves for fur without success, Are you tried the fur for octane 2.0 from blender plugins ?

Matt

aLeXXtoR wrote: It seems that the answer is Yes. I use both. For 2.0 I export alembic from blender via 1.5.

Thank you. May I ask if you had any problems since you said the answer seems to be Yes?

Another thing: Can you use alembic for exporting animations from Blender and rendering them in 2.0?

MattRM wrote: Yep,

Tnank you - did you have any problems/conflicts?

MattRM wrote: I tried export curves for fur without success, Are you tried the fur for octane 2.0 from blender plugins ?

color]

I haven't tried 2.0 yet. But I'd also like to know the answer to that.

hi,
i'm one of the beta tester of octane render 2.0
here is a speed test comparison between v1.55 and v2.00 with a dual GTX 780 setup. It's the same file with about 2k polys and two different render target, one in exterior with sun light and another one in interior with hdri.
the test is done with Direct light kernel in AO mode since in the Path Tracing and PMC kernel there is a new parameter for "Specular depth" that is not present in the 1.55.
since the sampling/pixel value is a bit erratic, i have pressed 4 times the "resume render" button and saved each time a screenshot at the end of the render. then i have taken the medium value and here is the result: there is a drop in performance and it's totally scene dependent, but absolutely not so exaggerated.
here is the hi-res pdf with all the screenshots: ciao beppe

Great comparison. Thanks Beppe.
Seeker

I'm trying to upgrade but the store gives me a paypal error when I try to check out.

I just tested the demo on benchmark and on 2x gtx 590 speeds were pretty much the same in comparison with 1.16

Also at first glance I noticed noise converged pretty oke too

I noticed Priority renderings on all 4 gpus were turned on by default on 2.0....instead of 12ms I got about 8...when I turned that off it was good again.

omgyes! Looks like you can select a region to render, when noise clears up -> another region, and so on! Like putting 2048 fermi`s just in the right spot