Material mix with vertex color: "_COLOR0" is added everytime you import the model
See original GitHub issueDescribe the bug If you import the model which use vertex color, you’ll get that annoying “_COLOR0” - everytime you import it! So if you export/import it multiple times, you’ll end with something like
MyMaterialName_COLOR0_COLOR0
And don’t forget about material name limit in Blender…
MyMaterialName_COLOR0_COLOR0_<...>_COLO
And what if material name is very long initially?
Looooooooooooooooooooooooooo<...>oongName_CO
Is this a normal behavior? Why do we need that “_COLOR0” in material name?
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
Mixing materials w vertex color - Blender 2.x - YouTube
In this tutorial I show how to mix two materials in the Material Node Compositor using as factor a Vertex Color Map in ......
Read more >Blender Vertex Color height blend material tutorial - YouTube
This tutorial gives you an introduction to the shader editor in Blender, Cycles & Evee as well as how to use Quixel Bridge...
Read more >How can I import an OBJ with Vertex Colors into Blender 3.2?
Then go to Material Properties, create a new material, click the yellow dot next to "Base Color", and in the far left column...
Read more >Make vertex colors visible | Maya 2020
Automatic vertex color display is enabled by default. The following conditions must be true for polygon colors to be visible in view panels....
Read more >Instancing - LearnOpenGL
Say you have a scene where you're drawing a lot of models where most of these ... Compared to rendering the actual vertices,...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, cool. Patch is just
Yes. (It sounds like in Three.js a material corresponds to a unique shader/pipeline.)
Let’s ask @julienduroure’s opinion. This got added as part of the initial fix for materials not being duplicated in #30.