Bug Experimental Mono broken on Linux

Thanks! When you say "beta" here, it applies to all the Linux builds, right?

 

Has this been fixed yet?
If not, in the above fix, is that in Unity editor project settings, i cant find any setting to switch to mono, and in monodevelop theres no setting to switch from monoBleedingEdge to anything else. Im running Ubuntu 16.04 LTS and Unity 2017.3.Op2 personal. Not sure if i just miss understood, could you please clarify.

 

I changed the runtime version in the player settings like in attached screenshot. Open it in Edit / Project Settings / Player and then scroll down to "Other settings".

 

aw, this didnt seem to fix my error. Owell time to post about it.

 

How would one go about switching from Mono Bleeding Edge to stock Mono when using Linux for CI builds via CLI?

 

Is this something that's also present on OSX? I have 2017.3f1 on Linux and the project opens fine. On OSX, the same project tracked by git, crashes on start up and the logs point to a crash while doing something with lightmaps. We are on MBE and as soon as I reverted to C# 4, the project now opens fine.

 

You can edit the field in the ProjectSettings file directly.

 

I don't understand how come this kind of stuff isn't baked into the editor release. I find it pretty unreasonable that these packages are pulled from an upstream source at build-time, and have the ability to completely grind-to-a-halt a CI process. Now we have to go through our entire project and convert back to different language features in order to get our projects to deploy again.

@PJayB - Will you be updating this particular thread once the issue is resolved, or should we be monitoring for updates on this somewhere else?

 

How does one "switch to stock Mono"? This is configurable in the PlayerSettings, correct? Even with my attached settings, I am facing problems getting anything to compile. Specifically, I am encountering this probably related error.

In the editor log, under the "Compiler Commandline Arguments", it looks like it's still using MonoBleedingEdge.

 

Any updates? Not able to use the Unity ML-Agents in Linux unless I'm on Mono bleeding edge.

 

You should be able to use the new runtime using the 2018.1b8 build: https://forum.unity.com/threads/uni...s-and-known-issues.350256/page-2#post-3398912

 

Now I can actually use the editor, thanks! Will there be any further beta updates before the final release?

 

I would assume it depends on how long until the final release. If there are 5 more betas and then RCs afterwards I would expect one more before the final one.

 

Is it possible to use the version of mono installed on system instead of the one provided with the Editor?

 

Any chance of getting an updated 2017.3 build that fixes the issue?

 

No, Unity's mono runtime is heavily customized.

 

Sorry, it looks like backporting the fixes to 2017.3 would be pretty involved, and the team is focusing on making the new runtime/framework solid on 2018.x+.

 

i get segfault on new fresh project, mono 5.14.0 do i need to downgrade or something

 

The version of mono you have installed on your system doesn't affect Unity.
If you're experiencing a crash, please file a bug report.

 

Any news about fix of this issue? Will it be fixed in 2018.3?

 

It was already fixed in 2018.1.
If you're experiencing crashes, please file a bug report.

 

I'm not sure if this is directly related to the "Failed to load Mono. Please see Editor.log file for more information." But here is what I have found out.

From Editor.log:

Unable to load mono library from /home/user/Unity/Hub/Editor/2018.3.9f1/Editor/Data/MonoBleedingEdge/MonoEmbedRuntime/libmonobdwgc-2.0.so

On Debian with SteamOS all hooked up with beta packages from valves repos so that Vulkan drivers are working on a nvidia old alienware alpha r1...

I can create, open, close and reopen all day long with 2018.3.9f1 with the "3D template" from unity hub 1.6 (platform selected linux x86_64 [not a server build fyi]) if I try to take advantage of the new Vulkan API by moving it to the top of "build -> player settings ->" uncheck -> "Auto graphics API for Linux" that is how I get the error. Just unchecking makes it so it doesn't find mono. Of course the goal is to move Vulkan to top and remove OpenGL Core. Then HD pipeline native in 2018.3 in editor using Vulkan. But for now I was going to settle for Standard pipeline on Vulkan but can't do that. as described above.

If I try to create a "3d template" from unity hub 1.6 targeting 2019.1.0b8 i get the error right away.
- now i can downgrade and open this with Unity 2018.3.9f1 just fine, only get a error on packages, the Analytics Library what not, and then the package manager ui 2.1.1 obviously won't work from 2019 to 2018, but this is not what I am reporting. It just seems like the mono location got borked. both in the vulkan graphics api settings and then in 2019 by default can't even create a basic 3d project.

[update]
i did notice that on 2018.3.9f1 i tried adding the Windows and Mac build support which include (mono) and that the 2019.1.0b8 did not have those components downloaded/installed via the Unity Hub 1.6, trying to add those components now.

[find] nope same error on 2019.1.0b8 as before even with the mono build target support for Windows/Mac...again I am not trying to target those I am just trying to target Linux x86_64 but 2019.1.0b8 nope, 2018.3.9f1 3d template still working fine so long as don't try to use new Vulkan api in build settings

[confirmed] same error creating 3d template 2019.2.0a9

/home/user/Unity/Hub/Editor/2019.2.0a9/Editor/Data/MonoBleedingEdge/MonoEmbedRuntime/libmonobdwgc-2.0.so

[also]
just posting here as not sure when i will have time to create a new forum.
the Total Space Required and Space Available on unity hub 1.6 still not calculating correctly. now matter how much space I have always says 5.8 gb avail. i have tried many different configurations to gleam where the Unity Hub is pulling that space query from to no avail

 

It calculates available space only for "/" even if you have 200gb available for "/home/" and in the hub settings you will install to "/home/..."- it will say that you have a space avail for "/" mount point.
But it can be two different partitions.