C4D might have been 'messed up' based on my prior attempts. I've restarted it and may be making progress.

found it!!! I had to float('0.5')

What I think you're saying is that I don't have to drop what I'm doing to fix my scripts before the team can move to 2026.3 but I probably ought to address it before 2027 to protect against things that are out of my control. Thanks for the response and info Ferdinand.

Hi- How long do you keep functionality in the SDK for a tool that has been deprecated in the application?

I'm trying to get a feel for how long I have to make changes to my scripts that rely on calling the UV Peeler.

Thanks,
Del

Thank you @i_mazlov . I had worked around it by setting it up as a custom color but my preference is to use the display color as I'm already setting that. I'll throw your solution into my project and give it a try.

Do you think this might be changed in the future? If so I want to leave myself a note in the script to revisit the sdk.

Have a great weekend,
.del

Hi - How can I set the icon color in the object manager to use the Display Color? The UX has options for None, Display Color, and Custom.

The sdk and VS Code only show values for None and Custom.

I'm not sure if the value was accidentally overlooked or if I'm approaching it incorrectly. I tried taking a stab at c4d.ID_BASELIST_ICON_COLORIZE_MODE_DISPLAYCOLOR but that did not work.

thanks,
.del

Cinema 4D SDK 2024.2.0 documentation » Classic Resource Overview » Basic Properties

Parameter: Icon Color

Parameter ID: c4d.ID_BASELIST_ICON_COLORIZE_MODE

Parameter Type: int

Cycle Values:

        None (c4d.ID_BASELIST_ICON_COLORIZE_MODE_NONE)

        Custom (c4d.ID_BASELIST_ICON_COLORIZE_MODE_CUSTOM)

thanks @i_mazlov

HI @i_mazlov - I have a script that cycles through polygon selection tags on an object and I'm inserting materials tags next to the associated polygon selection tag that it's matched to.

As far as KIllTag() goes, sometimes I have multiple tags of the same type. I don't necessarily want to remove all of them so starting at a specific index to just remove the tag I wanted made sense. I don't mind using Remove(). It's just that KillTag() is right there in the sdk with all of the other tag related things so that's where I started. I also think that the definition of it made me think that it removed a single tag versus all of the tags of that type "Removes a tag from the object and free its resources."

Do these tags always occupy the same position?

I'm trying things like MakeTag and KillTag that require an indexed position and having two invisible tags is kind of throwing things off. Right now I'm subtracting 2 from the position that I'm targeting but this feels ripe for a script error down the road.

Thank you. I'll have to remember TAG_VISIBLE for future scripts.

Why does op.GetTags() return a polygon tag and point tag even if there are not any on the object?

[<c4d.BaseTag object called Phong/Phong with ID 5612 at 1906901951872>, <c4d.PolygonTag object called with ID 5604 at 1906901936256>, <c4d.PointTag object called with ID 5600 at 1906901964288>]

Hi @m_adam - In this particular instance I'm calling it on objects that have children and I'm getting the prompt to include sub objects. If it were a modeling command or something like that it may include the ability to include or exclude the children programmatically.

I'm creating 30 objects and each object has six flat projections that I want to set to the size of the object. That's 180 confirmation clicks.