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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Add comment