Well @pim , that's indeed the issue. Sticking to the recommended IDE is always recommended.

Hi @pim thanks for reaching out us.

With regard to your request, well just having the "special" command-line args recognized is as easy as uncommenting this line.

It's indeed a working plugin and it should not be registered since it's not a plugin but rather a behavior defined when a C4DPL_COMMANDLINEARGS is intercepted.

Best, R

Hi @matniedoba, thanks for reaching out us.

With regard to your issue, given that it's not our primary task to debug plugins, to understand what's getting wrong I need you to provide:

• test scenes of different complexity;
• the smallest code able to reproduce the issue - rather than the whole plugin - considering that it's a matter of object dirty check.

I also second @zipit recommendations because improving code design via better function abstraction and documentation will lead to an increased clarity, reliability and, in the end, comprehension.
I'll try to find time in the course of the week to have a look at your issue given the items requested above.

Best, R

Hi @pim , thanks for reaching out us.

Although you've already set this thread as SOLVED can you, for the sake of a better knowledge-sharing, describe better what you mean by "I tried to update a R20 C++ plugin."? What steps did you actually run through? What version of VisualStudio are you using? What version of ProjectTool did you used?

Finally, please make sure you use our tagging system to enhance topic search.

Cheers, R

Hi @RenatoT thanks for reaching out us.
Can you please:

• add a tag to specify the C4D version you're using?
• can you make use of the Q&A functionality?

With regard to HandleShaderMessage, I confim that it is indeed used by shaders in NodeData::Message() when they have subchannels. The code snippet found the call documentation represents exactly what is used in the Fusion shader with regard to the Base, Mask and Blend channels.

Instead with regard to SHADERINFO_DYNAMICSUBSHADERS, assuming I've checked the version of Cinema you're working with, it is used no more.

Looking forward your further notes, give best.

Hi @dskeith thanks for reaching out us.

As pointed out by @PluginStudent, the NBIT_SOLO_LAYER behavior is explained in the Layer Manuel although it make sense to add a note to the Python API as well.

With regard to a complete example, I've partially reworked your code to make sure that by executing the script multiple times you can run across all the solo configurations that the scene can handle.

import c4d

# Main function
def main():
    layer_root = doc.GetLayerObjectRoot()
    if not layer_root: 
        return

    # Get the first layer in the scene
    layer = layer_root.GetDown()
    if not layer: 
        return

    soloSet = False

    while layer is not None:
        # Set `rawdata` to True flag so to get the original layer values without any additional global changes
        layer_data = layer.GetLayerData(doc, rawdata=True)

        # check the current layer solo state:
        if layer_data["solo"] == False:
            # if not "solo" then set to True
            layer_data["solo"] = True
            # update the layer
            layer.SetLayerData(doc, layer_data)
            # update the flag
            soloSet = True
            break
        
        # deactivate if layer solo was True
        layer_data["solo"] = False
        layer.SetLayerData(doc, layer_data)

        # go to next layer
        layer = layer.GetNext()
    
    # if one (or more) solo was set the set NBIT_SOLO_LAYER otherwise clear
    if soloSet == True:
        doc.ChangeNBit(c4d.NBIT_SOLO_LAYER, c4d.NBITCONTROL_SET)
    else:
        doc.ChangeNBit(c4d.NBIT_SOLO_LAYER, c4d.NBITCONTROL_CLEAR)

    # Add an event 
    c4d.EventAdd()

# Execute main()
if __name__=='__main__':
    main()

Cheers

Hi @C4DS, thanks for reaching out us.

There's actually nothing weird in your code rather than you're just attempting to back-port a code designed to work from R21 onward to R20.

Please have a look at our asynctest example on GitHub on how it was handled in R20.

Best, R

Thanks @kosmos3d for the contribution and making the whole community aware of it.

Best, R

Thanks a lot @zipit . I indeed agree and will update the documentation accordingly.

Best and stay safe!
R

Hi @geese780 , thanks for reaching out us.

As suggested from @PluginStudent , the Getting Started section as well as the related sections found there are indeed good starting points.
On top of this material I recommend having a look at our PluginCafé Channel on GitHub where you can find different repositories for your tastes.
Among the examples in the C++ Repository, I warmly recommend checking the MicroSDK which is a full-rounded, 100% complete example on how both C4D Classic API and Maxon API can coexist in a single plugin.

Other relevant topics - but please not limit your curiosity to such list - to investigate, fitting with your scope are:

• BaseList2D
• BaseDocument
• BaseObject

About IDE: the VS2017 Community Edition should work pretty well and doesn't need you to spend a buck!

Finally, although related to R20, you can find very detailed information on Compiling the Cinema 4D R20 C++ SDK Examples.

Feel free to come for any further support.
R