Game Crashes When Opened

One of my old projects on Steam seems to be running into a problem for some users. It was exported with the Node Webkit when I made it, and apparently it doesn't like to run on some people's computers. Here's the thread with the user's issue:

http://steamcommunity.com/app/363480/di ... 744066447/

It isn't everybody, or even a bunch of people, but I would like to know what could be causing it to make sure it doesn't happen in the future. Thanks to anyone who might be able to help!

What NW.js version did you use?

It was from about this time last year, so maybe C2 R201 or R202? I'm not too sure if the Node Webkit was it's own separate download back then or not.

There was/is a problem with NW.js and Avast, don't know if this still a problem.

https://github.com/nwjs/nw.js/issues/4023

What you could try, if the problem is not Avast, delete the folder with the name of the game in:

%USERPROFILE%\Appdata\Local

If the files in this folder are corrupt, it could cause problems, but also all save-states from the game will be deleted.

LDC Studios

Do you publish the win32 or win64 version of your game?

Edit:

your users have an exception error 0xc0000005? on an AMD CPU?

Asmodean

Thanks for that! I'll post that on the thread on Steam and see if it helps out.

MadSpy

I published the Win32 version. I'll ask them about the exception error. The user says he has a LENOVO Notepad,Windows 7.

It was from about this time last year, so maybe C2 R201 or R202? I'm not too sure if the Node Webkit was it's own separate download back then or not.

Then it might wortha try to re-export your game using the newest C2 and NW.js versions.

https://www.scirra.com/nwjs

LDC Studios

I suggest you publish the win64 and win32 and let the steam client install the right version, that should correct your issue

I suggest you publish the win64 and win32 and let the steam client install the right version, that should correct your issue

It would be a strange issue, since a win64 system should run win32 software without problem.

I have already encountered this problem