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.

hello, thanks a lot for posting your solution here. Cheers Manuel.

That should work. Thanks for the clarification and pointer to the example!

Hi @mike, I just wanted to confirm what @chuanzhen said. For more information see the C4DAtom Manual about the dirty stuff. Cheers, Maxime.

hello, if you have nothing to add, this thread will be considered as 'solved' and will be closed tomorrow Cheers Manuel

hello, It's not related to Iterator. This simple example also complain about the default constructor. #include <iostream> class MYINT { public: MYINT(int inInt) { _myint = inInt; }; private: int _myint; }; int main() { MYINT myint; system("pause"); return 0; } It should say 'hey i don't have any constructor with no parameters". But if you give him something to initialize with it understand. MYINT myint = MYINT(10); MYINT myOtherInt = 10; MYINT myThirdInt(10); all this will end with _myint = 10; Cheers Manuel

@r_gigante @Cairyn Thanks for the thorough explanation. I underestimated the task. I initially thought it was just an easy click since the function is already available as a generator. I was looking for the same behavior in Maya. Where the subdivision deformer or modifier is not a separate object. So I can select objects easily. Anyhow, will settle for what is available in C4D currently. Thank you. Will close this for now.

Hi Manuel, Right! Found the culprit... symbolcache file... Couldn't understand how it was working for you and not for me. After deleting symbolcache worked straight away and it seems that also works without having doc.SetActiveTag(outro_cal_tag) Thank you very much for your awesome help with this! Andre

@m_magalhaes said in Matrix/HPB to XYZ and vice versa: convert the matrix to XYZ xyz = c4d.utils.MatrixToHPB(m, order=c4d.ROTATIONORDER_XYZGLOBAL) # convert from radian to deg for i in xrange(3): xyz[i] = c4d.utils.RadToDeg(xyz[i]) print xyz Works perfectly. Thanks!

@lasselauch I guess I need to revisit the script in the link above when I need to bake user data. Anyway, your script will do at the moment. It's readable enough for my newbie eyes It works as I expected! Thanks for the handy script. @m_adam Thanks for the confirmation!

@s_bach Oh, i miss a important part, thank you!

hi @bentraje , Just to confirm @mp5gosu answer. We can also point you to BaseDocument manual where you have some information about ExecutePasses Cheers Manuel

@r_gigante Thanks for the headsup about FindOrCreateEntry. Since Put does use that method internally, I didn't even consider about trying to use it, as I simply assumed it would have the same issue. Guess I was wrong about not trying it. Problem solved.

Thanks, Mike for providing them, as said before be aware that if you encounter slowdown for the autocompletion and in typing in your IDE, it may come from here Cheers, Maxime.