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
- [Remote Config] PreparePayloadWithConfigType function is looking for camelCase property names, when the JSON objects are using PascalCase naming
- UI Builder Viewport's Tool Gizmo has deadzones
- SpriteShapes are rendered using multiple draw calls when the SRP Batcher determines their nodes are incompatible in a specific project
- UI Toolkit Debugger "Pick Element" selects Scene view panel when trying to select a world space UI element in the Scene view
- MSAA warnings are thrown when custom post-processing is used and the Scene contains transparent GameObjects
Add comment