Search Issue Tracker
By Design
Votes
0
Found in
2018.3.0b6
Issue ID
1092037
Regression
Yes
Use of unassigned local variable error after upgrading project
Steps to reproduce:
1. Open attached project
2. Notice error "Use of unassigned local variable 'val'"
Reproduced with: 2018.3.0b6, 2019.1.0a5
Not reproducible: 2018.2.13f1
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 (2018.3.X):
The Roslyn C# compiler reports some warnings that the mono C# compiler did not. I have added section at end of Upgrade Doc mentioning potential of new compiler warnings from Roslyn.