No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

No activity for more than a week. As per the tracker policy we assume the issue is gone and can be closed.

I don't know if it is related. The issue you linked does not have enough information to determine that yet.

@Jacques Lucke (JacquesLucke) is this also related then T73956 ?

I can confirm that this file looks different when comparing the viewport and a render. This is true for Cycles and Eevee.

Re-opening as the fix was reverted.

The shader probably reached the limit on the number of textures. When this happens the terminal warns that the texture limit in the material has been reached.

This is a driver-specific problem. The shader probably reached the limit on the number of textures.
When this happens the terminal warns that the texture limit in the material has been reached.
To launching Blender from the Command Line (terminal) in MacOS see https://docs.blender.org/manual/en/dev/advanced/command_line/launch/macos.html

I have the same problem. It occurs in Eevee and in Cycles.

This report does not contain all the requested information, which is required for us to investigate the issue.

Hi! Thanks for the report, but Maniphest is not the best place for user feedback and feature requests: https://wiki.blender.org/wiki/Communication/Contact#User_Feedback_and_Requests

Pile of Garbage.
Windows and Linux with Intel graphics works perfectly.
Linux have constantly evolving opensource Intel driver.

I understand now, you didn't hit F11, you just made a screenshot..

Right, but when you F12 you don't see the cube. When you viewport render (shading) you see the cube because x-ray doesn't work. See the problem?

I see same thing

Okay, try this:

In T73765#871192, @Christopher_Anderssarian wrote:

What do you see for rendered viewport? Your images look to be F12 renders... the issue is rendered viewport shading.

I've got this result, but I've had to render twice...

What did you get on your first render?

Empty image.
I have to hit render (F12) twice, when I open file. After that rendering works consistently (produces some image)

What do you see for rendered viewport? Your images look to be F12 renders... the issue is rendered viewport shading.

I've got this result, but I've had to render twice...

That ticket does offer a workaround. By switching to GLSL, I can avoid most of the slowdowns. But it's still slower than expected.

I had posted this bug before: https://developer.blender.org/T53290 . It seemed to be resolved. ??