Hi, no, I do not think there is, you can either: Add the vertices in question to a new PointObject, then let Cinema crunch on it (you might have to execute the cache pass on the object, I am not sure about this) and finally use the build in methods to get the bounding box vector. Or, and this is definitely the more sane solution and probably also even in Python the faster one, simply compute the bounding box yourself. You have just to loop over all vertices and find the minima and maxima for each component (i.e. x, y, z) and the average of the absolute of these two values is then the respective component of the bounding box vector. Cheers, zipit

Thanks. In the meantime I made some more experiments, and it seems the problem is limited to when you click Execute in the Script Manager or the Customize Command window. I created a keyboard shortcut and embedded the script as icon in the GUI. In both cases, the status bar gets correctly updated regardless of what window was active / received the key press, and where the icon resides (same window, other window, undocked toolbar). It seems the Python interpreter is not blocking the message loops in these cases. That makes the question somewhat academic, because shortcut or icon (or menu but I did not check that) would be the common ways to start the script; starting it from the Script Manager is common during development but irrelevant in practice. I'm curious to hear what the developers will say about the message loops though.

Hi @pyr I don't think there is anything related to the SDK and its a Cinema 4D bug so I invite you to post it on https://support.maxon.net/open.php On the contrary, if you experience this bug only via a script please post your script here so we can help you. Cheers, Maxime.

I have time and you have my attention sir Manuel! I'm looking forward for this :) I think adding this feature to C4D will be a good improvement... at least, for those who are interested in. Thank you again

Thanks! For whatever reason I couldn't get that particular code to work, but I eventually figured out a different method. I think my script is finished for now.

@Cairyn Thanks for this fantastic resource, I will definitely use this summer to level up with Python.

Thank you very much for your help to solve the previous doubts. I will continue to work hard.

Hi in C++ there is the BaseList2D.IsNodeBased method to check if a BaseList2D contains nodes and more interesting there is the NodeMaterial class that represents a Nodal Material, unfortunately, both are not available in Python. Note also that any type of material can be evaluated to a NodeMaterial and this will add the MaterialData the ability to use NodeGraph. So I confirm the only reliable way in Python to know if a material is a NodeBased one is to check the description. If you want to explicitly create a NodeBaseMaterial the only way for you do to do so is via CallCommand with c4d.CallCommand(202541) # New Node Material Cheers, Maxime.

User can drag and drop the field in the hierarchy and in the field list. So you should have to check every child or every entry in the field list.

@m_magalhaes Thanks for the confirmation. Although what zipit provided also works for my use case (i.e. defining the variable from Document B but using that same variable in Document A) @zipit Thanks for the code. It works as expected :)

Hi, about the time complexity of such algorithm: I only mentioned this, because I was justifying my proposal. Although it is technically an algorithm of high complexity, you should be totally fine on normal use case meshes of characters, which are intended for SDS, i.e. something with less than 100,000 vertices or so. Modern computers are fast ;) As you can see in MAXON's code, they did not utilise any optimisation whatsoever either; there are just two loops sitting on top of each other (they do not even remove the already found points from their comparison array, which puts their code's complexity squarely into exponential territory). But Python is quite a bit slower than C++, so it might be advisable to employ some kind of optimisation in Python. You could could for example use some Dynamic Programming to only compute each point pair distance once. But then again: Modern computers are very fast, you are probably fine with brute forcing yourself to success ;) Cheers, zipit

@m_adam Thanks for the confirmation! (I swear I'm not doing this on purpose...)

@PluginStudent @m_magalhaes Thanks for the reference link and sample code. It works as expected. Thanks also for the giving different methods in setting the strength. Provides more flexibility.

@m_magalhaes thanks, that'll do!

hi, I opened a bug entry. Cheers, Manuel

@Cairyn Thanks for the confirmation. I'll just continue with the revised script until I find a bug (lol). RE: Ah. Don't the built-in mirror functions suffice? Not really. Correct me if I'm wrong, The built-in mirror tool 1) mirrors only the objects itself and not the mirror plane 2) when it mirrors, it creates additional copy. might be good when you are modelling and rigging, but not on animating. Again, thank you for the detailed responses. Appreciate it alot. Have a great day ahead!

@m_adam Thanks for the confirmation. Will close this for now.

Hi @bentraje , thanks for pointing it out. We'll get it filled by a future documentation release. Best, Riccardo

hi, thanks a lot for reaching us out with that issue. i confirm that the code is setting the minimum subdivision to 1 if the command have been migrated (witch it is) I've opened a bug entry and transfert the problem to the devs. I'll come later if I have a more informations. Cheers, Manuel

Hi, Correct it was an unknown error. And yes it not only affect Layer but any kind of GeListNode inserted if they are not already in a hierarchy. I marked this topic as solved, and will bump the topic once a fix is included in a public release. Keep in mind this is a Python only issue. Cheers, Maxime.