Page MenuHome

Workbench: "Not enough texture slots!" Message being spammed and lags the entire computer
Confirmed, NormalPublicBUG

Description

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1060 3GB/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 446.14

Blender Version
Broken: version: 2.83.0, branch: master, commit date: 2020-06-03 14:38, hash: rB211b6c29f771
Worked: (newest version of Blender that worked as expected)

Short description of error
I had a file of a game scene made in 2.82 and it worked perfectly fine. But when I open the very same file in 2.83


it spammed this message when the big mesh was being rendered in viewport. The whole program lags to the point of unusability. I have to the .blend file with 2.82, disable texture display and re-open with 2.83

Exact steps for others to reproduce the error

  • Create a material with more texture slots than your GPU can handle.
  • See console

Event Timeline

This message is common.
It indicates that you have exceeded the texture limits supported by your GPU in the shader/material.
But it is strange that this message does not appear with the same file in 2.82.

Anyway, it seems like a bug spamming it so often.
This can actually cause lag.

To make it clear, can you confirm that this message does not spamming in blender 2.82?

To make it clear, can you confirm that this message does not spamming in blender 2.82?

yes, I opened the same exact file in 2.82 and it didn't lag at all

But does the message appear at least once?

strangely, not. It didn't appear at all.

Germano Cavalcante (mano-wii) changed the task status from Needs Triage to Confirmed.Thu, Jun 11, 4:33 PM
Germano Cavalcante (mano-wii) updated the task description. (Show Details)
Germano Cavalcante (mano-wii) changed the subtype of this task from "Report" to "Bug".

I'm getting this same spam but, to my knowledge, I'm not exceeding texture slot usage on any materials. The warning message about this is of very little help as it doesn't tell you what materials supposedly have too many textures, just that something does.

The slow-down renders solid / texture view virtually unusable. And, strangely, it scrambles the textures too: certain objects will show completely different textures to what they're meant to. Deleting materials or hiding / deleting objects even seems to change which textures are being shown, which sounds suspiciously like a memory leak. This only happens in solid / texture view: switch to material preview or rendered and things display correctly.

I'm getting this same spam but, to my knowledge, I'm not exceeding texture slot usage on any materials. The warning message about this is of very little help as it doesn't tell you what materials supposedly have too many textures, just that something does.

The slow-down renders solid / texture view virtually unusable. And, strangely, it scrambles the textures too: certain objects will show completely different textures to what they're meant to. Deleting materials or hiding / deleting objects even seems to change which textures are being shown, which sounds suspiciously like a memory leak. This only happens in solid / texture view: switch to material preview or rendered and things display correctly.

Hey yeah, this doesn't lag in Preview/Render views at all! And everything else you said is the same for me too

Could you run blender_debug_gpu.cmd using both 2.82a and 2.83, and then upload the files that are created when you close Blender please?

Could you run blender_debug_gpu.cmd using both 2.82a and 2.83, and then upload the files that are created when you close Blender please?

Done. Hope this helps narrow things down. In my test for this, I opened the exact same file in both versions, a house model I use for lighting tests. The view defaulted to Solid mode, I rotated the camera a bit, then quit.

Note the debug file for 2.83 is considerably larger than its 2.82a counterpart due to the sheer number of error messages the issue generates.

I'm getting this same spam but, to my knowledge, I'm not exceeding texture slot usage on any materials. The warning message about this is of very little help as it doesn't tell you what materials supposedly have too many textures, just that something does.

The slow-down renders solid / texture view virtually unusable. And, strangely, it scrambles the textures too: certain objects will show completely different textures to what they're meant to. Deleting materials or hiding / deleting objects even seems to change which textures are being shown, which sounds suspiciously like a memory leak. This only happens in solid / texture view: switch to material preview or rendered and things display correctly.

I am having the same issues with 2.83 in a file the works as expected in 2.82. I can also add that when, for example, I hide all objects except one, this one is textured correctly in solid mode. As more objects are becoming visible there comes a moment when things brake. In my case about 60 objects.

Clément Foucault (fclem) changed the task status from Confirmed to Needs Information from User.Sun, Jun 28, 4:47 PM

We need a simple file to reproduce the issue.

I agree the message is of little help. I'll improve it.

That said I don't understand what the report is aimed at. At the slowness? (in this case does it happen without a terminal opened?) or the fact the same shaders worked in 2.82 but not 2.83?


Whether console is enabled or not, it is almost impossible to use blender with texture color type in solid viewport shading mode.

We need a simple file to reproduce the issue.

I agree the message is of little help. I'll improve it.

That said I don't understand what the report is aimed at. At the slowness? (in this case does it happen without a terminal opened?) or the fact the same shaders worked in 2.82 but not 2.83?

I'll see if I can put together something to reproduce this issue.

As for the purpose of the report itself, I didn't open it personally but my specific issues are:

  1. It didn't happen in 2.82 and it does in 2.83
  2. I don't think the error is correct: I'm not, to my knowledge, exceeding the texture slots for any materials
  3. It's causing the Solid Mode of the viewport to be completely unusable in Texture view: not only is it very slow compared to any other mode, it's displaying incorrect textures on nearly every surface and they change depending on arbitrary factors, like which objects are visible

If I had to pick one specific issue it's definitely Solid View becoming extremely unstable / laggy.


Whether console is enabled or not, it is almost impossible to use blender with texture color type in solid viewport shading mode.

Oh, @Dmitrii (WeaselOnAStick) beat me to the punch with a file. Nice. If more are needed, let me know and I'll dig something up.

I am uploading the file where I encountered this message - behaviour. I stripped it down (deleted hundreds of objects to reduce size) to absolutely essentials for the behavior to take place. That is, more than 60 objects, each one with a unique material and texture. As you switch between solid and material preview shading you can notice some corrupt textures at the top left corner (top view).
With few objects like the file uploaded, lag is not a problem. The same file that has originally 1600 objects, with almost 1500 unique materials and textures is unusable.
Everything works as expected in material preview mode.
The problem is that solid shading, with texture as color is unusable, because a) of speed (in big scenes) b) of wrong - random texture placement.

Sorry for not reproducing from a clean file, I hope I can do when I have more time.

Clément Foucault (fclem) changed the task status from Needs Information from User to Confirmed.Sun, Jun 28, 7:21 PM
Clément Foucault (fclem) moved this task from Backlog to Bugs on the EEVEE & Viewport board.
Clément Foucault (fclem) edited projects, added BF Blender (2.83); removed BF Blender.

Ok I can reproduce. This is likely caused by the workbench refactor.

The issue has been fixed in 2.90 due to other refactors but they cannot be backported to 2.83 LTS.

@Jeroen Bakker (jbakker) I think we have to work on a fix in the LTS branch.

Clément Foucault (fclem) renamed this task from "Not enough texture slots!" Message being spammed and lags the entire computer to Workbench: "Not enough texture slots!" Message being spammed and lags the entire computer.Sun, Jun 28, 7:22 PM

@Jeroen Bakker (jbakker) I have this quick hack that solves the issue. P1491

Feel free to test/modify/commit.