Good morning Hugo, I think that is possible with a Python Effector, unless I do completely misunderstand you. If I understand you correctly, you want to do the following: Map the particles in your Boules cloner from to the particle positions in your M_FIG_01 cloner. You want to be able to animate the whole process, i.e. (linearly) interpolate from a starting position of a particle in Boules to a end position in M_FIG_01 You also want to be able to offset the animation for each pentagon point group in Boules, so that your particles "depart in waves". One and two are relatively easy to do, you only have to make sure that both particle systems/cloners have the same amount of particles (which you did ;)). Number three is a bit more tricky when you have more complex inputs for Boules, but in your case you can simply group the particles in Boules into groups of five, to get the particles for each pentagon. You then have to get the particle system of the M_FIG_01 cloner and simply interpolate between the positions of the particles. But to do that in a meaningful way, you will have to cache the starting positions of your Boule system. I cannot write the script for you, but I can guide you through the process. I would recommend first removing all clutter from your scene (unnecessary objects), so that you only have the two cloner/matrices and one Python Effector. Then write just a piece of code for a Python Effector that loops through all particles the effector is applied to (Boules) and print out their positions. Also try to group them into their pentagon groups. Come back when you are done or encounter problems :) edit: I did the tagging for you, but you can find the tags in the lower left corner of the posting editor. Cheers, Ferdinand

@zipit I just read this（Connect C4D with Tkinter） post，It does seem to help me Thank you again！

Hi @pyr, thank you for reaching out to us. I am afraid we will need a little bit more than that, as otherwise it will be very hard to answer your question ;) What kind of plugin do you implement? What does it do or what would you consider as running? On a very abstract level you cannot really prevent plugins from running other than not registering them at the start of the application. But you can of course modify their output depending on basically everything, including render events and at what time offset some given document is. Cheers, Ferdinand

Hi @Cairyn, yes, writing snap tolerances to these tool specific containers is not being respected. And after some further investigations I have come to the conclusion, that most things written to document snap settings (even the global settings) will be ignored. A workaround, which oddly is also done by Cinema internally, is to just invoke the respective plugin command for the snap implementations. I will have to ask the modelling team on Monday, why things are implemented this way and subsequently why they did choose to keep the snap settings around in this manner. In the mean time please take a look at the script below, which shows you how to read and write to SNAP_SETTINGS_TOOL with this rather odd approach. Cheers, Ferdinand import c4d def main(): """How to weasel your way around SNAP_SETTINGS_TOOL. The same approach can be applied to other snap tools (basically everything you can turn on or off in the snapping tool bar). """ # Get the command state. state = c4d.IsCommandChecked((c4d.SNAP_SETTINGS_TOOL)) print ("Tool Specific is enabled:", state) # Toggle the command. c4d.CallCommand(c4d.SNAP_SETTINGS_TOOL) # Get the new command state. state = c4d.IsCommandChecked((c4d.SNAP_SETTINGS_TOOL)) print ("Tool Specific is enabled:", state) if __name__ == "__main__": main()

Hi Manuel, thanks for getting back to me! The size of the bitmap you want to display ? It's 320x116 pixels. Do you want to bitmap to scale when you scale the GeDialog ? No. I rather want the dialog to be just wide enough to fit the bitmap in it. And that seems to happen automatically. Even if I open the dialog with a width of e.g. 100 px, it doesn't get any smaller than (width_of_bitmap + strange_gap * 2). Is it possible that it's a macOS-only issue? Maybe it's the radius of the windows' round corners that gets added to the size. Anyway, maybe this issue isn't worth spending more of your time on. Since it works with a ASYNC_POPUPEDIT style dialog, I think I can live with what I got.

hi, Confirmed, thanks @mp5gosu. That also work if the shader is inside another shader. Cheers, Manuel

Hi Manuel, thanks for the info! If smooth is set to false, the wrong positions disappear in deed. The distribution of the positions, however, is much uglier. It requires the user to change some specific attributes of the spline to make it look nice. But I think, that's ok for now. Thanks again & greetings, Frank

Thank you for the detailed answer. and indeed, I can confirm that a plug-in (Reeper 3.2 SE) loaded as a trial for R21 is working properly. I will now contact Paul Everett directly first.

Thanks for confirming! The strange thing is that I can reproduce this even in R20. Seems, not many people use this function to open URLs. I'll mark this as solved then, as my solution presented in this thread works flawlessly on all R2x releases. Cheers, Frank

Hi, I did not really expect an answer, I just did put it up to make you guys aware. Regarding your reply, I agree with most of it and am aware that there a some hurdles to overcome in mapping C++ interfaces to Python, i.e. that you do run into problems in general when you want to express overloaded methods in Python. But as @mp5gosu pointed out, my major point was that the function does not accept named arguments at all. Which is mainly a problem because the docs tell you explicitly otherwise in two ways. First of all the docs say explicitly that all arguments are optional which implies for Python usually that I can pick and choose in which arguments I can pass by passing named arguments. And secondly, you print out the signature as Vector.__init__(x=0.0, y=0.0, z=0.0) which implies the same. I would have probably ignored all this and booked it under "that's for me to know and for you to find out", if it wasn't for the fact that the method does not raise a TypeError on attempts of feeding it with such unknown named arguments. Which can make this quite critical IMHO. Cheers, zipit

Hi internally as stated in the documentation of GeListNode._setitem__ and GeListNode._getitem__ it's just a wrapper arround respectively C4DAtom.SetParameter and C4DAtom.GetParameter. Then Set/GetParameter will call the respective NodeData.G/SetDParameter of the GeListNode implementation. This method lets you define how the parameter access is done (aka retrieving the data from a local member variable or reading the base container made by the description). So if we go back to the s/getitem, internally in python it builds automatically a DescId based on the data provided doing a stupid If pyData.Class == PyBool: DescId(pyData, DTYPE_BOOL, 0) so you can easily reproduce this part too. But I don't think in C++ you can't support multiple arguments in the bracket operator see C++ [] array operator with multiple arguments?, so you could somehow hack around with the usual () operator, but our classic API doesn't really provide a mean of inspection so you will need to either do a lot of overrides or have unsafe void pointer arguments while PythonObject always has a type attached to them so you can at any time accept a PyObject* and retrieve is real DataType, and this is exactly what is possible to do with the MAXON API where you register datatype as MAXON_DATATYPE then they all can be retrieved in the form of a maxon::Data but you still have access to its maxon::Id and you can know the datatype ID and doing a safe casting. Hope this answers your questions. Cheers, Maxime.

@m_adam Thank you for your answer. C++ documentation have a "Example" show how to use flags in CAMorph.SetMode, but python documentation not (at least in R21.022), i compared the C++ code with Python, then went back to the C++ documentation and found this.

RE: This is a limitation you also have with the visual selector Not really. You can multiple select hotspots and/or controllers in the visual selector. Anyhow, thanks for the response. I guess there is no way around this.

@r_gigante Thanks for the response and the website reference. I was able to work the code with the following revisions: def CoreMessage(self, id, bc): if id == 1234: P1MSG_UN = bc.GetVoid(c4d.BFM_CORE_PAR1) pythonapi.PyCObject_AsVoidPtr.restype = c_int pythonapi.PyCObject_AsVoidPtr.argtypes = [py_object] P1MSG_EN = pythonapi.PyCObject_AsVoidPtr(P1MSG_UN) # check message and act if (P1MSG_EN == 1): c4d.documents.GetActiveDocument().InsertObject(c4d.BaseObject(c4d.Ocube)) elif (P1MSG_EN == 2): c4d.documents.GetActiveDocument().InsertObject(c4d.BaseObject(c4d.Osphere)) Thanks again. Will close this thread now.

@Cairyn @zipit @m_magalhaes Thanks for the detailed response. After installing the C++ environments, it works as expected. Sorry new to this. As I only have python to reference for. I also managed to build the plug-ins using this guide: https://plugincafe.maxon.net/topic/10967/compiling-the-cinema-4d-r20-c-sdk-examples

@m_magalhaes Ah gotcha. I guess there is no way around this, yet. Thanks for the confirmation.

@zipit said in Unable to Set Priority Data for Skin Deformer: probably overlooked correct, friday evening