Godot: Mono 3.0.3rc1: Core API hash mismatch!

Created on 3 May 2018  路  5Comments  路  Source: godotengine/godot

_(tried searching all issues tagged 3.0.3 nothing popped up)_

Godot version:
3.0.3rc1

OS/device including version:
Windows 10

Issue description:
Starting up godot 3.0.3rc1 in the console this error appears

OpenGL ES 3.0 Renderer: GeForce GTX 970/PCIe/SSE2
Mono: Initializing module...
ERROR: GDMono::_initialize_and_check_api_hashes: Mono: Core API hash mismatch!
   At: modules\mono\mono_gd\gd_mono.cpp:318
ERROR: GDMono::_initialize_and_check_api_hashes: Mono: Editor API hash mismatch!
   At: modules\mono\mono_gd\gd_mono.cpp:327
Mono: Runtime initialized
Mono: INITIALIZED

Steps to reproduce:

  • I uninstalled mono 5.4.1
  • I installed mono 5.10.1 Stable (5.10.1.47) x64
  • Restarted PC
  • Restarted Godot 3.0.3rc1
bug buildsystem

Most helpful comment

Just a heads up @akien-mga @neikeq this is a show stopper issue. You cannot build or test projects for 3.0.3 RC1 mono as of right now. Any ETA on a rebuild of RC1 mono?

All 5 comments

This turned out to be an error in the build scripts. This should be corrected soon, sorry for the inconvenience!

Yeah this completely breaks scripts it seems.

ERROR: GDMono::initialize: The loaded Core API assembly is out of sync
   At: modules\mono\mono_gd\gd_mono.cpp:253
ERROR: GDMono::initialize: The loaded Editor API assembly is out of sync
   At: modules\mono\mono_gd\gd_mono.cpp:261
Mono: Proceeding to unload scripts domain because of invalid API assemblies

Is an error that spits out when trying to execute a simple script to a scene.
TestingGlobals.zip

Another project I had doesn't acknowledge autoload scripts "Autoload script must extend a node" which it does, it's just broken here because I'm guessing the assemblies issue.

Just a heads up @akien-mga @neikeq this is a show stopper issue. You cannot build or test projects for 3.0.3 RC1 mono as of right now. Any ETA on a rebuild of RC1 mono?

I'm also getting this from the current master. I couldn't spend enough time to do a proper bisect, but I can confirm that the revision 48f9e6a05 works while 224d5371ff65a doesn't on my end.

This is fixed in 3.0.3-rc2. Closing this issue.

Was this page helpful?
0 / 5 - 0 ratings