Hi @Leo_Saramago thanks for reaching out to us.

With regard to execution priority, as you've already spotted, the scene nodes are evaluated after generator because classic Cinema items can indeed be used as entry point for the node graph. With regard instead to nodes graph execution priority, nodes are executed left-to-right, or better said, a node is evaluated when its input ports have received the needed data from the “preceding" nodes!

Hope it answers your question.
Riccardo

@ECHekman said in Compiling material nodegraph to shaders:

I take it this also means its not possible to manually convert node ourselves?

Right.

Thanks @ceen for reaching out to us.

I'll make aware Maxon ppl responsible for the animation area about your request and leave it, for the time being, to community on offering support.

Best, Riccardo

Hi @ECHekman, thanks for reaching out to us.

With regard to your question, at the moment with current API, is not possible to traverse a node-based material shader graph and consequently to convert to other convenient datasets.

As said already in other threads, it's under our radar and we hope to share soon updates on this regard.

Cheers, R

Hi @delizade, thanks for reaching out to us.

The PythonTag associated to an object is evaluated, by default, every time Cinema 4D evaluates the scene and this can happen even if the object has not changed at all.

Finally, without more details on the PythonTag code, its design and the ultimate goal, I can only think about of the simple solution of caching the last userdata value in the PythonTag's container and compare, before running your tag's business logic, it against the value found in the userdata.

Cheers, R

Hi @delizade, thanks for reaching out to us.

With regard to your question I've a few considerations to share:

• external libraries are supposed to be located either under %APPDATA%/MAXON/{cinemaversion}/python37/libs, if they are referred only to a specific Cinema version or in %APPDATA%/MAXON/python37/libs if they are supposed to be seen by all Cinema(s) installed on your machine (see here for further info);
• c4d.EventAdd() adds an event to the Cinema 4D events queue, and it's not responsible for the tag to not be executed "infinitely". Consider that a Python tag is executed every time the scene is evaluated so the behaviour your mention is consistent with the code posted.

Given said that and with regard to
@delizade said in How to use/import another script file in Python tag correctly?:

've solved the issue
c4d.EventAdd() was added end of my external function script. I removed it and used it in tag script. I think after that line python tag was triggered again.

I can't see, guessing your code I've reported below, how you stopped the PythonTag to be executed "infinitely".

import c4d
import test

def main():
    print ("test")
    customCode.myFunction(op)

Cheers, Riccardo

@fwilleke80 Thanks for the follow-up Frank! In all the previous cases I always notarized without specifying the timestamp. I'll again and in case update the guide.

Cheers, r

@fwilleke80 said in Plugin compiled on macOS Catalina for R23, not working on Big Sur?:

• Can you ask your customer what "usual" security questions he answered?
• Can you ask your customer before unpacking the zip archive, that maybe he has downloaded from an email or a website, to run $ xattr -d "com.apple.quarantine <zip archive to your plugin>"

Ah, thanks, I'll ask him to try that!

So, to make the plugin run on my beta testers' Macs with Bir Sur without warnings, I not only need to sign the binary, I also need to send the binary to Apple to have it notarised? Every single time I release a beta version to my testers??

Cheers,
Frank

This is actually what we do in our building pipeline. My suggestion is to automate the process which, being completely terminal based, should be far from being rocket science.

Cheers, R

Thanks @kbar it's clear to me, I just wanted to know what actually @fwilleke80 was meaning. And for those listening you can sign a plugin during or after the building process.

Cheers, R

Hi @fwilleke80, looking at our code base this statement is no more active in recent versions of Cinema.

What accompanies the code is Change to WarningOutput as Installer needs to run without objects module but, honestly, given the vague description is hard to further comment and being it R20 it doesn't allows us to invest more time on it.

Cheers, R