Search Issue Tracker
Won't Fix
Votes
1
Found in
2017.2.0f3
Issue ID
976364
Regression
No
Nested block comment with single-line comment will cause errors in shader compilation
How to reproduce:
1. Create a new project
2. Create a new Shader
3. Add lines anywhere in the shader:
/*
//*/
4. Notice, that the shader fails to compile
Actual result: There are errors caused by nested block comment with single-line comment inside.
Expected result: Shader should compile.
Reproducible with: 2018.1.0a7, 2017.3.0f2, 2017.2.1f1, 2017.1.2p4, 5.6.4p4, 5.5.5p2.
Notes:
Compiler errors:
No ENDCG tag found after CGPROGRAM tag
Parse error: syntax error, unexpected TVAL_ID
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Some UXML Template Asset foldouts appear enabled when all fields inside are disabled
- URP Terrain Demo crash on burst_signal_handler after Generating lighting
- Project window button icons are poorly visible and their shades differ in Light theme
- GC.Alloc called by HDRenderPipeline.LensFlareMergeOcclusionDataDrivenPass() when playing the default HDRP Sample Template project
- Automatic LOD fails and SRP Batcher incompatibility occurs when using spline-based quad-topology meshes
Add comment