Works like a charm! It's much more flexible than I hoped;) Thanks a lot!

Hi Manuel, what you say rings a bell. I was sure it was because the vector hadn't allocated anything yet. Global possibly wasn't the best way admittedly, it just started like that for convenience. But it ended up being a bit complex, there's a lot of things accessing it, so I didn't want to change it (for now). @m_magalhaes said in Setting up global plugin structs: create a pointer and in pluginstart and pluginend take care of assign memory and free it hadn't thought of that. Seems to work - I'll go with that! Thanks WP.

Thanks for the reply, Wicked. interessting, but not what i hoped for ... kepp on chrunching

@zipit Thanks, I thought so... but you never know whether some functionality has a hidden internal purpose. Deprecating it will probably be the best solution.

That are great news, but sadly I am not a Phyton User

well sorry for the misleading. I was thinking it should work because the object is inserted with doc->InsertObject Cheers, Manuel

hi, i was saying not to use the same ID (in case of conflict) But it seems that there's no conflict neither with the symbol name or the symbol ID. A bit strange. Cheers, Manuel

Hi @delizade, Thanks @a_block for helping out! @delizade you can find the description for the priority options in the Python Tag section of the user manual. Cheers, Ferdinand

It sure does answer the question. Thanks, Riccardo!

Hi, without further feedback, we will consider this thread as solved by Monday and flag it accordingly. Cheers, Ferdinand

@ECHekman said in Compiling material nodegraph to shaders: I take it this also means its not possible to manually convert node ourselves? Right.

Hi @nicholas_yue, @Cairyn said everything (thanks for that). I would additionally recommend to read the Wikipedia article on graph traversal I have posted in your other thread, as it might clear up a few things for you. Cheers, Ferdinand

@m_magalhaes Now i know how to solve my problem! Thank you for your reply. Cheers！

Thank you @m_magalhaes !

Hi @kbar I'm able to reproduce the issue and I've opened a new bug report about it. The only workaround is to return a new VolumeObject each time. Cheers, Maxime.

thank you for your help.

Hi, without further feedback, we will consider this thread as solved by tomorrow and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by tomorrow and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by tomorrow and flag it accordingly. Cheers, Ferdinand

Hi, without further feedback, we will consider this thread as solved by tomorrow and flag it accordingly. Cheers, Ferdinand