How to debug this? - Asset Browser -

Archive Python API
1

Hi,
I would like to report a bug from the latest build version of blender 3.2.0 alpha as of 06/02/2022.

blender-3.2.0-alpha+master.48fbf0baea88-windows.amd64-release.zip

We have blender integrated into our pipeline and we have a strange behaviour in the viewport when trying to place a random prop cube from the Asset Browser.

  • (1) The viewport is not updating the drawing of the prop cube in the 3d space (we have just only the mouse pointer). The importing method is “Append (reuse data)”.

    viewport
    viewport1576×1010 222 KB

    (see image number 1)

  • (2) When left clicking to finally place the prop cube into the 3d space view the console spits out the following error code regarding a cycle dependency. (see image number 2)

Captura de pantalla 2022-02-07 132129
Captura de pantalla 2022-02-07 1321291473×248 30.5 KB

We would like to try to debug this, but i dont see anything weird with the shading configuration we have in the prop. I cannot see this “Math.022” node apparently responsible for the cyclic dependency.

Captura de pantalla 2022-02-07 134400
Captura de pantalla 2022-02-07 134400459×532 29.3 KB

Furthermore, i dont know if this is something that is happening “under the hood” and if it is python accessible or it stems from the very core C++ blender api.

We would just like to report this and get some useful feedback if possible. Is this because of the unstable version we are testing?

Many thanks in advance!

Best Regards from Spain.

UPDATE: if i check the shading network for the list of nodes in the nodetree i cannot seem to find a “Math.022” node with this name.

3

Hello,
apologies in advance.
It is not a python or C++ code problem.
The shader network being used has many cyclic dependencies and it s a matter of debugging the shader.
Finally managed to inspect the internal nodes by double clicking in the shadernodegroups.

One quick and last question: is it expected to not trouble the viewport when those cyclic dependencies in shading occur? Would this be expected to be fixed in a “stable” or “LTS” release? I understand that if the shader is faulty, the viewport rendering cannot take place correctly either. Maybe a default failback shader would be a good idea?

Thanks.