Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
2017.1.0b1
Issue ID
902667
Regression
No
Standalone builds crash on launch: 'Failed to load mono' fatal error when built with 4.6 .NET scripting runtime
Steps to reproduce:
1. Create a new Unity project
2. Open player settings
3. Select 'Experimental (.NET 4.6 Equivalent)' Scripting Runtime Version
4. Build and run
Expected result: app launches
Actual result: 'Failed to load mono' fatal error is thrown on launch
Workaround: restart Editor
Reproducible with 2017.1.0b1
Not reproducible with 2017.1.0a6
Tested on Windows 10 Pro, Version 1703, OS Build 15063.138
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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
tomhsmith
Oct 13, 2017 06:38
oops, meant C# 6 and .NET 4.6
tomhsmith
Oct 13, 2017 06:38
Happened to me today, .NET 6, was building fine yesterday.
Green-Sauce-Games
Sep 30, 2017 02:37
It still happens to me! It seems related to using Null Propagation and .Net 4.6 Script Runtime.