Is 1.6 slower than 1.5 ?

[Grisha_J]

DarcTheo - If you are talking about crashing, as for me 1.5 has pretty much the same stability as 1.6. Flavius and I mentioned the IR responsive of 1.6  which is different (especially first few seconds after starting) compared to 1.5.But this is secondary.
The most serious issue is the speed, which in my understanding should be increased after each major update, or at least should stay the same.

Ondra - the speed issue happens in all scenes.
Configuration: i7 6700k ; 1050Ti; 16gb ram.

[cecofuli]

are the differences very "important"?
In my test, in 15 minutes, the difference is between Noise Level 5.7 and 6.0 = 0.3
In my opinion isn't so big. Anyway, van you share to us more info and, maybe, both rendering 1.5 vs 1.6?

Thanks

[Grisha_J]

I am sorry Francesco, but I don't have rights to share this scene.But developers of course have this scene and can test it - I uploaded it 2 weeks ago.
Based on my tests, this particular scene shows a difference as I wrote before - 12%!. In my opinion 12% is serious - I would say huge difference.
Also - I've described the negative sign of the new version. I don't think for most of us decreasing of performance is "not a big deal".I thought we spend  periodically our money, and update our cpus exactly for the performance.
Again I'm not complaining - I'm just trying to help and improve this great product.

[cecofuli]

Yes, 12% is too much. but, I think that, if there is a problem, the Corona Team will solve it.
Maybe your scene is a "special" scene.
I think that the Corona programmers did a lot of test  before 1.6 release, to know the 1.6 average performance =)

[Ryuu]

Some of our users found out that we have an unfortunate performance problem with VFB refreshing. The refreshing of the VFB contents (+ applying all the tone mapping operators) just takes too much of the CPU time.

We have identified the issue in the code and it will definitely be fixed. We'll discuss this internaly but from my point of view the code changes needed are so extensive that I wouldn't want to risk doing this in hotfix and so it will be fixed in 1.7 (daily builds).

In the meantime as a workaround you can try:

• Disabling sharpening during the rendering
• Zooming in the VFB all the way in
• Closing VFB during the rendering

I think that just the first step (disabling sharpening) should give you the biggest performance boost while still being only a minor inconvenience.

From the initial reports just zooming in to 1:32 can speed up rendering by up to 10%.

[cecofuli]

That's great =) I'm sure you will solve this "bug" soon

[Grisha_J]

Thank you Ryuu - we will wait new update!

[lupaz]

Was this fix on any hotfix?
Did anyone go back to 1.5? Is it possible to go back from 1.6?
Thanks.

[maru]

Was this fix on any hotfix?
Did anyone go back to 1.5? Is it possible to go back from 1.6?

Which fix do you mean specifically?
You can go back even to 1.0: https://corona-renderer.com/download/old

[lupaz]

Got it.
Thanks.

In the office they're using 1.6 hotfix 3.
With a heavy scene, the subsampling was very annoying, because it was erasing the vfb with every move. I lowered the subsampling to 1 and it's the sweet spot.