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
- Memory is allocated but nothing happens when duplicating Values with the duplication shortcut in the Inspector
- Frame rate becomes lower after turning vertical sync on and off when in the Player on macOS
- Memory Profiler fails to enumerate a specific Heap Segment
- Performance gets worse when updating the Material of Tilemap
- Script causes Console error "Reading pixels out of bounds of the current active render texture" when entering the Play mode on a HDRP project
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.