@m_adam said in Force update interface of the plugin: Regarding advice from @mp5gosu, MSG_CHANGE is only needed when the structure of the object change (you change the count of point for example) since SetParemeter will automatically increase the dirty count of an object is not needed in your case. Sorry, I actually meant EventAdd().

Hello, please see here: https://developers.maxon.net/docs/cpp/2023_2/page_maxonapi_programming_advice.html and especially here: https://developers.maxon.net/docs/cpp/2023_2/page_maxonapi_dev_windows.html (Windows includes)

Hi, actually this is not a bug, but a design decision. Here at MAXON we have a pretty large code base and especially disabled code branches tend to age a lot faster. So we try to force developers to also maintain such code pieces or to at least think about, if they are still valuable and otherwise remove and thus cleanup the code base. Cheers, Andreas

Hi, glad you were able to solve your problem. We'll take this as a hint and see if we can improve our documentation in this regard. Cheers, Andreas

@a_block Thank You so much Andreas ! I would like to try all the suggested approaches and hopefully I'll get my issue resolved (except second option is out of my context as I can't use another application). Third potion seems to be the best suited option and I would like to give it a try. Thanks Again...!

Thanks for the responses guys... I think I've found a virtual solution/work-around for the time-being. Cheers.

Thank you, Sebastian. Your reply clearly shows what I should learn. I need a little time to understand, but I am working on it and I made a little progress. Cheers Makoto

Hi rsodre, thanks for writing us. The Cinema 4D SDK has it's own structure which actually needs that both the plugins and the frameworks folder share the same parent folder and this is what the SDK toolset (sourceprocessor and projecttool) expects to work with. Any change to this structure may lead to unexpected behaviors and is highly discouraged. Using the workaround you pointed out in the projectdefinition.txt is not expected to work as you've already checked. On the contrary using symbolic links seems to work, but again this is not officially supported. For the sake of completeness the ln command I used is ln -s <path to frameworks> <path to plugins>/../. and I succeeded to compile all the shipped plugins under macOS 10.13.6 with Xcode 9.4.1 Cheers, Riccardo

@mikeudin Thanks for making us aware. We'll change the link with the next docs update.