GLSL: Fix bug setting component=0 for an auto-location assignment.
Setting component=0 is later taken to mean the shader did so, which is not always legal. It should instead set the component as not set by the shader.
This commit is contained in:
parent
8de7e7bf14
commit
94c18a84cd
7 changed files with 21 additions and 22 deletions
|
|
@ -58,8 +58,9 @@ float cull(int i)
|
|||
layout(location = 6) in bName1 {
|
||||
float f;
|
||||
layout(location = 7) float g;
|
||||
mat4 m;
|
||||
} bInst1;
|
||||
layout(location = 8) in bName2 {
|
||||
layout(location = 12) in bName2 {
|
||||
float f;
|
||||
layout(location = 9) float g; // ERROR, location on array
|
||||
layout(location = 13) float g; // ERROR, location on array
|
||||
} bInst2[3];
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue