OpenColorIO Error when adding Material to Object in New Scene #56147
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#56147
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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:
Exact steps for others to reproduce the error
Added subscriber: @doakey3
#58146 was marked as duplicate of this issue
#57600 was marked as duplicate of this issue
Added subscribers: @Sergey, @mont29
Don’t think that this is a bug, but let’s @Sergey decide here.
@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?
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.
Added subscriber: @MalDuffin
Just to add to this, I see the problem in 2.8 when I take these steps...
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 )
Added subscriber: @ttelos
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.
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 callingIMB_colormanagement_display_get_default_name()
, or we changeBKE_color_managed_view_settings_init()
to set proper a valid value for current display_device…Added subscriber: @lichtwerk
I'm still getting this crash in the latest build.
or do it in the other order...
Added subscriber: @AnadinX
Changed status from 'Open' to: 'Resolved'
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.