Topics created by Deyan

Hey @Deyan,

Thank you for reaching out to us. The answer for public users is, no, you cannot do that, and even with a bit deeper access this will be tricky.

Cheers,
Ferdinand

Thanks a lot for the clarification! It would be nice to include more usecase examples of GetAccessedObjects(..) implementation in the SDK examples in the future. I will try your suggestion once 2024.4 becomes available.

@deyan said in Changing description of material nodes dynamically:

is there an alternative for earlier SDK versions?

In our example, you have the files nodessystem_observer.h/cpp this shows how to create a ticket system. This system is based on observable that you can use, those observables are accessible in the GraphModelInterface or the NodeSystemManagerInterface.

ObservableTransactionStarted ObservableTransactionCommitted ObservableTransactionRolledBack

You have another example in our manual

The problem with observable is that you need to be sure that your function is registered or unregistered the right way/time. You need a proper system to handle those "tickets".
For now, you only have this "basic system".

Cheers,
Manuel

Hi @m_magalhaes , thanks very much for the provided information.

We are not modifying the database manually from an editor, but rather generate it on our own. That's why I was searching for an explicit documentation, because the process of adding nodes from the Resource Editor in C4D just to check an attribute may be tedious. Thanks we will consider doing that for version changes. Thanks again - I will take a look into this interface and ask again if I have questions for its proper usage.

Cheers,
Deyan

Hi,

I've asked the devs, the example react the same so it's not on your side 🙂

Cheers,
Manuel

Hi,

This question has been answered by email. You can use the DescriptionProcessors to build/rebuild the wires inside the Usernode.

Cheers,
Manuel

Hi,

you can create those preset with a commandData sure.

When you add the graph to your node material it will call the function you defined in maxon::nodes::NODESPACE::CREATEMATERIALGRAPHFUNC See Proving Default Graph Setup for more information. So be sure to remove the nodes added by this function if they are not needed.

You must create a NodeMaterial, insert it in the document, add the graph for the right nodespace and retrieve the graph itself (by first retrieving the nimbusref). We got an example on this page: Reading and Modifying Node
This page also contains an introduction to Transaction. maxon::GraphModelInterface::BeginTransaction must be used if you want to modify the graph. You can than Commit your changes, which will ensure the graph is in a correct state. You can have a look a nodespace_impl.cpp, you will find the function CreateMaterialGraphDefaultSetup. remarque: this function doesn't need transactions to modify the graph.
In this handbook, we are using transaction to modify some port's value inside a graph. With both examples, you will understand how to add nodes, connect them, and sets values.

Cheers,
Manuel.

Thanks for the investigation. At least now we are aware the problem is not on our side.

Cheers,
Deyan

Hi @ferdinand,

Thanks for looking into this. It is not so crucial to hide the handles - I will try the custom GUI approach as you suggest.

Hi, @m_adam, thanks for the effort. I suspected it will not be possible without a custom GUI/data implementation - I guess I will go with this approach.

Cheers,
Deyan

Thanks for the effort Maxime (and rendering department). I suspected that it won't be possible, but still asked because I thought I might have missed something.

Cheers,
Deyan