Chaos Corona Forum

Chaos Corona for 3ds Max => [Max] Feature Requests => [Max] Resolved Feature Requests => Topic started by: Nekrobul on 2016-03-11, 12:45:35

Title: Priority of progressive render limits.
Post by: Nekrobul on 2016-03-11, 12:45:35

The idea is to make some priorities between those limits.

For example i have 10 images to render in 10 h before deadline. So first i want them to be renderd for 1h each (maximum prority) or 400 pases wich i tested on problematic regions and is ok ofr me (second priority) and the last priority with a noise limit of 3%.


So what i ment - time limit > pases limit > adaptivity limit.

Title: Re: Priority of progressive render limits.
Post by: romullus on 2016-03-11, 13:24:54

Why just not to set those limits and render? It never won't render more than for 1 hour, more than 400 passes and won't reach less than 3% noise treshold. It's very simple and easy to understand. Should there be additional conditions, that would make all process too complicated to understand for non matematitians, like me.

Title: Re: Priority of progressive render limits.
Post by: Nekrobul on 2016-03-11, 14:46:49

Quote from: romullus on 2016-03-11, 13:24:54

Why just not to set those limits and render? It never won't render more than for 1 hour, more than 400 passes and won't reach less than 3% noise treshold. It's very simple and easy to understand. Should there be additional conditions, that would make all process too complicated to understand for non matematitians, like me.

Yes it is. But this noise limit is sometimes acting wierd.

For example i have 200 pases limit and 5% noise limit placed for batch render with 2 cameras 1 pointing to the area wich clears from noise quet well and fast other with volumetrics near the bright lightsorce. On the first image it reacheas 5% faster than 200 pases and render continues to the next image but on the second image it reaches 200 pases but render continues til it reaches 5%.

It was ok whe there was just 2 settings pases and time (both actualy control time but in different ways) and now we have 3 settings and one of them is controling only quality of the image ignoring pases limit.

Title: Re: Priority of progressive render limits.
Post by: Frood on 2016-03-11, 16:35:35

Quote from: Nekrobul on 2016-03-11, 14:46:49

[...] but on the second image it reaches 200 pases but render continues til it reaches 5%.[...]

Then this is a bug. All three conditions (#passes, time and %noise) are all equally eligible to stop the render, so

"max passes reached OR max time reached OR noise limit reached"

should stop the render process.

I can´t reproduce this here btw. (Latest DB + Max2016)

Good Luck

Title: Re: Priority of progressive render limits.
Post by: Ondra on 2016-05-08, 18:23:14

There were some bugs in the noise limit, hopefully it is now fixed