@kbar said in Plugin compiled on macOS Catalina for R23, not working on Big Sur?: @fwilleke80 I think setting the hardened runtime when you code sign solves the timestamp issue. I don’t set a timestamp. codesign --force --options runtime --sign 'Developer ID Application: YOURCOMPANYNAME' 'sdk/plugins/yourplugin/yourplugin.xlib' Thanks a lot Kent, for pointing this out! The one below is the string I use which, as said by Kent, doesn't need the timestamp because of the hardened runtime. codesign -f -s "Developer ID Application: <YOUR DEV ID>" --options runtime <binary file>.xlib Documentation updated accordingly

I just had time to check this hence the holidays. This works with the correct ID (1036219 = Redshift) the nodes render my "cleaned" C4D file again. Thank you very much @m_magalhaes kind regards mogh

Thanks @ferdinand , I misinterpreted the GetRange argument. That clears it up, and thanks for the example as well, it's very useful!

@m_magalhaes Thank you, Manuel!

hi, thanks a lot for posting the answer. the problem in your first code is that SetUtf32 is that you didn't define your number of character. In the documentation, the count parameter is defined like so: Number of valid characters in the buffer. A count of -1 calculates the string length automatically, terminating when \0 is found 3 solutions : // define the right character number copyright.SetUtf32(&copyrightChar, 1) iferr_return; // define an array of Utf32Char and initialise it maxon::Utf32Char copyrightP[2]{ 0x000000A9 , '\0' }; // Create a buffer in memory maxon::Utf32Char* copyrightP = NewMemClear(Utf32Char, 2) iferr_return; finally { DeleteMem(copyrightP); }; copyrightP[0] = 0x000000A9; copyrightP[1] = '\0'; Cheers, Manuel

Hi @flewis, sorry, there has been some mix-up with access rights, you should be now able to access the page. About your fix: It does not really matter if you do it manually or not. While you can decouple the modification of the node attributes - which is allowed from within a thread - from the redraw event, to carry out that newly computed camera transform, you still will have to invoke a redraw, which you cannot do from within your threaded environment. When you invoke such redraw event, the first thing the internal code does, is to check if its running on the main thread and if not, it just gets out. So there is not much won by doing it manually, at least for what from my understanding is the premise of your problem: To constantly frame the viewport to the object that is currently processed by your async code. Cheers, Ferdinand

Thank you @zipit I adopted your solution into our code and it works exactly as expected. Thank you for your help. Best regards, Tomasz

@zipit Thanks for the detailed info. Much appreciated!

Thanks for the effort Maxime (and rendering department). I suspected that it won't be possible, but still asked because I thought I might have missed something. Cheers, Deyan

I was in deed calling the code from within PluginStart(). Calling it from PluginMessage(C4DPL_STARTACTIVITY) fixed it. Thank you, Kent! Cheers, Frank

hi, thanks for reaching us out and welcome to the forum. Unfortunately, as you can read in our guidlines the scope of this forum is the Cinema 4D's API only. (developing for cinema4D with c++ and python) For other support case/request/suggestion, please contact our regular support I have to remind you that the scene node is still a demo of what we are working on and is still very young. I also have to remind you that the node system is a base where you can create your own assets. Because it's still at a young stage, the node system is changing a lot and your asset could not be compatible anymore with futur release. In your example you can simply create an asset with different aggregate nodes that output all the function you need. In any case, your feedback is appreciated and helpful. Cheers, Manuel

@PluginStudent Thank you so much! It worked! Yaroslav.

Hi @jochemdk, okay, I then took the liberty to close the question You can of course still post here. Cheers, Ferdinand

Hi @Motion4D, I am not quite sure if there will be anything in the pipeline soon, because the limitations of IDs and markers are more of principal nature due to Cinema's heavily procedural architecture; i.e., not really something that can be "fixed". If you have any particular feature in mind, I would ask you to make a separate post with a dedicated feature request. We however already did identify the whole "identifying and object"-thing a few weeks ago as something that is probably not explained well enough at the moment and added it to our to-do-list. There are no guarantees on when this will come though Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by Wednesday and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by Wednesday and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by Wednesday and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by Wednesday and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by Wednesday and flag it accordingly. Cheers, Ferdinand