NW.js not opening after export!
____ Use latest version of C2 (r252). Export blank project to NW.js, kiosk mode (playing a game in windowed mode with the "x" looks quite unprofessional so kiosk is the only real option for distribution). ____
____ It's super easy to reproduce, and NW.js can take almost a Gigabyte from C2 AS A BLANK PROJECT so it took a while to upload.. ____
Simply Open C2 and immediately export your blank project to NW.js.
____ Run the project. Close it. Look up your processes. There will be 3 leftover NW.js processes still running, preventing the app from ever opening again.____
Steps to Reproduce Bug
- Open freshly exported NW.js file.
- Run the 64 bit version
- Close it, then try to reopen it. Notice it doesn't open (I'm using Windows 10). And also notice there are 3 nw.js processes still running, if you manually close these (CTRL + ALT + DEL), it will run again. Otherwise it won't. Very unprofessional.
____ Can only run NW.js exports once and they will never open again until you restart or shut down the processes manually ____
____ Able to open and close the file freely and repeatedly for multiple user sessions... ____
- Chrome: (YES/NO)
- FireFox: (YES/NO)
- Internet Explorer: (YES/NO)
____ Windows 10 Version 1709 / OS Build 16299.192 ____
C2 version r252 ID
____ Exact version ID of Construct 2 you're using ____