AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
3 color blender12/19/2023 ![]() Read prefs: C:\Users\Jukka\AppData\Roaming\Blender Foundation\Blender\2.93\config\userpref.blendĬolor management: scene view "Filmic" not found, setting default "Standard".Ĭolor management: scene look "Very High Contrast" not found, setting default "None".Ĭolor management: sequencer colorspace "Filmic Log" not found, will use default instead. Cannot add 'XYZ' color space, there is already a role with this name.Ĭolor management: using fallback mode for managementĬolor management: Error could not find role data role. 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. I'm having this error, which just popped up out of nowhere and I came in searching for a solution. Regression) that the bug is not present in 2.93. It was reported in #86176 (Render properties. 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.Ĭonfig = OCIO_configCreateFromFile(short_name) 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.Ī similar issue was found before in #47869, but there was no reply to the () to OCIO since then. Blender itself appears to handle it properly. ![]() It looks like OpenColorIO treats the path with an incorrect encoding on your system or Blender passes it incorrectly to OpenColorIO. However, I can't reproduce this on my system by putting Blender into a directory with Katakana in the name. * quite a hack to support loading configuration from path with non-acii symbols */īLI_get_short_name(short_name, configfile) Ĭonfig = This does appear to be the case, based on the log file. 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. 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.Īrgv = C:\Users\nanam\OneDrive\デスクトップ\blender-2.90.0-windows64\\blenderĪ similar issue was found before in #47869, but there was no reply to the bug report to OCIO since then. Check if there is anything related to () set as environment This does appear to be the case, based on the log file. Press the "Environment Variables" button. Select the "Edit environment variable" entry and a window should open. Press the Windows Icon in the task bar and search for "Env". !()Īdditionally I'd suggest you check your environment variables. ![]() Add them to your bug report by clicking on the upload button as shown in the screenshot below or via drag and drop. The Windows Explorer should open and show you up to two files, a debug log and the system information. Once you've verified that the view transform options are missing, you can close Blender. This will start Blender in debug mode and create log files. If you can still reproduce this issue on your system, please open Blender's installation and double click on the `blender_debug_log.cmd`. ![]() ![]() Yes, I've tested this with `blender-2.90.0-windows64.zip` (can be downloaded ()), 2.92 and current master. ![]()
0 Comments
Read More
Leave a Reply. |