Hi @mdk7b2, Glad to hear and thank you for sharing your solution! Good luck and let me know if you have any further questions. Cheers, Ilia

Ok, I understand it now better, thanks.

Loud and clear! Thankyou!

Hi @Joel, Thank you for reaching out to us. You might want to have a look at this example script of ours which takes you in a scenic tour through SplineObject handling. I also covered the case of a multi-segment spline there. Cheers, Ferdinand

Thanks a lot for the quick response @ferdinand ! I'll use the raw int values then, thanks

@i_mazlov Hi, thanks for letting me know that. cheers~

Hello @ThomasB , without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly. Thank you for your understanding, Maxon SDK Group

Thank you. I got it working thanks to your hints.

Hello @gheyret , without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly. Thank you for your understanding, Maxon SDK Group

Hey @mikeudin, just as an FYI, one of our engineers pointed out that Description.CheckDescID is the likely culprit for the problem and that this method should be avoided when possible due to its resource hungry nature. Instead, you would just manually define the parameter ID you mean, e.g., c4d.DescID(c4d.ID_TAGFIELDS). The problem with this is of course that this statement has been made disjunct from the dynamic parameters example because I stripped that aspect away in my minimized code. The original code example says: # Fills DescLever type and creator completeId = desc.CheckDescID(descId, None) return True, completeId, tag So, they seem to be only after filling in the data type and creator ID and not resolving multi-level IDs. Which you could also do manually when you know the parameters you want to wrap, e.g.,: descId: c4d.DescID = c4d.DescID(c4d.DescLevel(c4d.ID_TAGFIELDS, c4d.CUSTOMDATATYPE_FIELDLIST, c4d.MAXON_CREATOR_ID)) return True, descId, tag Cheers, Ferdinand

@HerrMay Thanks!

Hey @zauhar, I do not think so that I have told you that, at least I hope so, because that what you say there is not quite correct A vertex map or a vertex color tag can be rendered. When you use the standard renderer, you will have to use the Vertex Map shader, and when you use Redshift, you will need the Vertex Attribute node (just drag and drop the tag in both cases in the respective reference fields of the shaders). Below is an example for the Redshift case: [image: 1686937459914-screenshot-2023-06-16-at-19.41.37.png] Other renderers support Cinema 4D vertex colors too, but you will have to ask their support how that works Vertex Map Shader Vertex Attribute Node Cheers, Ferdinand

Hi Ferdinand! Perfect! We got it, thank you so much for the quick reply.

Hi @i_mazlov, thank you for your reply. Yes, I thought as much. Too bad the take manager menu is not publicy exposed. And while I understand that Maxon as well as the community are not big fans of every plugin messing around with menu insertions, it still is a pitty. One can e.g. insert plugins into the menu of the material manager as done so by "CV-Swim". IMHO it should pose no problem when done carefully with UX in mind while doing so. Especially when one "only" appends entries to a menu. Nethertheless thank you for confirmation. Cheers, Sebastian

Hello @SemyonShapoval without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly. Thank you for your understanding, Maxon SDK Group

Thanks again for the great explanation. I guess I will go for a different workflow then.

Hello @jenandesign , without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly. Thank you for your understanding, Maxon SDK Group

Hi @i_mazlov , This solves my problem, for now I don't think I have another question, and I could consider my problem solved, thanks. cheers, James H.

Yes, thank you so much. This works perfectly. And thanks a million for the in depth explanation.

@ferdinand : The GetAllAssetsNew is a far more elegant solution for the problem I am trying to solve and I've rewritten the code so that it works now. We use Corona render and Redshift so it's a bonus that this works with pretty much all materials. Thank you very much for the help, I will put your information about the layer shader in my database for future reference as I'm sure it will become helpful in another project! Kind regards, Joep