Thanks, it is working.

Hi, you cannot, because the data container of a BaseList2D is not dynamically typed (like Python itself), but bound to data types specified in its description. If you want to change the data type of an user data element, you will have to modify the description of that element via GetUserDataContainer and SetUserDataContainer. There is also no 2D-Vector type in Cinema, only the crosshair thing custom GUI which you can apply to a Vector description element. Cheers, zipit

Hi @Eduardo-Oliveira first of all welcome on the PluginCafe community. I think @zipit already provided you some correct answers or at least point you that this workflow is kind of strange for a Cinema 4D user since normally the object by itself doesn't really set its own position, but it's up to a tag (constraint Tag) to define the object position to another one. But in case you really want to do it, doing it in the Execute method of your ObjectData is fine. def AddToExecution(self, op, list): list.Add(op, c4d.EXECUTIONPRIORITY_GENERATOR, c4d.EXECUTIONFLAGS_CACHEBUILDING) return True def Execute(self, op, doc, bt, priority, flags): op.SetMg(doc.GetFirstObject().GetMg()) return c4d.EXECUTIONRESULT_OK You also need to ensure you registered your object with the flag c4d.OBJECT_CALL_ADDEXECUTION so AddToExecution and Execute are called. Cheers, Maxime.

Thanks will close the thread for now.

@zipit Thanks for the confirmation!

Hello, thanks for the answer by the way you could also clone the renderdata, modify the clone and send it to as a parameter to the function RenderDocument. That way, you don't have to "restore" them. Just in case, don't forget that data may not be saved in the BaseContainer. Cheers, Manuel

The bug is fixed in R23. Cheers, Maxime

@PluginStudent Thanks for the explanation. Your solution works as expected

@m_adam said in PolygonObject.SetSelectEdges() and the Neighbor() class, a giant dilemma: ... Hope it answers your questions, Cheers, Maxime Thank you Maxime, this is a lot of useful info. Let me think through all of this and reply here if I have any further issues.

Realizing I never responded to this Thank you @m_magalhaes, @mikegold10, and @PluginStudent. I ended up manually making a list of the parameters I wanted to copy and iterating through all of them. Not ideal, but at least glad to know there wasn't an automated method I was missing.

@bentraje I don't have that much to add on your topic since I think @zipit already explained everything nicely. In any case some good resource for you about how global variable works in Python Global keyword in Python and Mutable vs Immutable Objects in Python. Regarding your last question, I think you should open a new topic, but the short answer there is no way to pass directly a variable with a MessageData, the best way is to use a scope accessible by both part and store this variable in this shared scope (can be global or any other). Cheers, Maxime.

Got it. Thanks, again, zipit for you answer.

@Cairyn @zipit @C4DS Thank you all for the responses. I ended up with @C4DS suggestion in using SpecialEventAdd() and CoreMessage for simplicity sake. Have a great day ahead!

@m_adam Thanks! Works as expected

Hi, thanks, that answers all my questions. Cheers, zipit

Thanks @moGRR for reaching out us. With regard to your question, as pointed out by @zipit, it's not possible to have a Python Generator to generate object which can be recognized as real spline by generators/deformers expecting a spline as input due to the Python Generator flags used in its registration. Beside the option mentioned by @zipit I also invite to have a look at this post where it's presented a generator outputting spline and accepting splines as input. Best, R

hi, I'll set this thread as solved without feedback from your side. Cheers, Manuel

Thanks for the clarification. Have a great day ahead!

Hi @fwilleke80, unfortunately, I confirm the shader effect is almost always dirty. I don't have any real workaround maybe you can retrieve all noises and compute their dirtiness, but this is indeed a very hard topic to handle all cases because you will also need to handle the actual parameter of the shader effector itself. Cheers, Maxime.

@zipit Thanks for the response. You are right. It should have worked if there is padding between buttons. For now, I just chose either buttonData["w"] or buttonData["h"]. And it works as expected. RE: hard to read your code due to the lack of documentation and its disregard of PEP8 Sorry about that.