@s_bach Thanks for the response! Works as expected. @zipit No worries. Will close this thread. I will probably revive this a year from now (lol). I have a feeling that Matrix will haunt me again in other aspects so this would be a nice exercise if that happens. Thanks again!

Hi c4dmac, thanks for following up here. With regard to the issue you've reported you can get fixed by reestablishing the executable bit on the kernel_app file found in the zip archive. To sum it up, upon downloading the project tool archive you have to: remove quarantine xattr -d "com.apple.quarantine" ./cinema4d_r21_project_tool_20190903.zip extract the archive (either via terminal or via finder) unzip -d ./cinema4d_r21_project_tool_20190903 ./cinema4d_r21_project_tool_20190903.zip re-establish the kernel_app executable bit chmod 555 ./cinema4d_r21_project_tool_20190903/kernel_app.app/Contents/MacOS/kernel_app Best, Riccardo

Thanks for the input! It's a shame you can't fiddle with the palettes. I think I'll just do it like x-particles and have a command that loads the palette and the user can dock it himself. Not the most elegant, but gets the job done. Cheers

Thank you, Ricardo!

Hi @bentraje beside zipit said which is indeed correct you may found interesting a plugin I made a long time ago when I started python, which has exactly this purpose but also supports specific objects such as sweep, spline and so on. https://github.com/gr4ph0s/graph_bottom_center_axis/blob/master/bottom_axis_center.pyp Cheers, Maxime.

Thank you. That worked like a dream.

@Cairyn Gotcha. Thanks for sharing! @m_adam ". . . but until everything is moved to the new core" That's a nice tease there

@m_adam Thanks! Works as expected!

Hi, reading this thread one question popped into my mind. You wrote: I create two temporary documents with IsolateObjects(), and after getting the required objects created in the new temporary documents, I KillDocument() both at the end. What do you mean by 'get'? If this means just referencing the objects this might explain your problems, depending on what you are doing with the objects. If you pass the object references as part of the results of your GVO and also free the resources of these temporary documents, you are passing objects that might be dead references at the time of rendering, giving an explanation for your problems. Also: When you just remove the resource freeing of your temporary documents, I do not think that they will be freed automatically by Python's garbage collector. The reason is: While the reference count for these document objects (objects referring here to the Python type) is zero after the scope of GVO has closed (making them candidates for collection) the referenced output objects (here referring to the Cinema type) are still alive and they do reference these document objects. Which would cause your temporary document objects to stay in memory. Which would not be too bad, since it would always be just the two documents and not an incrementally increasing amount, a.k.a a memory leak. Long story short: Clone your objects if you want to pass them as the output and flush the documents afterwards to make things easy for Pythons gc (which is one of the main reasons why Python tends to be bloaty/slow). Cheers zipit

Hi final3d, thanks for writing us. Please file your suggestions and recommendations on Maxon Support page paying attention to select "Suggestions and Ideas for Maxon". This forum is only aimed to discuss development-related topics. Best, Riccardo

Hi Maxime, thanks for trying! I'm also sure it's not specific to C++. I'll send you some code as soon as I find the time to strip it down. Cheers, Frank

Hi @m_adam Thank you for reference. It works as expected. Have a great day ahead!

Hi As Kent stated if it's a Cinema 4d frameworks you should put it in the framework directory. This way it will be accessible with APIS=common.framework in your projectdefinition.txt For more information, take a look at the Custom Framework Manuel. If you have any questions, please let me know. Cheers, Maxime.

Thanks for your advice. The build is complete. It was because VS2017 when Unity was installed was old. Now you can build other plugins. Thank you very much.

@m_adam RE: The A seems to be present until there is a target. Thanks for the clarification. That make sense. Your code works as expected. This is just a trivial question. In the documentation for the CAPoseMorphTag.ExitEdit it says: Must be called before doing anything to a morph tag. Shouldn't it be named EnderEdit? Since we are editing the morph tag or calling the ExitEdit after actually editing the morph tag? Again trivial but just seeking some clarification.

hello, I'll mark this thread as solved tomorrow if you have nothing to add. Cheers, Manuel

hello, I'll mark this thread as solved tomorrow if you have nothing to add. Cheers, Manuel

hello, I'll mark this thread as solved tomorrow if you have nothing to add. Cheers, Manuel

Hello, Really sorry about this issue. Would it be possible to send us a scene and some screenshot maybe to reproduce the behaviour ? That would be really appreciate. I will send that to our devs. You can use our mailbox [email protected] Thanks and cheers, Manuel