Daily builds version 2

[maru]

It was explicitly called "Significantly faster rendering of shadowcatcher in compositing mode" in the changelog, so I guess that's what it does. ;)
I think adaptivity and dark areas is a slightly different topic.

[sprayer]

but you wrote about noise in shadows, not how much faster it is now -__- also at yout picture i can see what AA now has more priority so so AA vs Gi may be different in 2.0

[romullus]

I find that noise level readings in 2.0 greatly differs from 1.7 Something like 18 min. vs 5 min. to arrive at 5% in the same scene. But of course 2.0 is much noisier than 1.7 at the same noise level. Was that done deliberately, or it's just consequence of some changes? To me it looks like noise level makes less and less sense with each release... :/

[sevecek]

I find that noise level readings in 2.0 greatly differs from 1.7 Something like 18 min. vs 5 min. to arrive at 5% in the same scene. But of course 2.0 is much noisier than 1.7 at the same noise level. Was that done deliberately, or it's just consequence of some changes? To me it looks like noise level makes less and less sense with each release... :/

It is a consequence of the changes in adaptivity, but it's definitely undesirable. I already changed the computed noise level to be (approximately) the same as in Corona 1.7, it should be in daily build soon.

[romullus]

Thank you! Looking forward to the next build then :]

[romullus]

Regarding constant IR refresh on mouse move over viewports, i found that it's like completely random thing. Over the period of same session, it came from stable IR, then to constant refresh and then to stable again. Nothing major was changed in the scene, appart from hiding/unhiding objects, creating and applying materials. Corona cameras are present in the scene, but were hiden at that moment and rendering was going through perspective view.

[TomG]

I had it happening in a scene with Corona Proxies, and when I removed those, it worked normally again, so that seemed to be part of it at least, not sure if that relates to what you were hiding and unhiding :)

[denisgo22]

Regarding constant IR refresh on mouse move over viewports, i found that it's like completely random thing. Over the period of same session, it came from stable IR, then to constant refresh and then to stable again. Nothing major was changed in the scene, appart from hiding/unhiding objects, creating and applying materials. Corona cameras are present in the scene, but were hiden at that moment and rendering was going through perspective view.

Strange thing--- if selecting all objects in scene with IR, some time this working correct, and after some time return to refreshing

[Ryuu]

We have a fix for the restarting IR. It will be in next daily (hopefully today).

Usual disclaimer: Not sure if this fixes all the IR restarting problems or just most of them.

[danio1011]

I was just curious, is the recent memory footprint reduction of 8 bytes per triangle a lot?  Or a little?  How much does a triangle usually use?

[Ryuu]

This doesn't have a simple answer.

In internal Corona representation this means ~12% reduction in memory per triangle. But each of Embree, Corona and 3ds Max has its own representation of the geometry, so the data is unfortunately triplicated (this is something we want to address in the future). To be honest, right now I have no idea of Embree or 3ds Max memory footprint for geometry data, but assuming it's the same as Corona, this results in a net ~4% memory reduction.

That's why we thought it was more important to just say it's 8 bytes per triangle so you can immediately see that "yay, my 1G poly scene will now consume 8G less memory" :)

[romullus]

1G triangles scene?! Tell that to my 16G computer :]

[maru]

So far I checked with displacement. In both cases the initial RAM usage for the whole system was ~10GB.
In 1.7 and v2 the curve look similar at the beginning, but with 1.7 it stayed at almost 18GB, and with v2 it stayed at just a bit over 16GB.
6:8 would mean 25% lower RAM usage in this case.

[Ondra]

yep, it is "1 gigabyte memory saved per 125M unique polygons". It is nothing dramatic, I am currently working on making something way better for scenes with motion blur.

[Dionysios.TS]

Hi all and happy new 2018!
Sorry for the silly question but I can find the post whith the new Dropbox link to be able to download the latest Daily Build 2.0....

Any clues?

Thanks!

Dionysios -