OpenColorIO Error when adding Material to Object in New Scene #56147

New Issue

Daniel Oakey · 2018-07-30T00:25:52+02:00

Daniel Oakey commented

2018-07-30 00:25:52 +02:00

System Information
OS: Arch Linux,
Graphics Card: GTX 1060

Blender Version
2.79b

Short description of error
This message repeats in the console repeatedly after adding a material to an object in a new scene:

  OpenColorIO Error: DisplayTransform error. Cannot find display colorspace,  ''.

Exact steps for others to reproduce the error

Open a new instance of blender
Create a new scene
(Click the "+" button at the right of the Scene selector at the top of the 3D View
Inside "Scene.001" in the 3D view, add a cube and give that cube a material.
Observe the console showing the repeated error message:

  OpenColorIO Error: DisplayTransform error. Cannot find display colorspace,  ''.

**System Information** OS: Arch Linux, Graphics Card: GTX 1060 **Blender Version** 2.79b **Short description of error** This message repeats in the console repeatedly after adding a material to an object in a new scene: ``` OpenColorIO Error: DisplayTransform error. Cannot find display colorspace, ''. ``` **Exact steps for others to reproduce the error** 1. Open a new instance of blender 2. Create a new scene 3. (Click the "+" button at the right of the Scene selector at the top of the 3D View 4. Inside "Scene.001" in the 3D view, add a cube and give that cube a material. 5. Observe the console showing the repeated error message: ``` OpenColorIO Error: DisplayTransform error. Cannot find display colorspace, ''.

Daniel Oakey commented

2018-07-30 00:25:52 +02:00

Added subscriber: @doakey3

blender-admin commented

2018-07-30 00:25:52 +02:00

#58146 was marked as duplicate of this issue

blender-admin commented

2018-07-30 00:25:52 +02:00

#57600 was marked as duplicate of this issue

Bastien Montagne commented

2018-07-30 11:54:31 +02:00

Added subscribers: @Sergey, @mont29

Sergey Sharybin was assigned by Bastien Montagne

2018-07-30 11:54:31 +02:00

Bastien Montagne commented

2018-07-30 11:54:31 +02:00

Don’t think that this is a bug, but let’s @Sergey decide here.

Sergey Sharybin commented

2018-10-29 16:26:11 +01:00

@doakey3, Can not reproduce the issue.. Do you use some sort of custom OCIO configuration? What does the color management settings of the new scene show?

Daniel Oakey commented

2018-10-30 00:45:30 +01:00

When I tested this on my windows computer, the issue did not occur. This only seems to happen on my linux machine. I guess I don't know what a custom OCIO configuration is. I'm using the XFCE desktop environment on Arch linux.

When I tested this on my windows computer, the issue did not occur. This only seems to happen on my linux machine. I guess I don't know what a custom OCIO configuration is. I'm using the XFCE desktop environment on Arch linux. ![demo.gif](https://archive.blender.org/developer/F5290297/demo.gif)

Mal Duffin commented

2018-11-02 10:08:19 +01:00

Added subscriber: @MalDuffin

Mal Duffin commented

2018-11-02 10:08:19 +01:00

Just to add to this, I see the problem in 2.8 when I take these steps...

Compile 2.8 ( in Visual Studio, or using the make command line tool ) : NOTE - the same latest build from the Blender website works OK
Load blender / default scene
Go into Eevee Rendered mode
Create new scene

Blender will now crash.

I've attached a screenshot showing the call stack when compiled and ran in debug mode, just in case that helps... ( the crash happens in release mode too in my locally built version )

If you want me to try anything at my end to try to narrow down the issue ( if you're not seeing the same thing on your own computers ), just let me know!

( Windows 10, GTX 1070 - I noticed that the original author has a 1060 )

Just to add to this, I see the problem in 2.8 when I take these steps... - Compile 2.8 ( in Visual Studio, or using the make command line tool ) : NOTE - the same latest build from the Blender website works OK - Load blender / default scene - Go into Eevee Rendered mode - Create new scene Blender will now crash. I've attached a screenshot showing the call stack when compiled and ran in debug mode, just in case that helps... ( the crash happens in release mode too in my locally built version ) ![image.png](https://archive.blender.org/developer/F5334682/image.png) If you want me to try anything at my end to try to narrow down the issue ( if you're not seeing the same thing on your own computers ), just let me know! ( Windows 10, GTX 1070 - I noticed that the original author has a 1060 )

Tom Telos commented

2018-11-06 04:52:05 +01:00

Added subscriber: @ttelos

Tom Telos commented

2018-11-06 04:52:05 +01:00

On Mac OS 10.13, recent nightly build of Blender 2.79, I'm having the same problem.

Despite the complaint, images do render, however.

On Mac OS 10.13, recent nightly build of Blender 2.79, I'm having the same problem. Despite the complaint, images do render, however.

Bastien Montagne commented

2018-11-22 12:51:45 +01:00

Can confirm the issue here with both 2.7x and 2.8 builds. Seems to be a problem between display device (set to DCI-P3 for new scenes for some reason)…

@Sergey either we stick to default startup display device in BKE_color_managed_display_settings_init(), instead of calling IMB_colormanagement_display_get_default_name(), or we change BKE_color_managed_view_settings_init() to set proper a valid value for current display_device…

Can confirm the issue here with both 2.7x and 2.8 builds. Seems to be a problem between display device (set to DCI-[P3](https://archive.blender.org/developer/P3.txt) for new scenes for some reason)… @Sergey either we stick to default startup display device in `BKE_color_managed_display_settings_init()`, instead of calling `IMB_colormanagement_display_get_default_name()`, or we change `BKE_color_managed_view_settings_init()` to set proper a valid value for current display_device…

Philipp Oeser commented

2018-11-22 13:10:56 +01:00

Added subscriber: @lichtwerk

Mal Duffin commented

2018-11-29 11:44:09 +01:00

I'm still getting this crash in the latest build.

Go into Eevee Rendered mode
Select "New scene" from the Scene dropdown in the top right

or do it in the other order...

Select "New scene" from the Scene dropdown in the top right
Go into Eevee Rendered mode

I'm still getting this crash in the latest build. 1) Go into Eevee Rendered mode 2) Select "New scene" from the Scene dropdown in the top right or do it in the other order... 1) Select "New scene" from the Scene dropdown in the top right 2) Go into Eevee Rendered mode

Philipp Oeser commented

2018-11-29 12:11:15 +01:00

Added subscriber: @AnadinX

Sergey Sharybin commented

2018-12-05 14:12:33 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue

2018-12-05 14:12:33 +01:00

Sergey Sharybin commented

2018-12-05 14:12:33 +01:00

I've done series of changes in this area, which solves this bug.

For those who are interested: b927d19696, 6122e1d6c0.

Thanks for the report, closing it now.

I've done series of changes in this area, which solves this bug. For those who are interested: b927d19696, 6122e1d6c0. Thanks for the report, closing it now.

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

OpenColorIO Error when adding Material to Object in New Scene #56147