Correct here are all the one we expect to fail: bz2 curses gzip lzma zlib As a quick reminder, Python 3.7.7 doesn't officially support M1, and only Python 3.9.1 (released in December does fully support it). Cheers, Maxime.

hi, one side note, there is GetDEnabling and GetEnabling you can have more information in our manual GetEnabling will call GetDEnabling. There are pretty the same but the one you implement is GetDEnabling. Cheers, Manuel.

That's okay, since it is a minor issue. For newcomers however, there should be a hint in the docs, because it clearly states Sorts the container entries by ID. which is not the case.

@blastframe said in Updating F-Curves in Timeline on EditSlider Drag: What's c4d.EVMSG_FCURVECHANGE for then? After a quick check (sorry, I should have checked yesterday for a more complete answer) literally nothing. It's used nowhere. Cheers, Manuel

@ferdinand Thank you for this; it makes things much clearer. I am very grateful we have the forum to clarify these issues.

hi, you can have a look at our manual about MachineInterface you will find all the machine information under those attributs Cheers, Manuel

@ferdinand That was exactly what I was seeking, thank you, Ferdinand!

Hi @blastframe, thank you for reaching out to us and for reporting these errors in the documentation. We will fix both the erroneously attributed short description of AddKey as well as the code example in an upcoming update of the C4D SDK Python docs. Cheers and happy coding, Ferdinand

Hi, @m_adam, thanks for the effort. I suspected it will not be possible without a custom GUI/data implementation - I guess I will go with this approach. Cheers, Deyan

@ferdinand Hi Ferdinand, Thank you for your time and help! Will get it sorted with your pointers above. All the best! Andre

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