Hello @vik-lc ,

without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @mikeudin ,

without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @datamilch ,

without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @Joel,

without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @Aleksey,

without further questions or postings, we will consider this topic as solved by Friday, the 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @Cairyn ,

without further questions or postings, we will consider this topic as solved by Friday 11th of august 2023 and flag it accordingly.

Thank you for your understanding,
Maxon SDK Group

Hello @filipst,

Without further questions or updates we will consider this topic as solved by Friday the 11th, and flag it accordingly.

Cheers,
Maxon SDK Group

@i_mazlov Thank you very much for your help!

@ferdinand
Many thanks for this detailed example, I'll try it out

P.S.
Oh my gosh, it's working perfectly. I decided to go the easiest way, just to check the dirtyness of the linked object.

linkDirty: bool = link.IsDirty(c4d.DIRTYFLAGS_DATA)

Many many thanks

Thomas

@i_mazlov Thanks👍

Hello @konradsawicki,

Thank you for reaching out to us. Cappucino Realtime is a tool to record mouse inputs; your plugin or things like the Vibrate tag do not count as mouse inputs and are therefore not recorded.

When you want to bake the output of whatever your plugin is, you will have to implement that yourself.

Cheers,
Ferdinand

@ferdinand The code works very well 👍

Thanks for the response.

I figured that something like this would be the case, will have to look into the options you mentioned.

John Terenece

Thank you Ilia,
Let me digest your extremely kind advice and example, learn from it, and come back tom you.
Kind regards,
James.

@ferdinand Thanks

@ferdinand Thanks a lot. Very useful information. You are the best!

@i_mazlov got it! thx for answer!

@ferdinand
Thank You for Reply

Hey @fwilleke80,

you are right, it does indicate an error, hence my example from above. When I searched in our internal code base for similar code, I found a lot of

return NodeData::GetDDescription(node, description, flags);

calls. While there are certainly node types which customize their description handling, this seems to be more a precaution for the case when we decide that we want to implement something in NodeData::GetDDescription in the future. Or something has been there in the past and we optimized it away. In any case, one should not take my comment about calling the base implementation being pointless too seriously. It is best to leave the call in, although it currently has no practical effect and probably will never have.

Cheers,
Ferdinand

@ferdinand

Thanks for the advice.

i'm going to try Have a nice day today