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

Hi Jesse, thanks for the report those issue have been fixed and will be up in the next update of the documentation. Thanks a lot for reporting them and if you see other one please report them ! Cheers, Maxime.

@cairyn It Works. Thank You. Very Much.

Hi @m_adam , It is unfortunate because I thought it would be useful if it were available, but I understand. Thank you for your prompt response!

Hello @kalugin, 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

Thank you for the swift reply though

Hello @bentraje, 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

hi, i confirm this is the right way of doing it. Be aware that the legacy mode has been removed now from the UI but is still accessible from python. If you define the legacy mode, the user will not be able to get back to normal mode. Cheers, Manuel

@m_magalhaes Thank you very much for your reply. Target was to let user run my plugin in pyton script without open its gui, but set options by some command. Meanwhile I came to solution by implementing ExecuteOptionID method. In this way user first sets options in gui and after can CallCommand anywhere he wants in scripts. Again thank you for your time.

Hello @render_exe, without any further questions and 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 @chuanzhen, 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