question

Yes, exactly, than you can be sure they won't collide.

Ok, just to check that I get it right:

For example I have 5 gras assets that all get the same material applied, then for each of the 5 objects I should use a separate namespace per asset?

Only procedurals can collide, the plugin takes care of other objects and shaders in the scene. So for instance if you have two shaders with the same name in a network, then the plugin adds an index to the second when exports it to Arnold. However the plugin can not change the content of the procedurals, they are black boxes.

Don't use any special characters in the namespaces, otherwise there's no special rule.

Hi Peter,

I'll look into the namespaces - I encountered this part of the manual while looking for a solution initally, but didn't quite understand the namespaces at first. I'll definetly give that a try.

On what level would collisions between shaders for example occur? Do they occur when 2 nodes in the same Network have the same name, or do they occur when an object has more than one material applied and nodes in those 2 different networks have the same name?

Also are there any specifics to have in mind when declaring namespaces?

I'm sure the solution is in there, as I think the paths now seem to work fine :)

Thanks!

Btw, if you can reproduce the issue and send me a scene, then I can take a closer look.

It might be a collision in node names. Nodes are identified by names, so if two nodes (two shaders for instance) have the same name in two different procedurals, they collide and the result depends on which procedural is loaded first. You can avoid this if you specify different namespaces per procedural.

I'm not completely sure that's the problem with your scene, but the inconsistencies might come from that.

Hi Peter,

thanks for the new build! I gave it a try, but I again run into some inconsitencies. As far as I can tell the path issue seems to be resolved, but on my first try I got following error messages:

After that I did nothing but deactivate/activate the Procedurals and restart the render a few times and then the Procedurals all of the sudden rendered fine without any problems at all.

I could see that the error messages might occur because I directly convert Cloner-/Surface Spread Objects to ASS, but what I don't get is why they sometimes work and sometimes don't, without anything having changed in the scene/settings.

I only tested for an hour so far, so nothing I said here is 100% certain. If I can help testing in any way let me know!

Thanks again! :)

Could you please try this build? Let me know if the issue is still there.

https://safeshare.solidangle.com/index.php/s/CA5VRslOwaqPhCl

password: 9h5XZWAN

That would be awesome Peter! As always thanks for the great support! :)

OK, I think I see where the problem is. The plugin finds the assets in export time, and so it can send them to the TR client, but it does not actually add the tex folder to the search path. So the low-level assets are not found in render time. Adding ./tex to the search path is not a good workaround, because it's relative to the current working directory, which is undefined inside C4D (not necessarily the project root). This is definitely a bug with nested procedurals. I'll try to fix this on Monday and send you a build.