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

@m_adam Thanks for help!

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

Hi there, I have a similar problem. But I use R25 version. If I write exporterID[c4d.FBXEXPORT_SDS] = True or exporterID[c4d.FBXEXPORT_SDS] = False I get error AttributeError: parameter set failed If I comment or remove this line, export works fine. Maybe I should create a new topic with this issue.

Kindly ignore. Adrian from Redshift forum answered it. You can look into the rslight.h from Plugins\C4D\R26\Redshift\res\description, all the parms are there

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

Hi this bug was fixed with release 2023.0 of Cinema 4D. Cheers, Maxime.

I don't know what your script does and if it needs fixing for 2026.3. What I said is that we usually put a lot of effort into keeping our ABIs and APIs stable, as exemplified with the 2026.3.1 hotfix where we fixed an issue with the UV tag interface that made it incompatible with old code. 2026.3 contained the UV manager overhaul as its main feature. We tried not to break any glass there but I cannot rule it out. when you find a regression in our APIs, you can also always report it. when the break was unintentional we usually provide a fix (in critical cases even a hotfix) or at least a workaround. We also usually do not remove systems. For example, the old content system and its "Content Browser" is still in our APIs and Cinema, although it long has been replaced by the Asset Browser and API. Can I guarantee that the UVPeeler will not be removed soon? No, we sometimes have to remove things. But it is quite rare.

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

@a_block said in ShowInFinder function in Cinema 4D S26: I tend to use GeExecuteFile() to open directories in Explorer/Finder. This seems to work for me regardless of OS. Are there any advantages of using ShowInFinder() instead? Or any disadvantages of using GeExecuteFile(). Absolutely None, except that the name of the function makes more sense if you just want to show the directory. Thanks for pointing that out, i overlooked that line. Bool ShowInFinder(const Filename& path, Bool open) { if (open) return GeExecuteFile(path); Cheers, Manuel

It works like a charm! Thanks a lot!

Hello @Djoneeeee, 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 @thecomishy, 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

Aaaand of course I forgot a crucial point: After modifying the clone positions in marr, you need to write them back to the MoData, but the last parameter apply_strength must be False: moData.SetArray(c4d.MODATA_MATRIX, marr, False) This is at first glance unintuitive since we want the strength to be present but when looking closely, you can fathom that the function will internally multiply with the falloff strength that it calculated itself, and that probably comes from GetFalloffs() again, so it's 0 and nothing is won. We do not want SetArray to do that at all, because we have already applied the falloffs that we calculated ourselves, and SetArray should keep its buggy hands off it!

Excellent! Thanks you a lot Regards,