OTOY Forums

does anyone know how to get rid of this? I have looked everywhere... I believe this is something I caused a very long time ago but I cannot find where to fix it - its persists through every install/update of the plugin as well as modo.

Modo->Preferences->Octane->delete the OCIO Config Filename, or delete your Modo.CFG file, or edit it and delete the user.value oc_ocioConfigFile.

Thanks

Paul

thank you!

spoke to soon - I deleted modo cfg file, uninstalled and deleted any remaining octane files (stand alone and plugin), went into the modo cfg, deleted the one line that matched, this error refuses to go away. its not hurting anything, just annoying. I am willing to delete everything - all versions of modo and octane, but I suspect there is a file somewhere that I am not finding - any ideas?

Seems that the OCIO config-file is not even loaded. The issue (whatever is causing it) prevents it from loading it (in the empty field where the file path should be, above "Browse...")?

Not an Octane-Modo user but what about replacing the "(OCIO disabled)" with "(OCIO enabled)"? I could be misleading you as I have never used Modo but there are cases where such text-editing does work.

Is it possible that you have the OCIO environment variable set on your PC?

Paul

it's possible but I am not familiar this at all so it would have been by accident - how can I check? I think this was the result of me following a tutorial on how to set up aces for C4D a long time ago, not realizing that I didn't need to do that in the more recent version of the Modo plugin.

To check for an environment variable

1. Click start and type "system environment variables" and click to open the window
2. Click environment variables
3. Look in both the USER and SYSTEM variables for anything with OCIO in the name, then select and delete them

I am not seeing anything there... should a specific file be showing in this box? am I missing a file that is somehow not being created on install?

Frankly, all that hassle might not even be worth it the ACES checkbox in the Camera Imager eventually does suffice? However, it is worth to investigate on the issue itself as it shouldn't occur.

jwfvr wrote:should a specific file be showing in this box?

Here is Standalone's OCIO preferences: