Originally posted by Meerschaum:

crashes on almost 70% of the turns in which I had combat - trying 32-bit mode...

I have about 10 dumps - despite re-downloading reinstalling, , verifying cache, manually running all the packaged dependencies - it's still having issues....

Write to location 050f0ef0 caused an access violation.

that - and it's looking for a file that doesn't exist, that the installer won't install
---
D:\SteamLibrary\steamapps\mono\mono\mini\mono.exe

It looks like an error that's not limited to Endless Legends - here's a report from MMX.

System.TypeInitializationException: An exception was thrown by the type initializer for Mono.CSharp.CSharpCodeCompiler ---> System.IO.FileNotFoundException: Windows mono path not found: E:\Program Files (x86)\Steam\steamapps\mono\mono\mini\mono.exe

http://forums.ubi.com/showthread.php/826242-BUGLIST-Please-report-bugs-here-Forums/page62


And from Endless Space (useful, since it's the same studio):

System.TypeInitializationException: An exception was thrown by the type initializer for Mono.CSharp.CSharpCodeCompiler ---> System.IO.FileNotFoundException: Windows mono path not found: D:\Program Files (x86)\Steam\steamapps\mono\mono\mini\mono.exe

at Mono.CSharp.CSharpCodeCompiler..cctor () [0x00000] in <filename unknown>:0

--- End of inner exception stack trace ---

at Microsoft.CSharp.CSharpCodeProvider.CreateCompiler () [0x00000] in <filename unknown>:0

at System.Xml.Serialization.XmlSerializer.GenerateSerializers (System.Xml.Serialization.GenerationBatch batch, System.CodeDom.Compiler.CompilerParameters cp) [0x00000] in <filename unknown>:0

at System.Xml.Serialization.XmlSerializer.RunSerializerGeneration (System.Object obj) [0x00000] in <filename unknown>:0

System.TypeInitializationException: An exception was thrown by the type initializer for Mono.CSharp.CSharpCodeCompiler ---> System.IO.FileNotFoundException: Windows mono path not found: D:\Program Files (x86)\Steam\steamapps\mono\mono\mini\mono.exe

http://www.lmpgames.com/output_log2.txt


I'm presuming that all three use the unity engine. On researching it, yep, looks like it's a Unity compiler issue with the 64 bit version:

What you're launching there is actually the 32-bit version - which is the workaround for this issue. We're talking to the Unity team to work out what's causing the problem with the 64-bit version.

If you want to launch that version through steam, set the custom launch options (from the game properties) to "-force32" (without the quotes). We'll post an update as soon as we confirm a fix for 64-bit though!

http://www.big-robot.com/forum/archive/index.php/t-904.html


Looking into it a little deeper, mono is an open source .net framework - http://www.mono-project.com/



Solution:


Reinstall the official Microsoft .net framework and make sure you have version 4.5.1

http://www.microsoft.com/net/downloads

Unlikely to work, but there might be value in having an alternative for Unity to use.


TL;DR


Looks like it's a common issue with the Unity engine & certain 64 bit architectures. Wait for a patch (Unity -> Amplitude - > Us).

I do have .NET 4.5.1. Oddly, I haven't seen it since using the 32-bit workaround for AMD - but I might just not be taking the action that triggers it.

I'd been getting crashes to desktop frequently - I've gone 90 minutes without a crash so far - hoping it stays good,

mono\mono\mini\mono.exe... :)