Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
0
Found in
2018.4
2019.4
2019.4.12f1
2020.1
2020.2
2021.1
Issue ID
1297115
Regression
No
No error is thrown and the Compute Shader ignores the code when the code is written after an inconsistent line ending
How to reproduce:
1. Open the attached "1297115_Repro" project
2. In the Project window select the "BrokenCompute.compute" Asset
3. Observe the Inspector (Window->General->Inspector)
Expected results: The "syntax error: unexpected end of file at kernel Generate Mesh" error is in the Inspector
Actual results: No errors are in the Inspector, the script can be compiled but the code will be ignored
Reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1, 2020.2.0f1, 2021.1.0a10
Notes:
- Adding any line after the line with a different line ending will remove the error from the Inspector and the Shader can be compiled but any code after that line will be ignored
- Opening the script in Visual Studio the "Inconsistent Line Ending" warning will pop up if it's enabled
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a3
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b4
Resolution Note (fix version 2020.2):
Fixed in 2020.2.4f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.21f1