materials not updated correctly after collada import #86314

New Issue

Damien Demars · 2021-03-05T16:59:18+01:00

Damien Demars commented

2021-03-05 16:59:18 +01:00

System Information
Operating system: windows 10
Graphics card: geforce gtx 1060

Blender Version
Broken: 2.92 release

Short description of error
all materials render black in cycles after collada import

Exact steps for others to reproduce the error

I can't join a scene reproducing the problem because if a save a scene with the problem then re open it, the problem disappear.

steps to reproduce are simple :
take the default .blend scene with the cube :

exported to a collada file (selection only : just the cube)
deleted from the default scene
imported back from collada file

in the "shader editor" view, the cube's material is correctly displayed

but in the "material properties" tab the cube's material is displayed with Surface : "None" instead of expected surface : "Principled BSDF"

Cycles rendering is affected (cube render black) while EEVEE rendering display the correct material

interacting with the material in the "Shader editor" UI can bring the material back to a fully initialised state :

  just start to click on an empty link, start to draw a line then release mouse...  is enough to update the material.
  another way to repair is just to save and re open the scene.

as collada importer seems to setup material properties correctly (as seen in shader editor view)
I think it can be more a blender refresh/update bug than a addon (collada) bug. (but I'm not sure of that..)

**System Information** Operating system: windows 10 Graphics card: geforce gtx 1060 **Blender Version** Broken: 2.92 release **Short description of error** all materials render black in cycles after collada import **Exact steps for others to reproduce the error** I can't join a scene reproducing the problem because if a save a scene with the problem then re open it, the problem disappear. steps to reproduce are simple : take the default .blend scene with the cube : - exported to a collada file (selection only : just the cube) - deleted from the default scene - imported back from collada file in the "shader editor" view, the cube's material is correctly displayed but in the "material properties" tab the cube's material is displayed with Surface : "None" instead of expected surface : "Principled BSDF" Cycles rendering is affected (**cube render black**) while EEVEE rendering display the correct material interacting with the material in the "Shader editor" UI can bring the material back to a fully initialised state : ``` just start to click on an empty link, start to draw a line then release mouse... is enough to update the material. another way to repair is just to save and re open the scene. ``` as collada importer seems to setup material properties correctly (as seen in shader editor view) I think it can be more a blender refresh/update bug than a addon (collada) bug. (but I'm not sure of that..)

Damien Demars commented

2021-03-05 16:59:18 +01:00

Added subscriber: @DamienDemars

Philipp Oeser commented

2021-03-23 16:09:42 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2021-03-23 16:09:42 +01:00

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

Philipp Oeser commented

2021-03-23 16:09:42 +01:00

Can confirm.

Philipp Oeser self-assigned this 2021-03-23 16:17:22 +01:00

Philipp Oeser commented

2021-03-23 16:17:22 +01:00

Got a fix.

blender-admin commented

2021-03-23 16:26:15 +01:00

This issue was referenced by 6b18678e34

This issue was referenced by 6b18678e34bfbe2e95430fa7491ed1d3fad4ff3a

Philipp Oeser commented

2021-03-24 10:33:41 +01:00

Changed status from 'Confirmed' to: 'Resolved'

Philipp Oeser closed this issue

2021-03-24 10:33:41 +01:00

Scurest commented

2021-04-30 17:58:15 +02:00

Added subscriber: @scurest

Scurest commented

2021-04-30 17:58:15 +02:00

I think this problem still exists for links created after the ntreeUpdateTree call, eg. links to texture nodes. If you import a .dae with a texture you get the same symptoms:

Should the ntreeUpdateTree call be moved to the end, after all the set_diffuse/etc calls?

I think this problem still exists for links created after the `ntreeUpdateTree` call, eg. links to texture nodes. If you import a .dae with a texture you get the same symptoms: ![bad_000.png](https://archive.blender.org/developer/F10047348/bad_000.png) Should the `ntreeUpdateTree` call be moved to the end, after all the `set_diffuse`/etc calls?

Scurest commented

2021-05-04 13:24:21 +02:00

@lichtwerk

Philipp Oeser commented

2021-05-04 14:40:28 +02:00

Checking again.

blender-admin commented

2021-05-04 15:19:33 +02:00

This issue was referenced by a1069b6c66

This issue was referenced by a1069b6c662ffbeba0457164c3ec831678b25fd4

Philipp Oeser commented

2021-05-04 15:21:58 +02:00

Changed status from 'Resolved' to: 'Confirmed'

Philipp Oeser reopened this issue

2021-05-04 15:21:58 +02:00

Andreas Schadrin commented

2021-05-05 21:03:33 +02:00

Added subscriber: @TheGremanCharizard

Andreas Schadrin commented

2021-05-05 21:03:33 +02:00

Can Confirm too.
Same Problem here.
#88062

{F10055309, size=full}

{F10055308, size=full}

Can Confirm too. Same Problem here. #88062 {[F10055309](https://archive.blender.org/developer/F10055309/DAE_BUG.PNG), size=full} {[F10055308](https://archive.blender.org/developer/F10055308/DAE_BUG_2.png), size=full}

Philipp Oeser commented

2021-05-06 08:44:20 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Philipp Oeser closed this issue

2021-05-06 08:44:20 +02: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

materials not updated correctly after collada import #86314