-
-
Notifications
You must be signed in to change notification settings - Fork 21.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is C# support broken on the 32-bit versions? #20012
Comments
I'll have a look at this. This worked in my tests on Win 7 pro and Win 10 home. (running 32bit mono binaries on 64bit windows at least) I don't have a Windows 8.1 license. I'll buy one. |
A friend of mine tested on Win 7 Ultimate x64, with Service Pack 1, and got the exact same error. |
I have a windows 8.1 license now. I'll test for 3.0.7 |
Looks like the same as #17299 |
Yeah, seems to be the same. A while after I posted this issue I began having other problems updating visual studio and even windows itself so I reinstalled it (just the "reset" install, without removing anything) and I began exporting normal 32 bit mono projects again. |
Duplicate of #17299. |
Godot version:
32-bit versions of Godot 3.0.3 and 3.0.4, running in self-contained mode.
OS/device including version:
Windows 8.1 Pro x64 (6.3.9600), installed less than a week ago so system integrity should be guaranteed
Issue description:
@hpvb
Everything using C# scripts gets compiled without errors but runs for less than a second and crashes. I even tried other examples like the demo projects and bunnymark, always with the same result.
Already tried reinstalling mono v5.12.0 Stable 32-bit and nothing changed. Didn't try older versions because Godot's download page states that only v5.12 will work.
The same projects run absolutely fine on the 64-bit version of Godot.
Steps to reproduce:
Run a 32-bit version of Godot 3.0.4 then open a project that uses C# scripts and try to play it.
Minimal reproduction project:
Literally anything that uses C# scripts, like this demo project
The text was updated successfully, but these errors were encountered: