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
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
- [VFX] Deleting “New Group Node” name doesn’t allow to type or add new name
- [VFX] Creating a long Group Node name breaks nodes boarders
Resolution Note:
[various]
Closing older low priority bugs that have not increased in user pain and are not blocking for users shipping projects.