Search Issue Tracker
Fixed in 2018.1.X
Fixed in 5.6.X, 2017.1.X, 2017.2.X, 2017.4.X
Votes
3
Found in
5.6.0f1
Issue ID
919351
Regression
No
Shader does not compile under GLSL due to miscompilation
Steps to reproduce:
1. Open the attached project(ShaderTest.zip)
2. Open Build Settings
3. Go to Player Settings -> Other Settings and uncheck Auto Graphics API for Windows
4. Add OpenGL and put it at the top of the list
5. Select the Debug shader in the Project window
6. Observe the error:
GLSL link error: Geometry info
0(3) : warning C7508: extension ARB_geometry_shader not supported
error: interpolation modifier mismatch for varying parameter (named vs_INDICES0) between shader stages
Expected result: Shader should compile
Actual result: Unity throws the error
Note:
Reproduced with GeForce GTX 750 TI
Does not reproduce on AMD R7 360. Shader does not turn pink. Only thrown an error is:
The given primitive topology does not match with the topology expected by the geometry shader
Reproduced with: 5.4.5p3, 5.5.4f1, 5.6.1p3, 2017.1.0b9, 2017.2.0a3
Comments (13)
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
- “FocusController has unprocessed focus events.” warnings are thrown after adding iOS, tvOS or visionOS Build Profiles
- Holes and different colors appear on default Tree Materials after applying them to the Tree GameObject and undoing changes
- Error indicating that the Text Asset Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
- Documentation installation shows "Install failed: Validation Failed" when installing Android Build Support module
- Error indicating that the Package Manifest Importer hasn't been disposed properly is logged when switching Importer Type in a Focused Inspector
susanalisa247
Sep 24, 2020 07:25
I also faced this issue in my website gameive.com and i tried the same technique and it resolved.
Ghost_101010
Jan 05, 2019 08:52
Not fixed ,Reproduced with
2017.4.14 f1
2017.4.16 f1
2017.4.17 f1 LTS
2018.1.0f2
2018.3.0f1
Ghost_101010
Jan 05, 2019 08:52
Not fixed ,Reproduced with
2017.4.14 f1
2017.4.16 f1
2017.4.17 f1 LTS
2018.1.0f2
2018.3.0f1
Ghost_101010
Jan 05, 2019 08:49
Not fixed ,Reproduced with
2017.4.14 f1
2017.4.16 f1
2017.4.17 f1 LTS
2018.1.0f2
2018.3.0f1
coen22
Feb 19, 2018 15:15
This issue also occurs in 2017.3 and the 2018.1 beta.