• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Custom OCIO path does not correctly apply the import/export settings

New Here ,
Feb 10, 2023 Feb 10, 2023

Copy link to clipboard

Copied

I'm trying to automate the colourspace setup at work and have run into a problem. We've tested this on version 7.4.1 and 8.2.0 on Windows 10.

 

This seems to be related to this thread, though as it's a year old, perhaps the update has been released and may not be working 100% correctly.

 

This happens on any preset, but just taking ACES 1.0.3 for example, if I load the preset, then the import/export settings are all set to the correct things:

Peter272917140rum_3-1676048015755.png

 

If I switch to custom and point to the same file inside the install folder (C:\Program Files\Adobe\Adobe Substance 3D Painter\resources\ocio\aces_1.0.3\config.ocio), then everything below gets set to the same value as scene_linear value, which in this case is ACES - ACEScg.

Peter272917140rum_2-1676048004524.png

 

In the case of 8.2.0, it does work when pointing to the C drive, but copying the folder to a network drive will break it again.

 

I noticed the documentation (https://substance3d.adobe.com/documentation/spdoc/color-management-with-opencolorio-225969419.html#s...) does not match the variables in the example files (eg. substance_3d_painter_bitmap_import_8bit vs substance_3d_bitmap_import_8bit), but switching between the two didn't make any difference.

Bug Unresolved
TOPICS
Bugs & Crashes , Color Management

Views

105

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
no replies

Have something to add?

Join the conversation
Resources