Page MenuHome

Eevee: Material not displayed
Closed, ArchivedPublic


Win 10, gtx970
Blender 2.8 4d795cee4938

Using Eevee, When I use the same Wood material on two separate objects, on one to the right the material is not displayed.
Please see the attached images and blend file.



Event Timeline

Sebastian Parborg (zeddb) triaged this task as Needs Information from User priority.

I can not reproduce this:

Please try a newer build and see if that helps.

Just tried the newest version 4dd0a90f4213 and the problem persists.
Can someone reproduce this on the same graphics card Gtx 970?

And when I duplicate the object, some of them are working and some of them are flickering the material.

Also, I updated to the latest graphics drivers.

I asked one friend to test it on his computer. and he has the same problem.
His system is: gtx 1050 ti, i3, win 10

Sebastian Parborg (zeddb) raised the priority of this task from Needs Information from User to Normal.

Can you attach (as a file) the output if you run blender with --debug-gpu. You can also see if --debug-gpu-force-workarounds helps.

Sorry, but I don't know how to do it.

You open up cmd and navigate to the directory where you have blender.exe. Then you type into the cmd: blender.exe --debug-gpu > output.txt. Load up the .blend file with the issue and then quit blender. The output should now be in output.txt.

I did it!
But with the help of my brother who is a programmer :)

Also when I put a new material, the problem still persists on that object.

If you select a group.
And try to Ungroup it.
The program shuts down.

I can confirm as well.

I get an assert opening the file in a debug build.
This has to do with some armature dependency cycles and bendy bones (but I cannot find any armature in the file).
After simplifying the file (leaving only the 2 meshes) I get no error and no shading errors (I get no shading errors even before).

Can you try doing the same on your end? Removing everything but the meshes and see if there is still shading errors.

The shading node group/ungroup crash is another issue that has to do with datablocks. Better report it separately.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.