Team render - render region ignores noise limit

[jojorender]

Version • 10 (Daily Build Jan 23 2023) / macOS 10.15.7 / R24

When render region is set, noise limit (5%) is ignored and render stops early around 20%
This happens when team rendering on 3 nodes. Noticed this on several different jobs.
It used to work as expected before.

[TomG]

Something must be triggering the stop condition, so questions are:
- Is there another target set, such as time or passes?
- Are you sure it isn't a reporting error in the noise amount, and that the noise may say 20% but is in fact 5%? (ie is the resulting image as noisy as a 20% noise target image from a single machine?) How many passes are done, and how does that compare to a render without TR?
- Does Corona 9 do the same thing? (as in, has been tested with these very same scenes)

[bnji]

Hi @jojorender
It would be handy to provide us with the info requested by @TomG
Additionally, could you please provide your scene project (including assets) so we can investigate a little bit further?
You can use the uploader located in my signature.
Looking forward to hearing from you.
Kind regards.

[jojorender]

Don't have time now to test this or prepare scene. Will do later.

- ONLY noise level set
- it stops while region is still very noisy - not reporting error.
- Did not test these scenes in V9, but I don't think V9 had this issue.

Current workaround, set high pass limit and let it run...

BTW, is it possible to have release version and daily both installed and easily switch between them without always complete reinstall?
If so, please let me know how this works. MacOs if that matters.

[bnji]

Hi @jojorender,
Thank you for your reply.
No worries, I'll try reproducing the issue in the meantime.
Regarding installing different Corona for Cinema 4D versions, you can try installing different versions, but it will require different C4D versions as well.
I mean, you could install C4D S26 + Corona 9 and also have installed in the same computer C4D 2023 + Corona 9 hotfix 1.
The only thing is that you should install both Corona versions using the "Custom" button during installation and enable/disable the appropriate C4D version checkbox, then complete the installation process.
Note: This scenario is not recommended, but still it's possible.
I hope this helps.
Please keep me posted.
Kind regards.

[jojorender]

So basically no easy switching… Thanks for letting me know.

I just ran into the region render noise limit bug again. TR stops early, single machine renders till 3%. See screenshots.
Will send a scene when I have a min.

[bnji]

Hi @jojorender
Thanks for the additional info.
Could you please let me know the spec for your rendering nodes? (CPU, RAM, OS, etc.)
Looking forward to hearing from you.
Kind regards.

[jojorender]

I wanted to prepare a scene for you to test - “Save Project with Assets” and lots of assets are now missing in the newly created project. My original file renders fine in TR and doesn’t show any issues with missing textures. The usual shared shader / Corona bitmap issue.
I wouldn’t normally use the C-bitmap but unfortunately many cosmos assets use this shader... knowing it has issues.
I think fixing the many C-bitmap problems is more important than this region render issue.
Thanks anyway!