Removing all the files with game.* then running dmengine.exe again did not resolve the problem.
Renaming the folder so it doesn’t have a space then running dmengine.exe, both with and without the game.* files, doesn’t resolve the error either.
And no, I don’t have any antivirus running that might interfere. I only have Windows Firewall running, and I’ve made sure that it allows Defold and dmengine.exe through both public and private networks.
Ok, hmm, I’m out of ideas. Is there anything non-standard with your windows installation or the hardware it is installed on?
Maybe @Mathias_Westerdahl has some ideas?
There’s nothing unusual with my computer or the Windows installation. I’m not the type to mod hardware, so my computer’s the same as when I bought it. And my Windows installation should be fine too. I’m on Windows 10 Home Version 1709 OS Build 16299.371.
If we’re lucky there could be some more information on why the application stopped working in the windows Event Viewer. IIRC that type of problem ends up in the “Application” or “System” category of events. Here is a quick intro if you’re not familiar with Event Viewer: https://answers.microsoft.com/en-us/windows/forum/windows_10-update/event-viewer-what-is-going-on-in-your-computer/fdda2010-d4df-4fed-863b-89ce0142419d
Thanks for being so patient and helping us nail down this problem!
Alright, so I took a peek at the Event Viewer, and it looks like the ‘Application’ category is what logs what’s going on with Defold. After building from the editor, two events popped up, so I generated the error reports as .txt files and put them here:
https://drive.google.com/file/d/108gTMjtWTy1teKmjq1Ti1UMmN31IMeDo/view?usp=sharing
https://drive.google.com/file/d/16Rdz9YB0KTyDiPao9CIJTqfsbxL7mOIJ/view?usp=sharing
Something Intel graphics related?
What’s your GPU?
My laptop has two graphics cards: AMD Radeon R5 M335 and Intel HD 520, but AFAIK, it only ever really uses the Intel card.
Did this yield exactly the same result as earlier?
I’m wondering if it’s the fact that we require OpenGL ES 2 and that your graphics card only provides OpenGL 1.0.
You can check what version it has with glview. More info about it and where to find it in this post
Also, could you open a command prompt in your folder (where the dmengine.exe is), and launch the executable there. Perhaps it will give us some information.
Press Shift + Right Click to open the context menu, and choose “Open command window here”:
And type “dmengine.exe” and press enter
Yes, it yields the exact same Windows error message.
I’m on version 4.5, so I don’t think OpenGL is the problem.
Running a command window shows that a crashdump is created. I’ve uploaded the _crash and _crash.dmp files here:
https://drive.google.com/file/d/1MOugaQXtYTwICXXMCMGYFbWveh2i3pZF/view?usp=sharing
https://drive.google.com/file/d/1v4h8WRyQiJJt6e8kO4ysPo7r9I4ur0su/view?usp=sharing
Thanks for sending the crash logs.
Sadly, I cannot find anything really useful in the callstack (no calls to Defold) other than references to a ig9icd64.dll which seems to be the graphics driver for your graphics card. Not sure what could cause this, and googling it results in various issues which I simply don’t know if they’re related at this point.
One thing could be to check if the drivers are updated?
Just verified that all my graphics drivers are up to date.
What if you try to enable the other card instead? Does it make any difference?
Doesn’t do anything, unfortunately.
Could it be that I need to downdate my graphics drivers? I had a similar issue with the LOVE2D framework: https://love2d.org/forums/viewtopic.php?f=4&t=85031&p=219450#p219450 that I ultimately resolved by reverting to an older driver.
I hope not. That wouldn’t be an acceptable solution. BUT if you’d like to temporarily do it to help us nail down the problem then please give that a try.
You’re gonna get a kick out of this. Downdating worked. I’m not sure at exactly which graphics driver version dmengine.exe starts causing problems though, and in hindsight, I should’ve noted what version my driver was on initially… it was 22.y.z or something or other.
Anyway, here’s the steps to repro:
I am now on driver version 21.20.16.4627, and Defold has no problems building or bundling.
Ah, there’s nothing like the smell of a driver issue in the morning!
Thanks for helping figuring this out!
Would it be helpful if I go through the different driver versions to try pinpointing exactly when dmengine.exe stops working?
Well, I don’t actually think so. In the callstack I got, there was only a reference to the graphics driver, and it’s really not much we can do on our side to prevent that from crashing anyways. But thanks for suggesting it!
