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

@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.

HI - Thanks for the response! I'm going to go with the sendModelingCommand method. I never would have thought to put the CallCommand value in there. This is really going to help me finish this script. I appreciate your help. thank you, .del

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