Crash when exporting my game

Not favoritedFavorited Favorited 0 favourites
  • 9 posts
From the Asset Store
HTML5 Game Bundle (7 Games) – Created with Construct 3
  • Hello,

    I have serious problems with the exports of my game. Here is the behavior I have:

    1) Exporting with Steamworks plugin makes it crash (and launches Steam, which displays an error message: missing executable)

    2) Removing Steamworks plugin from the project AND not minifying the script AND exporting with WebView2 makes the build to work!

    3) If I do the same as 2) but try to minify the script, the build crashes at launch.

    4) If I do the same as 2) but export with NW.js, it crashes at launch.

    4) If I do the same as 2) but keep the Steamworks plugin in the project, the build crashes at launch.

    I can preview the game in the editor without any problem, so I doubt this is related to the events in the project (?).

    I'm really lost about what could cause that. Any idea of what could the problem be?

    Thanks!

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • What minification mode do you use? Try simple minification.

  • Without seeing a project all anyone can do is try to rely on telepathic debugging, which is notoriously unreliable - as ever the best way to get help is to share a project so others can try it out. My best guess is you somehow mixed up mismatched versions of DLLs/plugins causing it to crash on startup. Or maybe it's a graphics driver crash. Hard to say.

  • Thanks for the replies.

    After more tests, I managed to make the export work as long as I remove Steamworks, with webview and nw.js. The problem with NW.js seemed to come from command lines.

    However, with Steamworks in the project, it still crashes all the time.

    After even more tests, I noticed that keeping the Steamworks plugin in the project still works as long as I remove my events calling it. And my only events calling it are.

    Steamworks is available --> set value to Steamworks.PersonaName

    With that, the game works when launched OUTSIDE of Steam, but I still get an error message when trying to play it on Steam :

    "An error happened while launching the game: game executable missing - C:\Program Files (x86)\Steam\(path)" (translated from French)

    It's not an option to share the game publicly, as I worked on it for years, and I feel very uncomfortable just throwing my work out on the internet like that. However, if someone wants to take a look, I'd be happy to share it privately.

  • Additional note :

    On Steam, the project WITH the plugin Steamworks but WITHOUT any event using it WORKS.

    As soon as I keep my events described above in the project, Steam gives me the missing executable error message.

  • Final test:

    Keeping only "Steamworks is available" condition allows the game to run correctly on Steam.

    My theory is that the condition "set value to Steamworks.PersonaName" causes a problem within Steam.

    I created a minimal project here :

    drive.google.com/file/d/1qvVTFsA1phItDKrhehoWteW8dbbhU2Eq/view

    Exporting this and putting it live on Steam gives the error message for me when trying to launch the game.

  • I can't reproduce any problem using that minimal project (note it does not specify an app ID, so I just put in 480). It correctly launches and gets the persona name and displays it with no error messages and nothing unusual in the browser console.

    It's a really weird problem that you've described: the Steamworks plugin always obtains the persona name from the Steamworks SDK on startup, regardless of whether your events refer to it. Then when you use the PersonaName expression it just returns the string it obtained on startup. So I cannot imagine under what circumstances it would only fail when using that expression, nor how it could have anything to do with the "missing executable" error, because using that expression just returns a string in JavaScript like any other expression.

    My best guess without knowing more is some DLL files have been mixed up. The Steamworks plugin bundles its own DLLs, so if you are trying to do something like copy DLL files like you used to have to with Greenworks, you'll might actually just paste in the wrong DLL and make it crash. Using Steamworks is much simpler - refer to the addon documentation and make sure you are only doing that, and aren't doing other steps that you don't really need.

    Other than that my best guess is something has got corrupted. Try saving a copy of the project that does not work, and start over: uninstall everything, reinstall everything again being careful to get the latest version of everything - possibly on a new system entirely - and try again. If it works, you could use a diff tool like WinMerge to compare the working version to the broken version and see what the changes are (e.g. maybe a DLL file is different). If they're identical, it would mean something else on the system was wrong - perhaps a corrupt Steam install or something.

  • Thanks a lot for the detailed reply and steps on how to fix. I'll try all that and post an update here if it fixes the problem.

  • For further reference and to keep you updated, the problem is now solved without me doing anything special. Maybe a Windows update solved it, or something with the cache was going on, but I've been able to export my game with Steamworks in the project and it works just fine now. Thanks again for your help!

Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)