Search Unity

  1. Unity Asset Manager is now available in public beta. Try it out now and join the conversation here in the forums.
    Dismiss Notice

[.NET 4.6] Standalone x86 builds can't start

Discussion in '2018.1 Beta' started by HarryCodder, Jan 17, 2018.

  1. HarryCodder

    HarryCodder

    Joined:
    Feb 20, 2015
    Posts:
    84
    Hello,

    Building an x86 standalone build using .NET 4.6 won't start and cause a "Failed to load mono" error instead.
    This doesn't happen when using il2cpp or with .NET 3.5 or targeting x86_64.

    I filed bug report 987235 last week but it hasn't been accepted yet.
     
  2. JoshPeterson

    JoshPeterson

    Unity Technologies

    Joined:
    Jul 21, 2014
    Posts:
    6,931
    Thanks, we'll investigate this issue.
     
    rklausch likes this.
  3. joncham

    joncham

    Unity Technologies

    Joined:
    Dec 1, 2011
    Posts:
    276
    This issue has already been fixed and will be in a future release.
     
  4. rklausch

    rklausch

    Joined:
    Jun 5, 2016
    Posts:
    10
    i can confirm that issue...none of my project builds are starting, when build with .net 4.6 and x86
    just getting a fatal error window saying "failed to find mono" . new API Comp. Level .net Standard 2.0 builds giving the same error as well. .NET 3.5 builds work fine.

    Then i updated my VS2017 to v.15.5.4, restarted my machine and switched my External Script Editor in the Preferences/External Tools menu from "Visual Studio 2017" to "Visual Studio 2017 (Community)" (whatever the difference is here) and now, x64 builds seem to start now also as .NET 4.6 Windows exe,
    But for x86 builds, the error above is remaining.
     
  5. joncham

    joncham

    Unity Technologies

    Joined:
    Dec 1, 2011
    Posts:
    276
    Correct. This issue only affects x86 Windows builds and will be fixed in future release.
     
    rklausch likes this.