Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4
2020.1
2020.1.0a18
Issue ID
1210102
Regression
No
No compilation error is produced when attempting to use GLSL syntax in Shaders
Steps to reproduce:
1. Open the attached project (case_1210102.zip)
2. Double click on "CorruptedShader" in the Project tab
3. Uncomment line 56
4. Comment line 55
5. Save the Shader and press Ctrl+R in the Editor
Expected result: A Shader compilation error is thrown
Actual result: A vague warning about the Shader not being supported is thrown and it is excluded from the current renderer
Reproduced in: 2017.4.36f1, 2018.4.15f1, 2019.2.17f1, 2019.3.0f4, 2020.1.0a18
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
- NullReferenceException is logged when undoing Deletion of a Visual Query Block of a Search Expression
- “Unsupported type MinMaxCurve” error and “Could not register property modification for animation binding…” warnings are thrown after moving playhead when Particle System Property is added to Animation window
- Nested LocalizedStrings can not query local variables
- Inconsistent "Mock HMD Loader" naming in the "Project Settings"
- Search Field breaks when deleting a Search Expression that has been converted to a Visual Query Block
Resolution Note:
[various]
Closing older low priority bugs that have not increased in user pain and are not blocking for users shipping projects.