@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

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

Good to hear, thanks!

Hi @delizade, without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

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

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

Hi @Hugo-BATTISTELLA , without further questions or feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

@zipit Thank you very much, Ferdinand. This helped me a lot!

@zipit Thank you for the information.

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

@r_gigante Thanks for your help!

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

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

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.

Ok, clear. Thank you.

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

@gsmetzer said in Adding multiple cameras from a single file to the render queue: My only question: Can you run this script without saving a multiple iterations of the source .c4d file to the OS? Sadly, this is not possible, you are forced to create a c4d file each time. However this is a feature we will tackle in the future, but I can't say when neither give any guarantee. Or, is it possible to delete the source .c4d file iterations upon completion? You can iterate all elements, call GetElementStatus and check for its finish state. If you need help to achieve that please open a new topic. Cheers, Maxime.