Hello @wuzelwazel, thank you for reaching out to us. I am sorry if I gave you the impression that this will be fixed with S24. This issue is still on our radar, but it does not have the highest priority. I am also unfortunately not a liberty to give you a time frame when this will be done. Thank you for your understanding, Ferdinand

Dear user, thank you for reaching out to us. Is it possible, via C++, to add a command to the right click menu that pops up for a parameter in C4D? Unfortunately, that is not possible. The context menu of a DescriptionCustomGui is sealed off from user access. The specific context menu is not meant to be modified. I would like to call a command and somehow get the parameter that was right clicked on as well. I don't think this is possible at all, but can't hurt to ask just in case. You are right, this is also not possible, at least in the context you are most likely talking about. You can get hold of the selected element(s) in a DescriptionCustomGui via GetDescIDSelection() (Link), but this requires one to get hold of that DescriptionCustomGui obviously. Since you are very likely talking about the Attribute Manger, this is effectively not possible, since you cannot get hold of it from the SDK side (in the way you want to). For a custom GeDialog with a DescriptionCustomGui this would be possible. While we can technically get hold of an Attribute Manager when implementing nodes, I do not see a way to get hold of its DescriptionCustomGui nonetheless. Cheers, Ferdinand

Hi @ferdinand, Your explanation and the given example solved all problems. I don't know why I did not found that earlier. Thanks, Chris

@m_adam Thanks for confirmation. Will close this thead now. Looking forward to the documentation

Hello @pim, without any further feedback or questions, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @JH23, without any further feedback or questions, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello @AiMiDi, without any further feedback or questions, we will consider this topic as solved by Wednesday and flag it accordingly. Thank you for your understanding, Ferdinand

Hello Maxime, Thanks for fixing the category for my post. I am new to Cinema4D. I found the correct IDs by opening the UI for the material and drag and drop the settings into the Python console. Kind Regards, Chris

Aha I see, this makes sense for the NormalTag data. And yeah of course cross product is what I need... Regarding the primitives not turning into polygon object, I thought that was happening with a cube, but now after testing it again it definitely is. So I must have been mistaken before. Thanks for the help, going to mark this as solved.

Thanks for the investigation. At least now we are aware the problem is not on our side. Cheers, Deyan

Hi @Yaroslav this is indeed possible however a bit clunky for the moment, but here a full step by step. Install pip with c4dpy -m ensurepip Install Python Visual Studio Debugger with c4dpy -m pip install ptvsd. Within Visual Studio in your launch.json just set up a basic attach setting, here is mine but for more information see Python debug configurations in Visual Studio Code. { "version": "0.2.0", "configurations": [ { "name": "Cinema 4D: Remote Debugger Attacher", "type": "python", "request": "attach", "connect": { "host": "127.0.0.1", "port": 3000 }, "pathMappings": [ { "localRoot": "${workspaceFolder}", "remoteRoot": "." } ] }, ] } The *.pyp plugin should be of course in the same workspace as your launch.json. Edit the *.pyp plugin and write the next code in the first line of your pyp file. import ptvsd ptvsd.enable_attach(address = ('127.0.0.1', 3000)) Start Cinema 4D, wait until its UI is loaded, meaning the pyp plugin is loaded, and the client (your script) is attachable from a debugger. Run the previously created debug configuration (called Cinema 4D: Remote Debugger Attacher). Put a breakpoint somewhere (like in the Execute of a CommandData) to trigger the BP. Enjoy Note this also works nicely for the script, however for script you should call ptvsd.wait_for_attach() after the ptvsd.enable_attach. Cheers, Maxime.

@Cairyn @ferdinand Thanks for the response. Printing the base container with their indexes worked in my use case

@Cairyn Thank you for your help ! That's it. I confused it all with the wrong word. Sory... Your answers help me very nicely @ferdinand I apologize about going out of the guidelines. I understand this and will create new topic for that point

Thanks for your answer, it solved my problem. Thank, AiMiDi

Thanks for your answer, it solved my problem. I used: Vector::ClampMax() and Vector::ClampMin() to limit the tangent to the value I want. Thank, AiMiDi

Thanks, Maxime! Looks like I have it running flawlessly now. good work on Terraform looks solid! Thank you! It is pretty solid, yes Cheers & happy Easter, Frank

Thank you @bentraje and @ferdinand ! You make the deal of the EffectorList function much clearer ! It works well now

Hey guys, thanks for the explanations. My only concern is that I can't really do anything besides closing Cinema4D to cancel the operation. Just for reference my plugin is a fluid volume that needs to be visualized in the viewport. This is not an expected workload, stumbled on it by chance, but so can one of the users. Anyway we can close this thread if it's not a bug. Regards, Georgi.