Hi, Maxime, I'm trying to be able to browse through every point, the tangents of those points, and the segments they belong to. It seems like a LineObject wouldn't help me get the tangents or the spline point locations so I think I would need the actual SplineObject.

I want to output a SplineObject, taking in the input splines points, tangents, and segments to be able modify it and return something different.

I hope that clears it up,
Dan

I hope this helps!

Upon adding Optimize Object to the scene and immediately closing Cinema causes a series of memory leaks.

Reproduce:

1. Open Cinema 4D.
2. Add an Optimize Object.
3. Close Cinema 4D.

Result:

1. There are resulting memory leaks.

Versions:
NOK 2024.0.2

Thank you so much! I couldn't ask for a more thorough response.

Dan

Hello, I noticed there seemed to be a new 'name' feature with the Condition object.

Is it possible to make use of it in a plugin?

'Condition' is just the object's Name, but I can't figure out how 'distance' is set.

Dan

Thanks for the info!

Dan

Hi @i_mazlov

Sorry about the lack of clarity in my post, I managed to trim the case down to something pretty narrow:

The hierarchy:

The code:

  BaseObject* firstChild = op->GetDown();
    if(firstChild != nullptr)
    {
        if(firstChild->GetType() == Ovolumebuilder)
        {
            VolumeBuilder* volumeBuilder = static_cast<VolumeBuilder*>(firstChild);
            if(volumeBuilder!=nullptr)
            {
                Int32 volumeBuilderInputCount = volumeBuilder->GetInputObjectCount(false);
                BaseObject* volumeChildInput = volumeBuilder->GetDown();
                
                if(volumeBuilderInputCount > 0 && volumeChildInput != nullptr)
                {
                    BaseObject* volumeInputObject = volumeBuilder->GetInputObject(0);
                    if(volumeChildInput == volumeInputObject)
                    {
                        ApplicationOutput("The two inputs are the same.");
                    }
                    else
                    {
                        ApplicationOutput("The two inputs are not the same.");
                    }
                    
                }
            }
        }
    }

In most cases it seems like the two objects equal each other, e.g. if the cube is moved. If an Undo is performed after moving the cube, so the Undo returns the cube's position back, then they do not equal each other.

This is the same circumstance where I'm not able to retrieve the cache from the GetInputObject() object. Would this be expected behavior in this circumstance?

Dan

Hello, I have a circumstance pretty far in my code where I'm using a VolumeBuilder.

If I have a cube as a child of a VolumeBuilder when I use GetInputObject to retrieve that cube, I'm not able to get the cache from that cube sometimes with GetCache().

In the same circumstance, if I use GetDown() from the VolumeBuilder, to retrieve that cube, I am able to get the cache from that cube same cube with GetCache().

Do GetInputObject() and GetDown() behave differently in this circumstance?

Thanks for the help!
Dan

Hi Ferdinand,

So to be clear, the only thing that can be done with ItemTreeData is adding new objects to it?

Thanks,
Dan

Hi Ilia,

At this point this seems a bit over my head, but it seems to be what I need, thanks!

Dan

Hello, I've just started to dive into Redshift materials and I was wondering if there is a way to sample them like a Standard material?

I've had some success with Standard materials with using BaseShader::Sample() and BaseChannel::Sample() to get the values of specific shaders at given positions. I can't find a similar way to sample a Redshift material.

Dan

Hi Ilia,

I'm on Mac 13.3 and C4D 2024.0.0 at the moment.

Dan

Hello, @i_mazlov

You're exactly right about what I'm trying to achieve. Thanks again for the answers.

With your code, placed in RoundedTube, seems to work in that the VertrexColorTag is preserved between updates and I can see the tag changes as it's updated.

I am encountering an issue where if I increasing and decreasing Rotation Segments I'll occasionally get a crash. Sometimes the crash is pointing to this line: "CheckState(pKernel->Commit());" but other times I'm not getting a particular crash location. Do you encounter this issue?

Then, when I implement your fix into my code, everything seems to be working well, until I shrink down the number of points I have. When increasing the number of points it seems like the VertexColorTag is increasing up correctly but when I scale decrease the number of points it will crash occasionally. This isn't tied to the above crash, since I'm not using Modeling in my code. Would any tweaks need to be done to the code to handle shrinking point counts?

Dan