Hello. The problem was that I didn't add the definitions. iferr_scope; signal = maxon::ConditionVariableRef::Create() iferr_return; Thank you for time and sorry for that :(

Hi @a_block Thank you for your answer.

Hi d_schmidt and thanks for reaching us. With regard to your request, what you actually need to do is to "sample" a BaseShader used somewhere in the material referred by the TextureTag. The topic is indeed not too complex but requires some reading in order to get comfortable and proficient with the means provided in the API before dipping toes in sampling shaders. I recommend: TextureTag Manual and Materials and Shaders Overview. I also point you to this thread where sampling the color at meshes vertexes is shown using a Python script. Maybe it will simply help you to glue together the information got by reading the reference above. Best, Riccardo.

Hello, Thanks for the responses. I thought that this might be the case and just wanted to clarify it before moving forward. John Thomas

Right, that's kinda what I thought. I guess showing "<< MULTIPLE VALUES >>" for all four values will have to do (it's not that big of a deal, it just kinda looks ugly on the UI). Anyways, thanks for your help! -CMPX

Thank you @m_adam It works fine

Hi WickedP, sorry for no bringing good news, but the architecture of the CommandData doesn't allow to "piggyback" off the "Frame All" command nor I've evidences of messages being sent around to have the "Frame All" to take place. The only, but maybe non-trivial, way to go is to write your own function based on the currently active rendering-camera in your "in-memory" document. Cheers, Riccardo

Good news. And... more good news. The best news are that, after creating a Debug version and running Cinema 4D R20 from XCode, all of a sudden, the plugin started working!!! I then created a simple build (not a Debug one) and it is still working fine :-) The other good news is that I now know how to create a Debug version :-)

Hi Daniel, Thanks a lot, you are indeed right, SimpleMaterial.cpp has been fixed. Cheers, Maxime.

Hi @m_adam, No problem, I hope you had great holidays and thank you for confirming the problem. Regards, Alamgir

Hi Frank, actually I think, all the examples on GLProgramFactory have been there for quite I while. I just checked and they were already available in Cinema 4D R13, maybe even earlier (there are actually quite a few, see GitHub). Unfortunately that is all we have on this topic, chances are pretty bad, we can shed any additional light on this topic. I turned this thread into a question. Cheers, Andreas

Hi Thomas, There is MSG_DOCUMENTINFO. And this message is available in python. def Message(id, data): if id == c4d.MSG_DOCUMENTINFO: if not data: return True if data["type"] = c4d.MSG_DOCUMENTINFO_TYPE_LOAD: print "newDoc" Unfortunately, there is no way to get this message called in C4D, since Python object which supports and receive a Message function are all scene dependants (like Tag, ObjectData). In C++ we do have the SceneHook NodeData plugin which allows this kind of stuff since it's a global NodeData, not attached to a special document. So your idea is probably the best way to go if you stick to python. Cheers, Maxime.

Thanks so much this is exactly what I was looking for.

Thanks @r_gigante that's what I thought.

@s_bach, thank you, I'll start to do some hard reading!

Hello and welcome, what exactly do you mean with "export keyframe data"? Do you want to write data into a file? The best way to develop such code would be in a Python script that you can edit and execute in the Script Manager. A XPresso Python node is meant to contain code that is executed as part of XPresso to define the behavior of the XPresso network. A XPresso Python node should not be used to modify the scene or to perform I/O operations. A CTrack object stores the DescID of the associated parameter. You can access that DescID with GetDescriptionID(). Alternatively you can use BaseList2D.FindCTrack() to search for the CTrack associated with a certain parameter DescID. You find an example on GitHub. You find general information on how to use CTrack and DescID also in the C++ documentation: CTrack Manual DescID Manual best wishes, Sebastian

Hello, Indeed this example is wrong. We will fix that as soon as possible. Thanks for noticing us. best wishes, Sebastian

@s_bach Wow! I didn't see that coming. Thanks for the clear-cut explanation. Now I know in which direction I have to move. Thanks again !

Thanks Riccardo, I think we reached the bottom of this issue. I just finished implementing a workaround, getting the tag associated with the shader, it's polygon, points and uvw tag, then paint each face with the average vertex value in a bitmap using GeClipMat. Working really good! Best, Roger