Chaos Corona for Cinema 4D > [C4D] Resolved Bugs

Possible Bug

(1/3) > >>

BigAl3D:
I have a project that I want to render on my small farm. I Save Project with Assets to ensure I have everything since this will be on another network.

Since this is an animation, I always like to pull up the texture manager make sure I have all green checks. Well, there are a bunch of materials that apparently didn't make the trip. I do see the word "shared" quite a bit in there. I believe every material in this scene is from the material library or Cosmos. Perhaps one or two I have a PBR set for. Nothing complex.

It is also possible that any missing textures may not be in the view of this camera, but didn't want to take a chance.

Is there a workaround for this? I would imagine this is a big problem for anyone sending their project to a real render farm.

Thanks.

Mac C4D r25
Version • 10 (Daily Build Nov 28 2022)

Just realized I have Version • 10 (Daily Build Dec 20 2022) on the remote Mac. Doubt that would cause this though.

Beanzvision:
Hi there,

I think the issue here is the shared shader. If so, the workaround would be to ensure that nothing is being shared and it may require some duplicate shaders instead. I understand that it might be time consuming, but if that's the cause, I'm not sure of any other workaround other than it being looked into by the devs. I hope this helps for now. Fingers crossed!

BigAl3D:
Thanks for the info. Interesting.

I do remember some discussion about shared items when sending jobs out to render farms. So in this case, I dropped the two materials in question into a new scene. In the wood material on the left, would the three nodes I have selected be considered shared since their output is sent to three places? I tried duplicating those three and linking the copied to the other two nodes, but the textures were still broken.

With my limited knowledge on this, it does not appear that the metal material on the right has any shared shaders, correct? Yet that material also breaks. Is sharing shaders only a Corona thing, or is that common in node editors? Curious if this is a Corona-only problem, or could it also be a Cinema 4D issue? Does Max have this problem too?

I have also sent The PixelLab an e-mail with this problem, but I will do a follow-up with the shared items issue. Maybe they can update the pak until a solution is found.

TomG:
C4D doesn't have the concept of "send the same shader to multiple different locations", unlike 3ds Max. This was what we had to code for ourselves to make our Node Material Editor (and is why it remains unique and different from "node based materials" in C4D, which still don't allow the same shader to be linked to multiple places in one material/shader or certainly not across shaders or materials). Behind the scenes, a special "Shared Shader" is created to handle this. Anything connected to more than one input can only work if this Shared Shader is created.

BigAl3D:
Knowing this issue has been around for quite a while, I have no problem finding a workaround. I know Joren from The Pixel Lab would be interested to know too. This is his first Corona pack and I don't want him to shy away from future Corona products. I'm thinking if I know what I need to eliminate from the node editor, I can set up a scene with corrected materials and be fine until a solution is found. In the attached image, and as my note indicate, it appeared there was one instance of a shared shader. I duped them and connected directly, but they still won't collect properly. I'm also confused as to why the other two shaders down below are also broken when they did NOT have shared shaders. Any insights?

Can I send this shader library to the private uploader to see if you can decipher anything wrong with the setup?

Navigation

[0] Message Index

[#] Next page