VFB doesn't update performance settings

[aaouviz]

Hi,

A little bug I've noticed in the past few days. I'm using the current latest daily.

When I update the noise level target, or the total passes (in the max settings) while rendering is taking place, although these targets are updated in the Corona VFB they are not adhered to. That is, they still follow the old targets as set when rendering is started.

This previously worked as expected, ie; I have 50 passes set, I press render, then when I change it to 25 passes, the rendering stops when hitting 25 passes (Same for noise level). However now, the updated target isn't followed.

I hope this makes sense? See attached. Thanks!

[Frood]

Afaik it has always been like this. I once requested to evaluate changed stop conditions during rendering to be able to control a running render by script remotely but was told that it is not as easy.


Good Luck

[aaouviz]

I'm 99% certain it used to work as I described... at least with noise target?

I could be going crazy...

[Frood]

Nope, none of noise level, pass limit or time limit are respected if they change either by ui or by script. You'd have to test for stop conditions by script "manually" and regulary, then initiate a graceful render stop instead.


Good Luck

[aaouviz]

Hmm, curious.

Indeed, I am going crazy then :)

Thanks!

[maru]

I don't think it ever worked like that, and I don't think it would make a useful feature.
If anyone disagrees, please let me know in which version it worked differently, and how this could be useful.

[Frood]

I don't think it ever worked like that

Me too.

and I don't think it would make a useful feature.

Me not.

and how this could be useful.

1. User errors and flexibility: imagine a render has been started with huge loading and parsing time and you noticed that you forgot to set a time cap or any other stop condition was not set correctly because you worked with preview settings while preparing the scene. Currently you would have to cancel, change the stop conditions and restart everything from scratch again. I'm talking about scenes made of several nested xrefs, 20 Min. loading/parsing time are not extraordinary.

2. Remote controlling jobs easily: See Mantis #0003017. The request to evaluate stop conditions during rendering has already been handled there. On a wish list scale from 1 to 10 it's a 7 for me, so I can accept the rejection. The reasoning is questionable though, because other renderer properties pulled out at render start are evaluated during rendering very well.


Good Luck

[aaouviz]

Agreed.

I think this would be a massively useful feature! Please consider :)

It could even be possible to control it inside the VFB? Just an idea...