Search Issue Tracker
Third Party Issue
Votes
0
Found in
2018.4
2019.4
2020.3
2021.1
2021.1.0f1
2021.2
Issue ID
1334013
Regression
No
[Windows] Semantics are not holding consistency between vertex output and fragment input
How to reproduce:
1. Open the user's attached project and Scenes/semantics scene
2. Observe the Cube in the Game view
Expected result: the color of the Cube is rendering world position
Actual result: the Cube is grey
Reproducible with: 2018.4.35f1, 2019.4.28f1, 2020.3.11f1, 2021.1.10f1, 2021.2.0a19
Notes:
1. Not reproducible when Graphics API is set to Vulkan, OpenGLCore, OpenGLES2, or OpenGLES3
2. Reproducible when Graphics API is set to Direct3D11 and Direct3D12
2. With Direct3D12 Cube is transparent
3. Issue is not reproducible when struct members of vertex output and fragment input order is the same
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note (2021.2.X):
It looks like it's just the way that FXC and DXC work - they don't respect the TEXCOORD index and just use the order of declaration for register allocation. There's also no way to manually specify the register index.
It seems the only way to do this correctly is to keep the order of declaration the same between shader stages.