ID 606827 - Custom OCIO configs fail to load correctly in Nuke Studio/Hiero if inside a OCIOConfigs/configs directory and they do not match the name of OCIO configs inside Nuke

Problem summary
Custom OCIO configs fail to load correctly in Nuke Studio/Hiero if inside a OCIOConfigs/configs directory and they do not match the name of OCIO configs inside Nuke
 
It will load in the Project Settings and Viewer, but not the bin/sequence right click menus or of the Clip/Read node properties
 
This happens with both OCIO 2.1 and 1.0 configs
 
It loads correctly in Nuke's node graph
 
Customer reported version
nuke.16
 
Customer reported platform
macOS
 
Steps to reproduce
 
1) Goto <nukeInstall>/plugins and copy the OCIOConfigs directory to a different location on the machine
 
2) Inside the /plugins/OCIOConfigs/configs directory, rename the OCIO configs, for example append _test to their names
 
3) Open Nuke Studio/Hiero and make a new project
 
4) In Project>Edit Settings>Color Management tab set the OpenColorIO Config to custom and Choose... a renamed config from the copied folder, for example:
 
\OCIOConfigs\configs\fn-nuke_studio-config-v1.0.0_aces-v1.3_ocio-v2.1_test.ocio
 
5) Import any footage and add it to s sequence
 
6) Check the different OCIO populated menus, some load, others don't:

 

 
Expected behaviour
For the correct OCIO colorspaces to be available in the correct places
 
Actual behaviour
The clip OCIO colorspace defaulted back to nuke-default
 
Workaround
Don't have folders named OCIOConfigs/configs, for example OCIOConfig/configs
 
Reproduced by support
This bug has been reproduced in:
Nuke Studio 16.0v5 - Windows 11, macOS Sonoma
Nuke Studio 14.0v8 - Windows 11 
Nuke Studio 14.0v3 - Windows 11, macOS Sonoma - regression
 
Unable to reproduce bug in:
Nuke Studio 14.0v2 - Windows 11, macOS Sonoma
 
Earliest version tested
Nuke Studio 14.0v2 - This issue doesn't appear in this version and has regressed