Color Management render view only has 'standard' #82081

New Issue

Daegon Kim · 2020-10-26T06:28:35+01:00

Daegon Kim commented

2020-10-26 06:28:35 +01:00

System Information
Platform: Windows
GPU: 'GeForce GTX 960/PCIe/SSE2'version: '4.5.0 NVIDIA 432.00'

Version: 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: 0330d1af29c0, type: Release

Short description of error
When placing Blender in a directory with Katakana (Japanese characters) as name, OCIO fails to find the configuration file. Blender thus only provides the "Standard" view transform in the color management options.

The path for the Blender directory is C:\Users\nanam\OneDrive\デスクトップ\blender-2.90.0-windows64.

system-info.txt

Exact steps for others to reproduce the error

Change the Windows locale to Japanese in the "Language for non-Unicode programs" settings.
Place Blender in a directory with Katakana in the name.

Start Blender.

Instead of changing the Window's locale language, placing the portable version of Blender on a non-C drive as Step 1. will also show the issue.

**System Information** Platform: Windows GPU: 'GeForce GTX 960/PCIe/SSE2'version: '4.5.0 NVIDIA 432.00' **Version:** 2.90.0, branch: master, commit date: 2020-08-31 11:26, hash: `0330d1af29c0`, type: Release **Short description of error** When placing Blender in a directory with Katakana (Japanese characters) as name, OCIO fails to find the configuration file. Blender thus only provides the "Standard" view transform in the color management options. The path for the Blender directory is ` C:\Users\nanam\OneDrive\デスクトップ\blender-2.90.0-windows64`. [system-info.txt](https://archive.blender.org/developer/F9117872/system-info.txt) **Exact steps for others to reproduce the error** - Change the Windows locale to Japanese in the "Language for non-Unicode programs" settings. - Place Blender in a directory with Katakana in the name. # Start Blender. Instead of changing the Window's locale language, placing the portable version of Blender on a non-C drive as Step 1. will also show the issue.

Daegon Kim commented

2020-10-26 06:28:35 +01:00

Added subscriber: @dk123

blender-admin commented

2020-10-26 06:28:35 +01:00

#101376 was marked as duplicate of this issue

Daegon Kim commented

2020-10-26 18:33:41 +01:00

Hi, it looks as if this only occurs if I only download the portable versions.
If I download the non-portable version, then suddenly all the portable versions I have also work.

Hi, it looks as if this only occurs if I only download the portable versions. If I download the non-portable version, then suddenly all the portable versions I have also work.

Evan Wilson commented

2020-10-26 19:26:46 +01:00

Added subscriber: @EAW

Evan Wilson commented

2020-10-26 19:26:46 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Evan Wilson closed this issue

2020-10-26 19:26:46 +01:00

Evan Wilson self-assigned this 2020-10-26 19:26:46 +01:00

Evan Wilson commented

2020-10-26 19:26:46 +01:00

Hi, @dk123, I have modified your report for readability.

Things that stick out for me:
OpenColorIO: 0, 0, 0
That should be OpenColorIO: 1, 1, 1

If I had to guess, I would say that the path Blender was using to find OCIO was incorrect. By installing the non-portable version, this path was updated to point to the correct location.

As this issue has been fixed for you, I will be closing this report. If the issue reoccurs, let us know!

Hi, @dk123, I have modified your report for readability. Things that stick out for me: `OpenColorIO: 0, 0, 0` That should be `OpenColorIO: 1, 1, 1` If I had to guess, I would say that the path Blender was using to find OCIO was incorrect. By installing the non-portable version, this path was updated to point to the correct location. As this issue has been fixed for you, I will be closing this report. If the issue reoccurs, let us know!

Daegon Kim commented

2020-10-26 19:31:48 +01:00

@EAW

I would say that the path Blender was using to find OCIO was incorrect. By installing the non-portable version, this path was updated to point to the correct location.

This absolutely does not sound like a fix. I would recommend keeping this open to actually resolve the issue.

@EAW > I would say that the path Blender was using to find OCIO was incorrect. By installing the non-portable version, this path was updated to point to the correct location. This absolutely does not sound like a fix. I would recommend keeping this open to actually resolve the issue.

Robert Guetzkow commented

2020-10-26 19:44:28 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-10-26 19:44:28 +01:00

@dk123 This happens when Blender doesn't find the directory with the color management settings for OCIO .\2.90\datafiles\colormanagement. You should've seen the following the error message in the terminal when Blender starts.

Color management: using fallback mode for management
Color management: Error could not find role data role.
Read prefs: C:\Users\maxmustermann\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend
Color management: scene view "Filmic" not found, setting default "Standard".

When this happens you will only have Standard as option in the View Transforms and OpenColorIO is reported with version 0, 0, 0.

@dk123 This happens when Blender doesn't find the directory with the color management settings for OCIO `.\2.90\datafiles\colormanagement`. You should've seen the following the error message in the terminal when Blender starts. ``` Color management: using fallback mode for management Color management: Error could not find role data role. Read prefs: C:\Users\maxmustermann\AppData\Roaming\Blender Foundation\Blender\2.90\config\userpref.blend Color management: scene view "Filmic" not found, setting default "Standard". ``` When this happens you will only have *Standard* as option in the *View Transforms* and OpenColorIO is reported with version `0, 0, 0`.

Daegon Kim commented

2020-10-26 19:49:00 +01:00

Hence, I believe it was correct to close this report.

I'd have to disagree. I notice that the portable version also has .\2.90\datafiles\colormanagement. The fact that the portable version couldn't find this I'd say would be an error.

I've just tried uninstalling the non-portable version of blender and I see the same situation reoccurring. I'd have to say this is a definite bug.

> Hence, I believe it was correct to close this report. I'd have to disagree. I notice that the portable version also has `.\2.90\datafiles\colormanagement`. The fact that the portable version couldn't find this I'd say would be an error. I've just tried uninstalling the non-portable version of blender and I see the same situation reoccurring. I'd have to say this is a definite bug.

Robert Guetzkow commented

2020-10-26 19:57:49 +01:00

So the version you're testing that fails to load the config has the colormanagement directory and also contains the following files?

config.ocio
./filmic
- filmic_desat65cube.spi3d
- filmic_false_color.spi3d
- filmic_to_0.99_1-0075.spi1d
- filmic_to_0-35_1-30.spi1d
- filmic_to_0-48_1-09.spi1d
- filmic_to_0-60_1-04.spi1d
- filmic_to_0-70_1-03.spi1d
- filmic_to_0-85_1-011.spi1d
- filmic_to_1.20_1-00.spi1d
./luts
- aces_to_xyz.spimtx
- dci_xyz.spi1d
- lg10.spi1d
- rec709.spi1d
- rec709_to_aces.spimtx
- srgb.spi1d
- srgb_inv.spi1d
- srgb_to_xyz.spimtx
- vd16.spi1d

Have you set an environment variable for the OCIO config or do you use another software that may have? It currently sounds like a configuration issue of your system and not like a bug in Blender.

So the version you're testing that fails to load the config has the `colormanagement` directory and also contains the following files? - `config.ocio` - `./filmic` - `filmic_desat65cube.spi3d` - `filmic_false_color.spi3d` - `filmic_to_0.99_1-0075.spi1d` - `filmic_to_0-35_1-30.spi1d` - `filmic_to_0-48_1-09.spi1d` - `filmic_to_0-60_1-04.spi1d` - `filmic_to_0-70_1-03.spi1d` - `filmic_to_0-85_1-011.spi1d` - `filmic_to_1.20_1-00.spi1d` - `./luts` - `aces_to_xyz.spimtx` - `dci_xyz.spi1d` - `lg10.spi1d` - `rec709.spi1d` - `rec709_to_aces.spimtx` - `srgb.spi1d` - `srgb_inv.spi1d` - `srgb_to_xyz.spimtx` - `vd16.spi1d` Have you set an [environment variable for the OCIO ](https://opencolorio.readthedocs.io/en/latest/guides/using_ocio/using_ocio.html) config or do you use another software that may have? It currently sounds like a configuration issue of your system and not like a bug in Blender.

Daegon Kim commented

2020-10-26 20:00:50 +01:00

So the version you're testing that fails to load the config has the colormanagement directory and also contains the following files

Correct. This is also a clean install of windows with just this portable version of blender, hence I find it difficult to say that this is a configuration issue on my side.

Has anyone checked if this is reproduceable? I feel as if people may be stating that it's a problem on my side without checking.

> So the version you're testing that fails to load the config has the colormanagement directory and also contains the following files Correct. This is also a clean install of windows with just this portable version of blender, hence I find it difficult to say that this is a configuration issue on my side. Has anyone checked if this is reproduceable? I feel as if people may be stating that it's a problem on my side without checking.

Robert Guetzkow commented

2020-10-26 20:07:11 +01:00

Yes, I've tested this with blender-2.90.0-windows64.zip (can be downloaded here ), 2.92 and current master. If you can still reproduce this issue on your system, please open Blender's installation and double click on the blender_debug_log.cmd. This will start Blender in debug mode and create log files. Once you've verified that the view transform options are missing, you can close Blender. The Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop.

Additionally I'd suggest you check your environment variables. Press the Windows Icon in the task bar and search for "Env". Select the "Edit environment variable" entry and a window should open. Press the "Environment Variables" button. Check if there is anything related to OpenColorIO / OCIO set as environment variables.

Yes, I've tested this with `blender-2.90.0-windows64.zip` (can be downloaded [here ](https://download.blender.org/release/Blender2.90/)), 2.92 and current master. If you can still reproduce this issue on your system, please open Blender's installation and double click on the `blender_debug_log.cmd`. This will start Blender in debug mode and create log files. Once you've verified that the view transform options are missing, you can close Blender. The Windows Explorer should open and show you up to two files, a debug log and the system information. Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. ![2019_12_04_upload_icon_developer_blender_org.png](https://archive.blender.org/developer/F8190038/2019_12_04_upload_icon_developer_blender_org.png) Additionally I'd suggest you check your environment variables. Press the Windows Icon in the task bar and search for "Env". Select the "Edit environment variable" entry and a window should open. Press the "Environment Variables" button. Check if there is anything related to [OpenColorIO / OCIO ](https://opencolorio.readthedocs.io/en/latest/guides/using_ocio/using_ocio.html) set as environment variables.

Robert Guetzkow commented

2020-10-26 20:32:30 +01:00

Changed status from 'Archived' to: 'Needs User Info'

Robert Guetzkow reopened this issue

2020-10-26 20:32:30 +01:00

Robert Guetzkow commented

2020-10-26 20:32:30 +01:00

I just noticed that you've placed Blender inside the OneDrive sync folder. Just to rule out OneDrive interfering in an unexpected way, could you please also try to put the portable version in another directory?

Evan Wilson was unassigned by Robert Guetzkow

2020-10-27 00:22:36 +01:00

Daegon Kim commented

2020-10-28 06:12:12 +01:00

blender_system_info.txt

blender_debug_output (1).txt

[blender_system_info.txt](https://archive.blender.org/developer/F9115862/blender_system_info.txt) [blender_debug_output (1).txt](https://archive.blender.org/developer/F9115863/blender_debug_output__1_.txt)

Daegon Kim commented

2020-10-28 06:25:06 +01:00

I've tried multiple configurations, and it seems that if the path of blender contains japanese characters, then color management seems to fail to pick up.

Robert Guetzkow commented

2020-10-28 12:41:46 +01:00

@dk123 This does appear to be the case, based on the log file. However, I can't reproduce this on my system by putting Blender into a directory with Katakana in the name. It looks like OpenColorIO treats the path with an incorrect encoding on your system or Blender passes it incorrectly to OpenColorIO. Blender itself appears to handle it properly.

Log file opened as UTF-8:

OpenColorIO Error: Error could not read 'C:\Users\nanam\OneDrive\ǹ¯~1\BLENDE~1.0-W\2.90\DATAFI~1\COLORM~1\CONFIG~1.OCI' OCIO profile.

argv[0] = C:\Users\nanam\OneDrive\デスクトップ\blender-2.90.0-windows64\\blender

A similar issue was found before in #47869, but there was no reply to the bug report to OCIO since then. Since Blender contains the following code in colormanagement_init (colormanagement.c), it seems that a workaround is still necessary and this is what might be failing on your system.

#ifdef WIN32
      {
        /* quite a hack to support loading configuration from path with non-acii symbols */

        char short_name[256];
        BLI_get_short_name(short_name, configfile);
        config = OCIO_configCreateFromFile(short_name);
      }
#else

@dk123 This does appear to be the case, based on the log file. However, I can't reproduce this on my system by putting Blender into a directory with Katakana in the name. It looks like OpenColorIO treats the path with an incorrect encoding on your system or Blender passes it incorrectly to OpenColorIO. Blender itself appears to handle it properly. Log file opened as UTF-8: ``` OpenColorIO Error: Error could not read 'C:\Users\nanam\OneDrive\ǹ¯~1\BLENDE~1.0-W\2.90\DATAFI~1\COLORM~1\CONFIG~1.OCI' OCIO profile. ``` ``` argv[0] = C:\Users\nanam\OneDrive\デスクトップ\blender-2.90.0-windows64\\blender ``` A similar issue was found before in #47869, but there was no reply to the [bug report ](https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/406) to OCIO since then. Since Blender contains the following code in `colormanagement_init` (colormanagement.c), it seems that a workaround is still necessary and this is what might be failing on your system. ``` #ifdef WIN32 { /* quite a hack to support loading configuration from path with non-acii symbols */ char short_name[256]; BLI_get_short_name(short_name, configfile); config = OCIO_configCreateFromFile(short_name); } #else ```

Robert Guetzkow commented

2020-10-28 15:04:05 +01:00

Changed status from 'Needs User Info' to: 'Needs Developer To Reproduce'

Richard Antalik commented

2020-10-29 14:04:48 +01:00

Added subscriber: @iss

Richard Antalik commented

2020-10-29 14:04:48 +01:00

Also can't reproduce this.

Robert Guetzkow commented

2020-10-29 14:11:23 +01:00

@dk123 Do you have any special language/locale or code page configurations on your system?

Daegon Kim commented

2020-10-30 16:18:57 +01:00

This is a clean install of Win 10 (japanese), I don't recognise anything else.

Daegon Kim commented

2020-10-30 16:20:39 +01:00

https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/406

It might be worth adding some more comments on to this thread here if it's the fundamental problem.

https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/406 It might be worth adding some more comments on to this thread here if it's the fundamental problem.

Robert Guetzkow commented

2020-11-02 12:19:19 +01:00

Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'

Robert Guetzkow commented

2020-11-02 12:19:19 +01:00

I can reproduce the issue when changing the locale on Windows to Japanese in the "Language for non-Unicode programs" settings.

Evan Wilson commented

2021-01-18 22:31:05 +01:00

@Sergey reported this upstream to OCIO in 2016. It would be nice if it could get fixed for OCIO’s 2.0 release. I will look around at other FOSS’s workarounds to see if I can get OCIO a PR in the next few days. https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/406

Evan Wilson commented

2021-01-18 22:38:39 +01:00

Added subscriber: @Sergey

Evan Wilson commented

2021-03-03 06:02:40 +01:00

Triaging Note: I can reproduce this without having to change my Window's Language settings by placing the portable version of Blender on a non- C drive.
Binary Path: 'D:\\previous Blender Versions\\Others\\2.93_builds\\blender-2.93.0-デスクトップ-windows64\\blender.exe'
Reported Error: OpenColorIO Error: Error could not read 'D:\previous Blender Versions\Others\2.93_builds\blender-2.93.0-Ç¹¯ÈÃ×-windows64\2.93\datafiles\colormanagement\config.ocio' OCIO profile.

Triaging Note: I can reproduce this without having to change my Window's Language settings by placing the portable version of Blender on a non- `C` drive. Binary Path: `'D:\\previous Blender Versions\\Others\\2.93_builds\\blender-2.93.0-デスクトップ-windows64\\blender.exe'` Reported Error: `OpenColorIO Error: Error could not read 'D:\previous Blender Versions\Others\2.93_builds\blender-2.93.0-Ç¹¯ÈÃ×-windows64\2.93\datafiles\colormanagement\config.ocio' OCIO profile.`

Vyacheslav Kobozev commented

2021-03-11 00:35:40 +01:00

Added subscriber: @Vyach

Vyacheslav Kobozev commented

2021-03-11 00:35:40 +01:00

windows 8.1, Russian system language,
paths:
D:\Progs\Graphics\3d\Blender-2.93.0
C:\Users\Ad\AppData\Roaming\Blender Foundation\Blender\2.93
Start with factory settings have bug.
Clean start without settings folder (in appdata/roaming) don`t have a bug

I reset to English for Blender and system language (locale). Then made clean restart (creating new settings folder or uploading previous settings). It helped.
After setting Ru and back to En bug appears and left with English system.

Deleting colormanagement folder in settings (bf/blender/2.93) will help as workaround

windows 8.1, Russian system language, paths: D:\Progs\Graphics\3d\Blender-2.93.0 C:\Users\Ad\AppData\Roaming\Blender Foundation\Blender\2.93 Start with factory settings have bug. Clean start without settings folder (in appdata/roaming) don`t have a bug I reset to English for Blender and system language (locale). Then made clean restart (creating new settings folder or uploading previous settings). It helped. After setting Ru and back to En bug appears and left with English system. Deleting colormanagement folder in settings (bf/blender/2.93) will help as workaround

Ankit Meel commented

2021-06-11 12:56:47 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-06-11 12:56:47 +02:00

It was reported in #86176 (Render properties. Color management lost options. Regression) that the bug is not present in 2.93. So could anyone retry ?

Jukka Korhonen commented

2021-06-17 14:57:52 +02:00

Added subscriber: @loadus

Jukka Korhonen commented

2021-06-17 14:57:52 +02:00

In #82081#1175125, @ankitm wrote:
It was reported in #86176 (Render properties. Color management lost options. Regression) that the bug is not present in 2.93. So could anyone retry ?

I'm having this error, which just popped up out of nowhere and I came in searching for a solution.
The path to the Ocio config is malformed >>

OpenColorIO Error: Error: Loading the OCIO profile 'C:\Users\Jukka\AppData\Roaming\BLENDE~1\Blender\2.93\DATAFI~1\COLORM~1\CONFIG~1.OCI' failed. Cannot add 'XYZ' color space, there is already a role with this name.
Color management: using fallback mode for management
Color management: Error could not find role data role.
Read prefs: C:\Users\Jukka\AppData\Roaming\Blender Foundation\Blender\2.93\config\userpref.blend
Color management: scene view "Filmic" not found, setting default "Standard".
Color management: scene look "Very High Contrast" not found, setting default "None".
Color management: sequencer colorspace "Filmic Log" not found, will use default instead.

The file itself and it's contents seem to be fine, just that the lib can't find it via that path.

[EDIT]
Correction, manually editing the ocio profile and removing the XYZ entries, the color management configuration loads up. Still, having this error pop up out of nowhere was a real headscratcher. I'll see if I can hunt down the cause, my guess would be the endless settings imports from previous versions.

> In #82081#1175125, @ankitm wrote: > It was reported in #86176 (Render properties. Color management lost options. Regression) that the bug is not present in 2.93. So could anyone retry ? I'm having this error, which just popped up out of nowhere and I came in searching for a solution. The path to the Ocio config is malformed >> ``` OpenColorIO Error: Error: Loading the OCIO profile 'C:\Users\Jukka\AppData\Roaming\BLENDE~1\Blender\2.93\DATAFI~1\COLORM~1\CONFIG~1.OCI' failed. Cannot add 'XYZ' color space, there is already a role with this name. Color management: using fallback mode for management Color management: Error could not find role data role. Read prefs: C:\Users\Jukka\AppData\Roaming\Blender Foundation\Blender\2.93\config\userpref.blend Color management: scene view "Filmic" not found, setting default "Standard". Color management: scene look "Very High Contrast" not found, setting default "None". Color management: sequencer colorspace "Filmic Log" not found, will use default instead. ``` The file itself and it's contents seem to be fine, just that the lib can't find it via that path. [EDIT] Correction, manually editing the ocio profile and removing the XYZ entries, the color management configuration loads up. Still, having this error pop up out of nowhere was a real headscratcher. I'll see if I can hunt down the cause, my guess would be the endless settings imports from previous versions.

Yuro commented

2022-06-14 10:41:29 +02:00

Added subscriber: @Yuro

Yuro commented

2022-06-14 10:41:29 +02:00

Does this mean that this long-standing bug is hopeful to be fixed?

#95206 :
OpenColorIO 2.0.0 --> 2.1.1

OpenColorIO v2.1.1 release :
PR #1527, Fixes Unicode paths on Windows (#1363)

Does this mean that this long-standing bug is hopeful to be fixed? #95206 : OpenColorIO 2.0.0 --> 2.1.1 [OpenColorIO v2.1.1 release ](https://github.com/AcademySoftwareFoundation/OpenColorIO/releases/tag/v2.1.1): PR #1527, Fixes Unicode paths on Windows (#1363)

Omar Emara commented

2022-09-26 23:33:15 +02:00

Added subscriber: @PacoChan

Evan Wilson commented

2022-09-26 23:55:04 +02:00

Added subscriber: @LazyDodo

Evan Wilson commented

2022-09-26 23:55:04 +02:00

I can confirm that this is still an issue in 3.3 and 3.4.

@Yuro unfortunately the issue is not yet fixed (as @PacoChan has shown) due to an error in the CMAKE syntax that causes the Unicode fix to not be built.

Fixing this requires the OCIO libraries to be rebuilt with the corrected option added to CMAKE.

See: CMake: Fix issue that led to Windows Unicode support still defaulting to off #1594

@LazyDodo it looks like the following code needs to be added to CMAKE.

if (WIN32)
    option(OCIO_USE_WINDOWS_UNICODE "Compile with Windows Unicode support" ON)
endif()

I can confirm that this is still an issue in 3.3 and 3.4. @Yuro unfortunately the issue is not yet fixed (as @PacoChan has shown) due to an error in the CMAKE syntax that causes the Unicode fix to not be built. Fixing this requires the OCIO libraries to be rebuilt with the corrected option added to CMAKE. See: [ CMake: Fix issue that led to Windows Unicode support still defaulting to off #1594 ](https://github.com/AcademySoftwareFoundation/OpenColorIO/pull/1594) @LazyDodo it looks like the following code needs to be added to CMAKE. ``` if (WIN32) option(OCIO_USE_WINDOWS_UNICODE "Compile with Windows Unicode support" ON) endif() ```

Jesse Yurkovich commented

2022-12-17 02:52:34 +01:00

Added subscriber: @deadpin

Jesse Yurkovich commented

2022-12-17 02:52:34 +01:00

Unfortunately the move to OCIO 2.2 last week did not fix this - it should have the CMAKE change mentioned above. This might be an issue on Blender's side as there's some interesting behavior here.

Default situation where Blender might be using a unicode path (fails):

cd D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release

.\blender.exe
OpenColorIO Error: Error could not read 'D:\blender-3.5.0-╟╣»╚├╫.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio' OCIO profile.

Explicitly setting the OCIO env var to effectively the same location (succeeds):

cd D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release
$env:OCIO="D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio"

.\blender.exe
Color management: Using D:\blender-3.5.0-πâçπé╣πé»πâêπââπâù.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio as a configuration file

I'll try to take a closer look this weekend if no one else spots the real issue before I can take a look.

Unfortunately the move to OCIO 2.2 last week did not fix this - it should have the CMAKE change mentioned above. This might be an issue on Blender's side as there's some interesting behavior here. Default situation where Blender might be using a unicode path (fails): ``` cd D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release .\blender.exe OpenColorIO Error: Error could not read 'D:\blender-3.5.0-╟╣»╚├╫.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio' OCIO profile. ``` Explicitly setting the OCIO env var to effectively the same location (succeeds): ``` cd D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release $env:OCIO="D:\blender-3.5.0-デスクトップ.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio" .\blender.exe Color management: Using D:\blender-3.5.0-πâçπé╣πé»πâêπââπâù.6546113f1ed2-windows.amd64-release\3.5\datafiles\colormanagement\config.ocio as a configuration file ``` I'll try to take a closer look this weekend if no one else spots the real issue before I can take a look.

Ray molenkamp commented

2022-12-17 03:26:28 +01:00

i can confirm ocio was build with the right options, whatever is wrong, it's not the cmake option. from the CMakeCache.txt used to build ocio :

//Compile with Windows Unicode support
OCIO_USE_WINDOWS_UNICODE:BOOL=ON

i can confirm ocio was build with the right options, whatever is wrong, it's not the cmake option. from the CMakeCache.txt used to build ocio : ``` //Compile with Windows Unicode support OCIO_USE_WINDOWS_UNICODE:BOOL=ON ```

Jesse Yurkovich commented

2022-12-17 10:30:43 +01:00

Alright, the issue is because we're still using a workaround in Blender (which doesn't seem to work and/or is no longer necessary). Removing this workaround fixes things: https://developer.blender.org/diffusion/B/browse/master/source/blender/imbuf/intern/colormanagement.c$674

Now here's the interesting bit, both 3.4 AND 3.3 can work if we remove that workaround even though they still use OCIO 2.1.1. This is because our app manifest declares that magical UTF-8 setting which seems to fix things up. I verified using 3.4 but not with 3.3 though it should be the same.

3.5 works once the workaround is removed and regardless of the app manifest setting which proves the fix for OCIO 2.2 is correct as well.

Alright, the issue is because we're still using a workaround in Blender (which doesn't seem to work and/or is no longer necessary). Removing this workaround fixes things: https://developer.blender.org/diffusion/B/browse/master/source/blender/imbuf/intern/colormanagement.c$674 Now here's the interesting bit, both 3.4 AND 3.3 can work if we remove that workaround even though they still use OCIO 2.1.1. This is because our app manifest declares that magical UTF-8 setting which seems to fix things up. I verified using 3.4 but not with 3.3 though it should be the same. 3.5 works once the workaround is removed and regardless of the app manifest setting which proves the fix for OCIO 2.2 is correct as well.

blender-admin commented

2023-01-06 05:44:24 +01:00

This issue was referenced by b6c74b4c6f

This issue was referenced by b6c74b4c6f6b2b1ec28ec9db091a2a0f4fe66b94

Jesse Yurkovich commented

2023-01-06 05:46:28 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Jesse Yurkovich closed this issue

2023-01-06 05:46:28 +01:00

Jesse Yurkovich self-assigned this 2023-01-06 05:46:28 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Color Management render view only has 'standard' #82081

Start Blender.