Hi everyone,
I've been running into ongoing issues when using Team Render with Corona Renderer. The rendering behavior is noticeably different compared to local renders, and in this particular case, the Mixture Shader is not working correctly when rendered over Team Render. Locally, everything looks fine.
I've been using Corona since the early Alpha days (back when it was still free), so it's been around 8–9 years now. Unfortunately, I’m seeing more and more issues related specifically to Team Render.
Please also check my previous threads on this topic – I haven’t received any response there yet.
At our studio, we have six high-performance Team Render machines running locally, but due to the issues described, we currently can't use them. This seriously impacts our timeline and workflow, as we're now forced to render everything locally just to make sure results are correct.
I kindly ask you to take a closer look at this issue. We're definitely not the only ones experiencing these problems – and some of them have existed for quite a long time now. I always try to describe everything in as much detail as possible and provide clean test scenes to help track down the issue.
The current problematic scene is attached. I hope this can be investigated further.
Best regards,
Tuami
2025.2.1
Latest Daly 02.06.
Other current problems
Problems with CXR when renderings via Team Renderer
https://forum.corona-renderer.com/index.php?topic=44128.0Team Renderer Issue with Corona Bitmap Shader in C4D 2025: Materials Not Display
https://forum.corona-renderer.com/index.php?topic=44204.0See also last post from BigAl3D
Interesting. I had reported this Team Render issues a long time ago, maybe 4 or 5 years. Team Render behaves similar to Save with Assets. In my case, textures, at least from third party materials sets, when collected would change the name of the texture file to some random numeric name, but not the inside the path so they would all be missing from the render. In my case it was a material set from The Pixel Lab. I will try your workaround with a C4D node sitting in there.
For me, I haven't used Team Render in a long time, but this issue would be a problem if you want to use a render farm too.
From metanerd
I’m following up on this again. Just like with Tuami, we can reproduce the same behavior here.
Everything works as expected up to version Cinema Version 2025.0.2.
Starting with version 2025.1 and up to the current version 2025.2.1, files imported from the Asset Browser that either use the Bitmap Shader or are set up as Shared Materials no longer work in Team Render. Both V12-Hotfix 1 and V12-Update 2 work correctly under version 2025.0.2, but not from version 2025.1 onwards.
For us, this means we can no longer install any C4D updates, which is extremely inconvenient.
