Alex Hamer

Hi,

This should be fixed in the next daily build, and you should be able to place down a recipe with a karmalensshader node inside.

However the order of some of the parameters may be scrambled slightly.

Bug 139281

Thanks.

Hi fs_reddog.

I was showing you a proof of concept for how you would use a for loop to export based on an attribute. I used primitives as an example. My solution is fairly hacky and was more valid a year ago but PDG can do this much more efficiently, I'd suggest going with Tom's route.

Hi fs_reddog,

I recently did a similar approach, here's a solution I found.

I have a basic setup where I have a bunch of cubes, and each primitive face has its own random value of a set attribute, called 'test'. Not a very creative name, I know.
You'll likely need to do your own setup in terms of getting the specific mesh not just a primitive face, but this reply should hopefully give you a nudge in the right direction.


We then create a foreach loop over primitives.
We then wrangle our test attribute which is a point float attribute, and convert it to a string detail attribute. Make sure you're running over detail so it doesn't make it a string prim attribute.


Then we use a python node to actually run the execute button on our ROP node.


As for having each file be named dynamically, use this script with details() to grab the string detail attribute on the null node.


And as you can see as the result when you run the loop:




Please note this is a fairly hacky solution so that you don't have to leave sops. There are simpler solutions with PDG/TOPs