Chaos Corona Forum

Chaos Corona for Cinema 4D => [C4D] General Discussion => Topic started by: jojorender on 2022-05-21, 15:24:50

Title: Some Cosmos assets not team rendering
Post by: jojorender on 2022-05-21, 15:24:50
I’m late to the V8 game, so this is probably a known bug, but some assets render correctly on single machine but not in TR.
That’s a real joy, when you are pressed for time and use Cosmos assets - do a quick low res single machine render and then a full rez TR render overnight.
How fun when the next morning half your garden was rendered with the “nuclear winter pro" preset… There goes your deadline. 
This seems to happen to assets that use the opacity layer.
macOS 10.15.7 / S24/ V8
Title: Re: Some Cosmos assets not team rendering
Post by: BigAl3D on 2022-05-23, 15:38:39
Can we assume your are not missing textures for these assets? I haven't used Cosmos with TR yet, but that was my first though. If the materials are there, what happens if you convert the Proxy to mesh?
Title: Re: Some Cosmos assets not team rendering
Post by: bnji on 2022-05-23, 17:48:22
Hi,
I can see you're using Mac, could you please try using our latest Daily Build from here?: https://forum.corona-renderer.com/index.php?topic=36221.msg198797#msg198797
See if the issue persists.
Regards.
Title: Re: Some Cosmos assets not team rendering
Post by: jojorender on 2022-05-25, 20:08:18
Can we assume your are not missing textures for these assets? I haven't used Cosmos with TR yet, but that was my first though. If the materials are there, what happens if you convert the Proxy to mesh?
I would have said yes, the textures are there, they render on single machine but not in TR
Then I checked to make sure, and now I don't know anymore...
See screenshot attached. …immutable shader what??? No idea what this means.
That "mystery shader" does not show up in asset inspector.

@bnji
In the middle of a project that hopefully finalizes next week. Will try V9 daily then.
In general, is this related to the corona engine or could a cosmos browser update fix issues too? 
It looks like the leaf mapping is flipped 180°?
Title: Re: Some Cosmos assets not team rendering
Post by: Beanzvision on 2022-05-26, 12:15:46
Hi there, what's the asset that you have imported? Those textures do look flipped indeed. That's something we will need to look at. If you can let me know the name of this asset, that would be super!
Title: Re: Some Cosmos assets not team rendering
Post by: jojorender on 2022-05-26, 17:35:42
Purple Willow 001
Preview flipped, renders correctly, but maybe bump reversed?
TR shows faint leaves - nodes can't access these "immutable shaders"?
Happens to other assets w/ immutable shaders.
Title: Re: Some Cosmos assets not team rendering
Post by: Beanzvision on 2022-05-27, 11:01:40
Purple Willow 001
Preview flipped, renders correctly, but maybe bump reversed?
TR shows faint leaves - nodes can't access these "immutable shaders"?
Happens to other assets w/ immutable shaders.
Hi Jojo, Thanks for the info. I'm currently looking into it and will report it if need be.
Title: Re: Some Cosmos assets not team rendering
Post by: BigAl3D on 2022-05-28, 03:48:55
Curious if this issue has anything to do with the Proxies. For giggles, hit C on your proxies to convert them into meshes. Try TR after that. Total shot in the dark. Maybe I'm thinking of C4D's old problem of Xrefs.
Title: Re: Some Cosmos assets not team rendering
Post by: jojorender on 2022-05-30, 00:46:09
Hi BigAl3D, same outcome if rendered from mesh. I think the TR issue is related to the immutable shader.
My COSMOS assets get saved to a server that all nodes can access, but maybe they need to live on the main machine to be send to TR.
Are you by any chance already on V9 daily? When you have a minute, can you try to TR the 'Purple Willow 001" or any other asset that uses the mystery immutable shader?
Trying to figure out if this is related to my setup.
Thanks!   
Title: Re: Some Cosmos assets not team rendering
Post by: jojorender on 2022-06-07, 15:37:10
Hi Beanz,
any updates on this?
I checked the chaos help and can’t find out how to configure the cosmos browser installed on the nodes.
How do I make sure on the nodes with just TR client installed that Cosmos is looking in the right network folder for assets? 
MacOs 10.15.7/ S24/ Cor V8