Search Issue Tracker
Fixed in 2017.2.0f3
Votes
0
Found in
2017.2.0b2
Issue ID
927609
Regression
Yes
[macOS] Unity 2017.2.0b2 crashes 100% when trying to use .Net 4.6 (Experimental)
Steps to reproduce:
1. Create a new empty project
2. Go to "Player Settings"
3. Set "Scripting Runtime Version" to "Experimental (.NET 4.6 Equivalent)
4. Unity will request to restart the Editor > accept.
5. Try to reopen project
Result: Unity crashes. Unable to open project.
Reproduced with: 2017.2.0b2, 2017.2.0b1.
Not reproduced with: 2017.2.0a4, 2017.1.0f2 and earlier.
Note:
Deleting Temp and Library folders does not help.
Reproduced on macOS.
Works as expected on Windows.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Memory leak occurs when focused on Player while using Direct3D12
- 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
Add comment