Eevee: Fix generated coordinates when no texture coordinates connected
Orco should behave the same if it comes from unconnected vec inputs, or
from the Texture Coordinate -> Generated node output.
Fixup for 11e7e0769a
.
This is related to T52528. The coordinates are still different between
Eevee and Cycles, but at least it behaves consistent within itself.
In fact the shader should now be correct, but the orco attributes we are
passing the shader seems to be where the problem is. But it's to be
tackled separately.
This commit is contained in:
parent
9e762693db
commit
0e29a97813
Notes:
blender-bot
2023-02-14 06:39:21 +01:00
Referenced by commit 99b1f9f4f4
, Revert "Eevee: Fix generated coordinates when no texture coordinates connected"
Referenced by issue #52528, Eevee nodes (e.g., Checker Texture) has different coordinates than Cycles when no UV
|
@ -2472,7 +2472,7 @@ void generated_from_orco(vec3 orco, out vec3 generated)
|
|||
#ifdef VOLUMETRICS
|
||||
generated = worldPosition;
|
||||
#else
|
||||
generated = orco;
|
||||
generated = orco * 0.5 + 0.5;
|
||||
#endif
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in New Issue