Im trying to get the natvis files to work, and I added the settings from the documentation.
However this does not seem to do anything. Is there something im missing?

AdditionalSolutionFiles=\
..\..\frameworks\core.framework\project\typeviewer\msvc\maxon.natvis;\
..\..\frameworks\cinema.framework\project\typeviewer\msvc\c4dapi.natvis

I have gotten it to work by manually adding the natvis to the visual studio document folder, but i would like to automate it.

Could you explain the issue with this though? Is C4D doing strange stuff with c++ classes derived from ShaderData?

I wanted to avoid having to recreate the PluginNodeInfoStruct every time an instance is created by placing it in ::Init. Would the following be fine?

virtual PluginNodeInfoStruct& PluginNodeInfo() const override 
{ 
    static PluginNodeInfoStruct sPluginNodeInfo
    {
        SOME_ID,
        SOME_UI_ID,
    };
    return sPluginNodeInfo; 
};

In the documentation i read the following:

Do not use global static classes of complex types. Elementary data types (Int32, Float, Char etc.) are allowed, see Primitive Data Types Manual (Cinema API).

Im not sure what this exactly means. But im trying to create a settings class as a static member to ShaderData nodes that contains information about the derived class that the base class needs to know.

struct InfoStruct
{
public:
    UInt32 SomeID;
    Int32 SomeUI;
};

PluginNodeBase  : public ShaderData
{
    INSTANCEOF(PluginNodeBase, ShaderData)
public:
    virtual PluginNodeInfoStruct& PluginNodeInfo() const = 0;
}

class SomeClass: public PluginNodeBase
{
    INSTANCEOF(VolumeMedium, PluginNodeBase)

public:
    // Set plugin node info
    inline static PluginNodeInfoStruct sPluginNodeInfo
    {
      SOME_ID,
      SOME_UI_ID,
    };
    virtual PluginNodeInfoStruct& PluginNodeInfo() const override { return sPluginNodeInfo; };

}

Would this be fine? or is there a reason Icould not use static in this way?

Thank you for your reply.
I take it this also means its not possible to manually convert node ourselves?

I am looking into supporting cinema4d nodegraph materials into our pathtracer plugin.
I looked through the documentation, but found very little about the material node system on the technical side.

Would it be possible to compile or translate material nodegraphs into GLSL shaders?

Im trying to dynamically track all the objects in the active BaseDocument, including the cached InstanceObjects and BaseObjects that are created by cloner objects.
I have a function that scrapes the BaseDocument contents and keeps a list of all the relevant objects as BaseLinks. This list is updated every time there is a change in the BaseDocument.

This is working very well with most scenes, and I can track all the InstanceObjects and (cached/deformed)PolygonObjects in the scene.
However, I found that in certain scenes, BaseLink::GetLink will crash on PolygonObjects taken from some cloner cache's. I suspect it has something to do with mograph cache?

I also found that pointers to these PolygonObjects that crash GetLink, will work initially, but then suddenly stop working and return 0 on GetType.

Am i doing something wrong here? Or did i find a bug? Are there better ways to do what im trying to do?

Im working on a rendering plugin, and im looking for the best way to track the lifetime of various objects in the scene.
Currently im looking at Meshes (PolygonObject), Materials and Textures.

What would be the best way to check if objects have been removed and added to a scene?
According to the documentation I should not use pointers, but baselinks. But I cannot compare baselinks with eachother.
I have also read that the various ID functions are not always unique for all objects.