Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0b2
Issue ID
913831
Regression
No
Automatic shader upgrade creates inconsistencies in the line endings
Repro steps:
1. Create a new project
2. Create a new "Shader" -> "Standart Surface Shader"
3. Open the new Shader file and show the line endings
4. Paste in the provided Shader code and convert the line endings to Windows (CR LF)
5. Save the Shader file and enter the Unity Editor
6. Notice the "inconsistent line endings" error
7. Enter back to the Shader file and notice that it needs to be reloaded
8. Reload the Shader file and notice that at the Top of the file a new line was automatically added that has different line ending from the rest of the code
Expected result: The automatically added line endings should be like the rest (CR LF in this case)
Actual result: The automatically added line endings are different (LF) than the rest (CR LF)
Reproduced with: 5.6.0f3, 5.6.1p1, 2017.1.0b7, 2017.2.0a1
Did not reproduce on: 5.5.3p4(No code to automatically update)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
Add comment