Hi @mikegold10 thanks for reaching out us.

With regard to your request, you've to distinguish two cases:

• during a rendering process the public VolumeData member of the ChannelData (not of the BaseShader as shown in your code) is valid, you can retrieve the linked BaseTag and, from that, you can access you userdata attached to the TextureTag to find the color of interest
• outside a rendering process, you can use the ShaderData::Draw() to find the BaseTag and, from that, you can access you userdata attached to the TextureTag to find the color of interest.

Best, R

@zipit: I'm a bit confused of your remarks here as well
In my answer I see no reference to BaseObject::GetCache() here and looking at the documentation of both methods reported in the initial boolean expression, to answer first @mfersaoui's question, it results to be True if the cache is dirty or any object's parameter has become dirty.

Cheers, R

Hi @mfersaoui thanks for writing us.

The following line of code is supposed returning True only if parameters of the object changed?

That's partially true: the expression can be True also if the object's cache is dirty

But why it also returning True when my object selected and I Move / Scale / Zoom / rotate the perspective view.

That's weird and to answer here you've to show how you're using it with the rest of your ObjectData::GetVirtualObjects() method.

Best, R

Hi Daniel, after some investigation, it has been found that, as from your special case, having a completely empty dialog (ASYNC_POPUPEDIT) means there's nothing to layout. Therefore, the empty dialog content is centered in the window which means Local2Screen does account for that offset.
That's legacy behavior of the layouter and probably has been like that since the last century.
If the dialog presents items to display the Local2Screen and Local2Global behave correctly as from the tests we ran here.

Best, R

Hi @rsodre I'm sorry but I don't have any update on the bug resolution being it, as already stated, low-prio nor I can share bug-tracking information on a public forum.

Best, R

Hi @nicholas_yue , thanks for reaching out us.

With regard to your question please be aware that C4DAtom::SetParameter() has to be called with DESCFLAGS_SET_USERINTERACTION flag to set ID_CA_XREF_FILE.

Best, Riccardo

Hi @blastframe the NBIT_CKEY_ACTIVE is set when the animation path key is selected in the viewport (and not in the Timeline)

Cheers, R

Hi @blastframe, thanks for reaching out us.

I confirm that there's no handy way - considering how flexible the timeline is - to immediately identify which Timeline is currently active. However, given the consensus about the lack of this feature, I'll file an idea request to our development team.

Best, R

Hi @blastframe thanks for writing us.

Yes, as stated in your second post having unique ids for the different dialog is the safer way to prevent unexpected behavior like the one reported initially. Tested successfully (both main (async) dialog and modal dialog were correctly sized and placed on mac and windows) I also confirm there's no need to specify the subid.

Best, R

Hi @liushu thanks for reaching out us and sorry for the late answer.

As pointed out by @Cairyn exporting a c4d scene from Cinema 4D to FBX format is indeed straightforward (see abc exporter example) on the contrary, Cineware SDK (which in any case doesn't come in a Python flavor) was not designed with this in mind and it's actually not possible without re-creating completely the whole FBX exporter.

Best, R