Found it! ☺

c4d.documents.IsolateObjects(doc, t_objects)

A helper routine to copy the objects t_objects of document doc to a new document (returned). All materials associated are also copied over and the links are corrected.

Parameters:
doc (c4d.documents.BaseDocument) – The document that contains the objects in t_objects.
t_objects (List[c4d.BaseObject]) – The objects to isolate.
Return type:
c4d.documents.BaseDocument

Returns:
The document containing the isolated objects.

Thank you all ! 👍

Hi Maxime, thanks for the response! I was aware that the scene gets copied, but unaware of the GetDocument function so it definitely makes sense! I will give that a try and report back. I have been trying this with both a python effector, as well as in a python xpresso node.

Andrew

Wow, thanks so much for this complete Example, Maxime..!!!
Great work, really appreciated!

Cheers,
Lasse

hello,
thanks @tummosoft, it's nice to see it's helpful 😄

@ilad
By the way instead of ID_BASEOBJECT_POSITION you could have use ID_BASEOBJECT_REL_POSITION. Both Ids are the same.

If you want to know how to get those ids you can use the python console and drag and drop parameters, more information on this page

In this case the DescID is composed of two DescLevel. The first define the Vector type, the second de Float type for X, Y and Z.

(DescID can have less or more levels)

To change the Size.Y of the cube, the descID will be :

c4d.DescID(c4d.DescLevel(c4d.PRIM_CUBE_LEN, c4d.DTYPE_VECTOR, 0), c4d.DescLevel(c4d.VECTOR_Y, c4d.DTYPE_REAL, 0)))

To change the scale of the object the descID will be :

c4d.DescID(c4d.DescLevel(c4d.ID_BASEOBJECT_REL_SCALE, c4d.DTYPE_VECTOR, 0), c4d.DescLevel(c4d.VECTOR_Y, c4d.DTYPE_REAL, 0)))

Cheers
Manuel

@rsodre : looks like it.

@r_gigante
Thank for your professional help! I am so grateful for your commitment!☺ 👍 👍

Hi @m_magalhaes

Thanks for the response and clarification specially with the
def __init___ and def InitValuesthat was news to me.

The plug-in works as expected. Have a great day ahead!

Hi Riccardo,

Thank you for the detailed answer. With the many options available, I chose one that fits best with our installer.

Again, thanks for the help!

Maxime

@mfersaoui said in Automatically add effector object into In-/Exclusion User Data:

@m_adam Thank you,
Now I'm searching for how to add an Object to an In-Exclude user data. I tried with the following code but this doesn't work.

import c4d def main(): effectors = op[c4d.ID_USERDATA,2] # In/Exclude User Data plain = doc.GetFirstObject() # Plain object (Effector) effectors.InsertObject(plain, 1) c4d.EventAdd() if __name__=='__main__': main()

The actual issue is that effectors = op[c4d.ID_USERDATA,2] perform a copy of the InExcludeData so that means you have to reassign the data correctly after it since you don't do the change directly from the InExcludeData of the BaseContainer.
op[c4d.ID_USERDATA,2] = effector

Cheers,
Maxime.

@s_bach Sorry, I just saw your message. the replies notifications was disabled.
Thank You!

hello,

we did run a couple of test and seems that the "issue" is on Patreon side.

HTTP Error 403: Forbidden

We did try with other url, it work.
We did try adding header-agent or things like that, it failed.

They probably changed something on their server that doesn't allow to connect with python with default parameters.
You have to contact them in order to know what you have to do.

Cheers
Manuel

@m_adam Thanks

hello,

if you can give us feedback that would be awesome.

Cheers
Manuel

Hi Root Star, thanks for reaching out us.

With regard to the IDE version, we highly suggest sticking the compatibility table reported in our documentation. Visual Studio 2019 is not supported by R20 and it's likely not to be officially supported also on R21.

With regard to .hxx files, these are generated by our source processor when the building process is initiated and it's highly discouraged to change or get rid of them during the building process. The issues you're facing are highly related to the fact that the solution/project file(s) built by the projecttool (when kernel_app_64bit.exe g_updateProject=<your path to Cinema SDK> is executed) are not 100% compatible with VS2019 resulting in building tool-chain flaws.

Best, Riccardo

hello,

I've got some feedback,

You can't rely on the fact that all resource name contain Redshift. (most but not all).
As Some parts are generated dynamically this could break your tools.

May I ask you what are you trying to implement ?

Cheers
Manuel

@m_magalhaes 👏 👍

Hi CMPX, thanks for reaching out is.

With regard to your topic I recommend to have a look at how the Lattice Plane example on Github works.
This is a simplified example showing how to deliver the mechanism of the Lattice Deformer on a plane and, at the same time, it put the bases to extend it with an arbitrary mesh.
Definitively your mesh modifier should implement the ObjectData::ModifyObject() method to displace the mesh of the object to be deformed based on the displacement that you've set on the controlling mesh.
If your controlling mesh(es) are then Cinema 4D generators, then you have to run through BaseObject::GetCache() or BaseObject::GetDeformCache() in order to retrieve the points of the controlling object, and based on their relative position in the space deliver the modification on the target object.

Best, Riccardo

hello,

this thread will be considered as Solved tomorrow is you have nothing to add.

Cheers
Manuel

hello,

this thread will be considered as Solved tomorrow is you have nothing to add.

Cheers
Manuel

to be honest - i don't know where my fault was. Unhappily i didn't commit the not working version. In my plugin i
already used a virtual doc for some other calculations. thank you!

vd.ExecutePasses(c4d.threading.GeGetCurrentThread(), True, True, True, c4d.BUILDFLAGS_NONE) md = c4d.modules.mograph.GeGetMoData(matrix) for m in md.GetArray(c4d.MODATA_MATRIX): rdPoints.append(m.off)

works like a sharm.