OTOY Forums

Hi, this feature was annonced a while ago (mainly for 1.5), but i have not seen or heard more about it since..
Is it now implemented in 2.0?

https://www.youtube.com/watch?v=4k0sOCf-1dU

Would be interested too.
Any infos?

5 months ago they said that the improved sampling did not pan out, and that it will not be implemented. Something like it worked really well on small scenes but did not show any improvements on larger scenes

huh... I remembered the same thing today and wanted to ask... not quiet a good info bcravin gave here

Do you know the thread, where it was discussed?
I hoped to see some improvements in scenes with heavy light usage in 2.0...

Huh? Where do they say that? .. Never seen anything about it..
I for one would happily welcome performance improvements on small scenes.....

It's buried somewhere in forum discussion. It was definitely said though.

here:

http://render.otoy.com/forum/viewtopic.php?f=9&t=36737

The new direct light sampler didn't work as well in real life scenes as in our test scenes: In our test scenes the image converged many times faster than with the old light sampler. We observed a reduction of the render time to get to the same noise level by about 50-80%, i.e. a speedup of 100-400%. But the new sampler introduced a lot of complexity, and GPUs don't like complexity. Not at all. As a result of the added complexity the overall sample rate slowed down a lot (about 10-40%, depending on the scene). But we had the faster convergence, right?
Well no... When we tested more real life architectural scenes, we experienced a bad surprise: Some areas in the image converged quite well, but some areas much worse than with the old sampler. We understand the problem, but we don't have a solution that doesn't introduce even more complexity. In the end we decided that this development was a dead-end and that we should cancel it. I.e. we will not release the new direct light sampler until we have found a better and faster solution.
We know it's disappointing, but be assured that we have tried really hard to get this working and it was quite frustrating to get stuck and not being able to make it work good enough in most cases. I think we will revisit this area not too far in the future.

ok the answer is:

with 2.0 you will need to double the performance of your hw because the core now is 2x slower
Yesterday I was observing that Embree is the answer.
Octane 2.0 is slow because Cuda is not ok and programmers has to invent complex tricks to add new features.

regards

hmm, that really is the bad side of 2.0 then.. I bought it thinking ofcourse i would get a nice speedboost
Anyway.. the other 2.0 features are great so..

gabrielefx wrote:ok the answer is:

with 2.0 you will need to double the performance of your hw because the core now is 2x slower
Yesterday I was observing that Embree is the answer.
Octane 2.0 is slow because Cuda is not ok and programmers has to invent complex tricks to add new features.

regards

Please send your scenes to Abstrax and Karba and work with them to investigate this. It should not be 2x slower.