Search Issue Tracker
Fixed in 11.x
Votes
0
Found in [Package]
10.0.0-preview.27
Issue ID
1286430
Regression
Yes
ShaderGraph files use a mix of 'CR LF' and 'LF' line endings
How to reproduce:
1. Create a new URP/HDRP Template project
2. Create a new ShaderGraph file
3. Observe line endings in Notepad++ (Or some other editor which can show line endings)
Expected result: ShaderGraph file uses unified line endings
Actual result: ShaderGraph file uses a mix of 'CR LF' and 'LF' line endings
Reproducible with: 10.0.0-preview.27(2020.2.0a20), 10.1.0(2020.2.0b10), 11.0.0(2021.1.0a3)
Not reproducible with: 7.5.1(2019.4.14f1), 8.2.0(2020.2.0a20)
Could not test with: 2018.4(ShaderGraph was in early preview stage)
Notes:
1. HDRP/Lit and Blank shader graphs were used for the testing
2. ShaderGraph 10.0.0-preview.27 became available in 2020.2.0a20
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
Add comment