Attribute Error in py-ocio_node_2025.pyp

[steinhouserj]

Hello, @mxn-ferdinand
First of all: THANK YOU FOR THE CODE EXAMPLES! :)

I am trying to get the py-ocio_node_2025.pyp example plugin running to learn the most recent best practices for Python plugins.
I downloaded the example and moved it into the plugins folder.
when I create an instance of th Py-OCIO Node 2025 object, I get these errors:

AttributeError: module 'c4d' has no attribute 'DRAW_TEXTUREFLAGS_USE_PROFILE_COLOR'
Traceback (most recent call last):
  File "C:\Users\stein\AppData\Roaming\Maxon\Maxon Cinema 4D 2025_789E552B\plugins\py-ocio_node_2025\py-ocio_node_2025.pyp", line 224, in Draw
    c4d.DRAW_ALPHA_NORMAL, c4d.DRAW_TEXTUREFLAGS_USE_PROFILE_COLOR)
                           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'c4d' has no attribute 'DRAW_TEXTUREFLAGS_USE_PROFILE_COLOR'
Traceback (most recent call last):
  File "C:\Users\stein\AppData\Roaming\Maxon\Maxon Cinema 4D 2025_789E552B\plugins\py-ocio_node_2025\py-ocio_node_2025.pyp", line 291, in Draw
    drawTextureWithLabel(0, c4d.DRAW_TEXTUREFLAGS_USE_PROFILE_COLOR)
                            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

They both claim that the c4d module doesn't have a DRAW_TEXTUREFLAGS_USE_PROFILE_COLOR attribute.
I find this confusing as it is listed here.

Any help would be greatly appreciated.
Thank you!

[mxn-ferdinand]

Hello @steinhouserj,

Thank you for reaching out to us and pointing out the issue. Something in the RC version of 2025.1.0 seems to have messed up the symbol export for DRAW_TEXTUREFLAGS::USE_PROFILE_COLOR (symbols are automatically pulled from our C++ API). We will have to check what went wrong there.

In the meantime, I have just manually exposed the symbol in said code example to make it functional again.

Cheers,
Ferdinand

[steinhouserj]

Hello @mxn-ferdinand,
Thank you very much for the quick reply and for the updated code!
I just checked and it works now 🙌

I am however still getting some weird behavior (it was the same before the code update):
Whenever there is a Py-OCIO Node 2025 object in a scene, the editor camera behaves like if I switch the Camera Mode in the Preferences to Center. When I remove the Py-OCIO Node 2025 object again, the camera behavior switches back to normal (Cursor, in my case).
I am appending a quick screen recording that shows the issue.

To reproduce the behavior I use these steps:

1. Open Cinema 4D
2. Make sure Preferences -> Navigation -> Camera Mode is set to Cursor
3. Add a Cube object to have geometry in the scene to test the orbit pivot working as intended in Cursor mode
4. Verify that the camera orbits around the cursor on the surface of the previously placed geometry
5. Add a Py-OCIO Node 2025 object
6. Verify that the camera behavior switched to Center mode
7. Delete the Py-OCIO Node 2025 object
8. Verify that the camera behaves like in step 4 again

I am using this C4D build:
2025.1.1 (Build 2025_1_1_4f2adbd43ba2_1581908240) Win

Do you have any idea what could cause this? I tested it many times in several new files, and it is always linked to having a Py-OCIO Node 2025 object in the scene.

Also, would you prefer me to open a new issue for this instead?
Thank you very much, I really appreciate your help!
Cheers,
Julius

https://github.com/user-attachments/assets/88f4ffb7-ddbe-44c3-af98-d1f2b9da6902

[mxn-ferdinand]

Hello @steinhouserj,

Thanks for the detailed bug report. I do not know out of my head what is causing this, I will try to have a look before the next release. Currently the C++ SDK is demanding my attention, so it might take a few weeks.

Regarding where to post - We are generally not very Github centric when it comes to issue tracking. We prefer it when users ask questions and report bugs on developers.maxon.net. But we will also answer questions here on Github when that is how people find us :)

Cheers,
Ferdinand

[steinhouserj]

Hello @mxn-ferdinand,
Thank you! I wish you the best for your work with the C++ SDK.

For the future I will make sure to check out the Forum on developers.maxon.net, thank you for the tip :)

Thank you again for being so responsive,
Best
Julius