@zipit Thanks for sharing the code. Now I know that initializing the InExcludeData is not InExcludeData.__init__ and the correct way was c4d.InExcludeData(), which I really did not think of when initializing specialized data containers.

I had a problem (again) with InExcludeData. this time with initializing the thing

Also, it seems like there is no way to merge two different InExcludeData fields to make a single InExcludeData list with no object duplicates on it.

Can any of you can explain to me how can I really do this using Python?

It basically was unclear for me as of now...

Is it possible for objects to be excluded from the environment's effect? For example, if the Fog option is enabled, the fog won't affect several objects that are meant to be not affected.

I have 2 planes with custom sun and moon textures which is really annoying right now because it always gets affected by the fog, and also I don't want to cover the sky with fog either, so I need to exclude them from the fog effect of the Environment object...

I hope there was a solution for this problem...

@zipit said in Python NODES - Shouldn't really they can change the scene?:

This statement is a bit nit-picky, but this is not really a relative path, but a url with a unusual scheme (the Maxon preset scheme that is). You can get the preset folders with c4d.storage.GeGetC4DPath() and the respective path symbols and then check with these and os.path.exists.

Thanks for mentioning that, and also telling the correct usage. I've beem havong a bad rime using os.path.relpath() and os.path.abspath() with os.path.exists()

Edit: One thing though, this code kinda has it's own holes, because I encountered a problem once more. I think what os.path.exists() looks up is the OS Absolute Path, which in this case, not very helpful because of two points:

1: The preset:// followed by file name do not follow the OS path of the file, like preset://thispreset.lib4d was the path, but preset://browser/thispreset.lib4d is the one which it was looking for.

2. The preset name on C4D do not follow the actual filename, for example, I have ThisRig by Someone.lib4d for OS path, and c4d reads it on the program as ThisRig v# - someone and have the path preset://ThisRig v# - someone.lib4d insted of the one being looked up by os.path.exists

Results on a test run using your code:
preset://browser/default.lib4d prints out the full OS path

preset://testrig.lib4d prints False

preset://broswer/testrig.lib4d prints out the full OS path if file name was testrig.lib4d

preset://broswer/testrig.lib4d prints False if file name was testrig0.lib4d

So far, I want to detect if this path exists on Cinema4D preset list, even if it doesn't exist in any of the directories being used by Cinema4D itself, as long as it's listed in the Preset list. This was due to the nature of some users just drags and drops a .lib4d file from some folder.

However, I think using a combination of detecting if a Bitmap is valid by looking at the file resolution if it matches, since it also brings the correct and always updated preset:// path (Update Textures are still a need since this isn't automatic when either Preset Folder name was changed, or it was moved to a new preset. I just thought of other ways to do that other than the Bitmap way.

I got these results, later on, I encountered the said crash:

v1 (Python Node Direct) = Secured Code, Draw Delay, No Crash
v2 (Python Node Code Transfer to Python Tag) = Secured Code, Function Delay, Draw Delay, No Crash
v3 (Python Generator) = Exposed Code, No Delay, No Crash
v3.1 (Python Node Code Transfer to Python Generator) = Secured Code, Crashes before Draw

@PluginStudent said in Python NODES - Shouldn't really they can change the scene?:

@SolarPH said in Python NODES - Shouldn't really they can change the scene?:

without any need of any plugin

If you want to have interaction with a scene without plugins you could do this:

• Add a Python Scripting Tag to your scene
• Add user-data buttons and other UI to that tag
• implement the message() function of that tag
• in that message() function, you can react to interaction with the tag's user-data UI
• you can write code that is executed from the main thread to edit the scene safely
• and leave the poor Python Node and all that thread stuff alone...

I checked with the c4d.threading.GeIsMainThread() on Python Scripting Tag and Python Generator. Seems both runs on Main Thread. I can use them, but...

Using those ways have no way to lock the code using a password, which I always do with my code to protect them against unwanted changes.

Is there any way to seal the code until it executes all?

Also, is there a way to look if a relative directory exists like "preset://mylib.lib4d/" without the other stuff inside it? That's what I need right now to do verification on the files before my python node passes the code to python generator or python scripting tag before they execute anything, just to still secure the code.

Edit: LoadFile() and ShowInFinder() doesn't work as I expected. I hope there was a specific one that works from R14 to the latest one (just for the sake of people who still use 32-bit)

EDIT(2):

After testing Python Scripting Tag with the same code but transfered using the Python Node protected inside XGroup, it has a delay until you deselect the owner, then it executes the code, but it doesn't run on the main thread as printed by c4d.threading.GeIsMainThread()

Test in a Python Generator also not want to run on Main Thread during merge...

also I can't get what message() was used

Also, Anyone know how to extract Thread Name? Or if possible, a list of Thread ID with their thread name would be useful.

I have put a piece of code on my node and this was what it prints out:

Also, I wonder if procesisng the threads can have a delay using a timer thing...

@m_adam @zipit @PluginStudent
Can you check the file I have on this folder (google drive)
https://drive.google.com/open?id=1IZ76o55libdd8d_DUtljETEt7v6FU6MY
The time of the rig files being available are only limited, since this rig is sold for purchase for animators.

Upon observation, there was no delays about the objects being imported having any delay before it shows up on my Viewport, and I also noticed that in both versions (R14 and R19), obj.Remove() adds an Undo event, and I can retrieve back the Rig Importer without deleting the imported character.

On R19 observation though, it seems like c4d.EventAdd() doesn't force all updates to show up on viewport, as if it cannot update the viewport from execution source being a Tag. Since the object is a one-time use, and cannot be keyframed, it doesn't pose too much problem on the scene.

Other than that, nothing much. Just looking up for your recommendations about making a behavior like this python node, and how to make it really on the Main Thread without any need of any plugin (because I actually need this to be compatible with all versions from R14 to R21+ without updating any plugins).

@zipit said in Python NODES - Shouldn't really they can change the scene?:

@SolarPH said in Python NODES - Shouldn't really they can change the scene?:

Is there any way for the execution to be placed from a python node to anywhere it's safer to run into?

Hi,

I have admittedly not red the whole thread here, but one approach to modifying the scene graph from a non-main-thread context could be registering a plugin id and using that id as a message id.

From your threaded context (i.e. your Xpresso Python node) you can send the id as a core message. In a separately implemented MessageData plugin you then listen for that message and upon reception set a flag in the instance of your MessageData plugin that you want to do something.

When you are sure, that you are back in the main thread in your ```MessageData`` plugin (you might have to use a timer message for that), you can execute whatever the message told you to execute.

Cheers,
zipit

Is there any way to not make it dependent on a plugin? My actual main goal is to modify the scene (not in the level of me calling any GUI around c4d). It seems to be successful and I was just about to post the scene with the specific importer and the specific preset which my importer was made for. You can look at it later. For now, it was being tested on R19 from R14