Hi, I am glad it does help you. I forgot to mention one thing, which is worth pointing out, when somebody stumbles over this thread, searching for performing edge selections. The way I treat edge selections in this script only works because of the specific scenario - selecting edges that are only associated with one polygon. In all other cases you have to select two edge ids (one for each polygon) for each edge or use the convenience methods of c4d.BaseSelect for that. Otherwise you will end up with a corrupted edge selection. Cheers zipit

Hi fyeng, thanks for reaching out us. With regard to your question, I confirm that the workflow you're trying to achieve using the python executable found among the Linux CLR modules is not possible since only c4dpy, as you've already seen, has access to all the needed modules. Best, Riccardo

Hi angel23, thanks for reaching out us. With regard to your question the answer can be pretty wide depending on the depth you're aiming to tackle. Cinema 4D comes as @bentraje properly stated with C++ and Python APIs: whilst the first is bigger and more comprehensive the second is a specialized subset of the first and easier to approach. For the Cinema 4D API newcomers we recommend to stick to the Python API which gets rid of all the hurdles of the building process and to get proficient with it. Upon getting used to it and to the foundation Cinema 4D API concepts, moving to C++ won't be too complex. Best, Riccardo

@zipit Thanks for the insight! This makes sense, I vaguely recall typo-ing random.seed and forgetting the () and it threw an error so I fixed that, went writing more of the code and then didn't relate this error back to that brief moment. I don't recall assigning it as a property, but I do have a seed = 12345 elsewhere in the code, so maybe I did! Thanks all for sanity-checking it, solved. cheers, brasc

@m_adam thanks

@m_adam Thanks for the additional insight and the related links. Appreciate it a lot.

Hi @daltonmonaie, could you open a new topic for the last things regarding the update of the render path and post all your code if possible so like that we are sure we speak about the same things. Cheers, Maxime. I've created the new topic, please continue the discussion on this one: Update Render Path in an Xpresso Node.

Hi, @Xplorer do you have any example in Cinema that would have similar behavior? If you could explain in detail or give example especially the second part of this sentence "load in c4d a particular object already modeled, and also have it hidden to stay focused on the settings and sliders available in the plugin." it will be nice. Cheers, Maxime.

Hello, Thanks again @zipit for the fast and nice reply I also move this thread to general programming as it's not related to Cinema 4D Cheers, Manuel

@m_magalhaes said in Cinema tools local development, control and deployment: And if you find something in your side, sharing that would be awesome. Absolutely!

@m_adam Thank you very much ! it is certainly helpful !!

Hi hhgemalmaz and thanks for reaching out us. With regard to your question I warmly suggest to read the Cinema 4D C++ documentation get familiar more specifically with the Getting Started topics download the Project Tool[URL-REMOVED] used to create specific IDE solutions/projects for the different projects provided with the sdk archive shipped with Cinema 4D. unarchive the sdk.zip in your preferred folder execute kernel_app_64bit.exe g_updateProject=<your full path to sdk> open the solution in your IDE build the examples shipped in the sdk.zip archive. If your Cinema 4D version is older than R20, then you can skip steps 3, 4 and 5 since solution files and API folder are already available in Cinema 4D installation path. Best, Riccardo [URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.

I'm not sure it's a bad habit or what's the difference. There's maybe type conversion, i don't know. Or maybe with the code optimization there's no difference at the end. I just wanted to add my 2 cents to have bool and not value xD Cheers Manuel

@m_magalhaes all good my end! Am interested to see the further example when available (if nothing else, just to add it to my examples kitty!). Cheers, WP.

Hello, this is a support forum for plugin developers (About This Forum). For general questions on how to use Cinema 4D you might want to consult a more general user forum like c4dcafe.com or forums.cgsociety.org best wishes, Sebastian

@Graeme Thank you very much! @r_gigante Will do, thanks.

Hi @mikeudin, thanks for reaching out us. With regard to your request, although it's not expected it to work inside the Cinema 4D Script Manager you can get it properly working using the c4dpy executable (here's the 20.059 compatible version[URL-REMOVED]) as much as you do on the Python Shell or on SublimeText console as you can see from the log below. $ more test.py import inspect # Save this code as script py-file and start def main(): code = inspect.getsource(main_new) # place function code to str variable print code # print code text. Works on Python Shell, but not in C4D Scripts Manager def main_new(): # This is a comment # New comment string # Change this code, to check the console output pass if __name__ == '__main__': main() $ ./c4dpy.app/Contents/MacOS/c4dpy test.py def main_new(): # This is a comment # New comment string # Change this code, to check the console output pass $ Best, Riccardo [URL-REMOVED] @maxon: This section contained a non-resolving link which has been removed.

Sorry for late reply, there was an issue with my account. Many thanks for comprehensive answers. The topic looks kind of mind bending now, not much easier than after I realised Api doesn't really have what I expected to have for the task accomplishment Now I think the better way might be to simulate the mouse over the viewport, so it will be an independent app which will only need from the Cinema to know where the viewport is. That seems easier I hope. When my research or development will reach some success I will share what I learned here, maybe it will be handy for somebody else. Thanks once more!

@Cairyn and @m_magalhaes Thanks for the responses. The dictionary route seems like a good workaround. I think I'm going with it. Have a great day ahead!