Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.1.0f3
Issue ID
932045
Regression
Yes
Unity-upgraded shader cause inconsistent line endings warning if saved with Windows/Mac line endings
How to reproduce:
1. Open the attached project
2. Open "Test.shader"
3. Uncomment the code and save the file using Windows or Mac line endings
Expected result: Unity upgrades the code with correct line endings (warning does not appear).
Actual result: Unity upgrades the code and messes up the line endings (warning appears).
Reproducible with: 2017.3.0a1, 2017.2.0b4, 2017.2.0b3, 2017.1.0p1, 2017.1.0f3, 5.6.2p4, 5.6.2f1, 5.6.1f1, 5.6.0p4, 5.6.0f3, 5.6.0f2.
Regression introduced in: 5.6.0f2.
Not reproducible with: 5.6.0f1, 5.6.0b1, 5.6.0a1.
Notes:
The upgraded code's line endings are correct if they were previously saved with Linux line endings.
The warning is caused by "OUT.vertex = mul(UNITY_MATRIX_MVP, IN.vertex);" line.
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note (2019.3.X):
Hi, this is a cosmetic issue that we will not be addressing. After the upgrader has run there are already file changes that need to be validated and checked into version control so some user action is already required.