Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0a1
2018.3.0b2
Issue ID
1083445
Regression
Yes
API Compatibility Level changes when upgrading Project from 2018.2 to 2018.3/2019.1
Steps to reproduce:
1. Create a new project in 2018.2
2. Change Scripting Runtime Version to .NET 4.x Equivalent
3. Confirm that the API Compatibility Level has changed to .NET 4.x
4. Open project in 2018.3 or 2019.1
Expected results: The API compatibility level doesn't change
Actual results: The API compatibility level has reset to .NET Standard 2.0
Reproduced with: 2019.1.0a2, 2018.3.0b3
Not reproducible: 2018.2.8f1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment