https://bugs.winehq.org/show_bug.cgi?id=45546
--- Comment #3 from lubosz lubosz@gmail.com --- @Anastasius
Thanks for the lengthy reply!
So apparently Unity forked Mono due to licensing issues and are maintaining it badly?
Right, the issue is less visible for me when the application runs slowly.
So the goal would be for MTGA have a mono version newer than "Wed 18th Oct 2017"? I analyzed the one from Hearthstone and it ships one that is from December 2017. Unfortunately they are not interchangable, the game does not start when I change the Mono directory.
Unable to load mono library from C:/MTGA/MTGA_Data/Mono/EmbedRuntime/mono.dll
GC_DONT_GC=1 unfortunately didn't do anything for me. Does MTGA's own mono react to this parameter at all? I also tried a wine prefix with and without wine's Mono, the outcome is the same.
The question is, why does this old Mono version does not produce this issue on Windows, and isn't it the goal of Wine to work around that?
I wonder which conditions you met for this not to crash, I also saw the issue on the AppDB. Which Windows version did you have set, which wine version did you use?