@m_adam Thanks so much! You are a very professional guy!!!

Sorry for the late reply In order to do that you will need to start a new thread, and you need to keep alive the thread as long as it execute, meaning you will need to store it in a global variable. Best way would be to reach octane directly as 3rd party are free to implement this as they want. Cheers, Maxime.

Hello @LingZA, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand

@m_magalhaes Thank you!

Hello @lingza, well as lined out, you cannot implement a VertexmMapTag which is the same as a normal VertexMapTag but has extra parameters to realize your desired functionality. You can solve this problem with either the pattern I described under point 3 in my last posting, or by implementing a ToolData plugin which simply generates the tag. The solution using a driver tag has the advantage that the user can continuously tweak the output of the vertexmap, while a tool must be picked up again. Actually, I mean that I want to create a tag which contains the vertex weights, then vertex weights are used by ZRemesher after I put the tag into Density Map linkbox. So I don't need a "vertex map" indeed, but I need a tag I describe above. This is unfortunately not true. You will need a vertex map tag, as this parameter, the Density Map parameter, will accept only a VertexMapTag. It will not know what to do with a CustomDataTag . I would recommend having a look at the project file I have posted above, it contains a practical example for the pattern of a tag driving a vertex map. Cheers, Ferdinand

Thanks for the update!

@noseman seems that it's needs to be updated https://github.com/nrosenstein-c4d/c4d-prototype-converter/issues/52

Thanks so much!!! Your answer makes me understand that PolygonObject.GetPolygonS(self) and PolygonObject.GetPolygonH(self) respectively represent selection states in a list from BaseSelect and visibility states in a list from BaseSelect.

@ferdinand thanks for explanations and example.

Hello @Peek, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand

Hello @blastframe, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand

Hello @DGLopez, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand

Hello @will_blizzard, without further questions or postings, we will consider this topic as solved by Wednesday 31/05/2023 and flag it accordingly. Thank you for your understanding, Maxime.

Hello @mikeudin, Thank you for reaching out to us. Vectors represented by the type c4d.Vector are immutable in Cinema 4D, so one intentionally cannot change one of the components of a vector after it has been instantiated (matrices are not immutable over their vector components on the other hand). To achieve what you want to do, you must write: old = Cube[c4d.ID_USERDATA, 2] Cube[c4d.ID_USERDATA, 2] = c4d.Vector(old.x, old.y, 12) The following would also be possible, but it is not an improvement IMHO: Cube[c4d.ID_USERDATA, 2] = c4d.Vector(Cube[c4d.ID_USERDATA, 2].x, Cube[c4d.ID_USERDATA, 2].y, 12) Cheers, Ferdinand

@m_magalhaes - All good! Just wanted to make certain that the issue hasn't been fixed yet (since 2018..). In the future I'll write a python class, extending a group that is collapsible using the workaround you mentioned. Thank you for getting back to me and looking into this! Cheers.

Great, thank you guys!

Hello @m_magalhaes , Thanks a lot for the tip, works perfectly as you said [image: 1652754301818-cinema_4d_f7fynzcvz4.gif]

Sorry for the late reply, my issue went away after reinstalling C4D so I forgot about it Thank you for your feedback

Hello @byoneukp, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand

Hello @jesse, without any further questions or other postings, we will consider this topic as solved and flag it as such by Friday, 17/06/2022. Thank you for your understanding, Ferdinand