OCIO broken 2026.2

Flame Flame Questions
1

Installed 2026.2

made a new project using our studio config, config works fine in every app I throw it as, and it validates the OCIO config with ociocheck.

Opened project on a different mac:

image
image1864×896 114 KB

Got this Error message.

Did not change anything, went to settings and hit reload OCIO, now it works again.

Thats not great?

Log message is same:

Config failed display view validation. Shared view ‘arri-reveal_20251104_151312’ refers to a viewing rule, ‘Viewport Inactive’, which is not defined.

CLRMGT: ERROR: Config failed display view validation. Shared view ‘arri-reveal_20251104_151312’ refers to a viewing rule, ‘Viewport Inactive’, which is not defined.

Failed loading ‘/Volumes/lucid/xxx_pipeline/ocio/rpb-ocio/config.ocio’: [Config failed display view validation. Shared view ‘arri-reveal_20251104_151312’ refers to a viewing rule, ‘Viewport Inactive’, which is not defined.]. Defaulting to RAW config.

2

OCIO is working without issue in 2026.2. Your issue is probably related to the fact that loading the OCIO config from LucidLink did not refresh the referenced transform file,as the error message stated. Flame was not able to read the content of the transform file then showed the error message.

I guess you are good to go since the second restart was successful.

3

even tho my mountpoint is called lucid, the ocio config is just a local SMB share .

I had similar issues wirh 2926.1 without custon ocios

4

Thanks for the quick update!

That probably means that the transform file was not yet mounted from the SMB mount. Is this issue show after a reboot?

At startup, Flame loads the OCIO config and the config validates all referenced transforms and reports issues in case it cannot find these files. This action might have refreshed the file from the SMB share but not fast enough to get the content of the file visible for OCIO (transform can be large file and take time to load).

5

will further observe , share was definetely mounted tho, but would it be preffered to put this on a NFS mount?

I am not getting great playback performance on macOS using NFS in resolve - SMB works much better for reading exrs in my case.

(i do use nfs for managed media / framestore media cache and project data of course)

6

Thanks for the info. SBM should not cause issue.

Please open a support call and include your OCIO config and reference file ASAP and we will have a look. Please share the ticket ID so I can follow up.

1 Like
7

Damn @finnjaeger. Loo session with @Slabrie. That issue run deep deep down.

1 Like
8

Sorry for the long exchange, I thought we were at the pub :wink:

3 Likes
9

yea i made a ticket for like 2026,1 in agust , where we had similar issues with view transforms created in flame erroring .

ill make a new one if I see this pop up again, we havent used 2026 , but are planning to give 2026.2 another shot for the next project after ironing out all the issues we had with performance and disaster recovery e.t.c , this literally happend after me setting up the first test project to check if the upgraded projectserver would do its thing or not.

CaseNo:24637191 havent heard back if the issue was reproduced and fixed ort whatever.

10

this is not a pub?

11

Virtual Pub!

Based on the support ticket data, you have got a mail at your work address on September 9th for the case 24637191 with a workaround for the problem. The email must be buried in a busy inbox pre IBC.

1 Like
12

Once again I’m doing everything wrong here. No OCIO breakage for me. Not for many months.
Is the problem anything to do with OCIO 2.5 in Autodesk Flame 2026.2.0?
I know other software packages like nuke and resolve are usually a bit behind in general.

13

No worry, we got Finn’s custom OCIO config and will have a look and let you know what we will find.

3 Likes