So as of Nov 25 2014, Construct 2 does not export to .EXE?

I wanted to know as I am interested in this product, however, I was alarmed this program does not allow you to simply export to a simple standalone runner for your game and needs google chrome. I am alarmed only because your free product that you give away, Construct Classic, does allow this.

So, Should I just stay with Construct Classic? I mean how do all of you sell your apps besides those who stream through webbased/adrevenue channels or share them with your friends who do not have internet connections?

I am trying to compare this to other competitive products such as the dated Clickteam fusion 2.5 which developers have native .exe export-to support for. (The cost of that programs development version makes me look at this as an alternative).

I realize you can already export to some pseudo stand-alone app with that node webkit but I just wanted to know if this is supported now or if its the same as it was in 2013 and if there is a reason not to bother adding it to this software.

As of today, C2 does not export .exe

It does export a standalone app (NodeWebkit)

Check https://www.scirra.com/store/construct-2.

As can be seen, C2 exports to standalone, as well as many other platforms, but you will need a license to access the exporters.

Check .

As can be seen, C2 exports to standalone, as well as many other platforms, but you will need a license to access the exporters.

Sorry, I am now confused, I read the same as you have now but the post above you states only node appwebkits are available. So if I bought the payed version I can export to .EXE?

There is only one exporter, html5. There are several wrappers, one of which allows you to have a packaged exe via Node-Webkit.

That is with a licensed version.

https://www.scirra.com/store/construct-2

UtemboMcjib0 - are you asking whether you can export to .exe without using an unsupported plugin?

There is only one exporter, html5. There are several wrappers, one of which allows you to have a packaged exe via Node-Webkit.

That is with a licensed version.

Ok, I'm beginning to understand what this program is about. So everything you make is an HTML5 game and it can be made to work a certain way depending on what sort of wrapper you use. Kind of like DOSBOX making old DOS games work on windows through an emulator?

So the nodewebkit emulates games onto Windows made in Construct 2 through chrome's wrapper?

Pretty much.

Minus the emulation part.

Its a little like the exe versions of flash games.

Pretty much.

Minus the emulation part.

Its a little like the exe versions of flash games.

So this is like a pygame game needing python installed before it can run? Does the node webkit wrapper wrap the necessary chrome files inside of the folder to make it a stand alone app? I searched videos and it seemed to do so but I was not sure if that was the case. It also showed me a .pak file inside of the video which I assume houses all of your games assets when packaged and installed onto someone elses PC? Is this encrypted or just easy to open and view? I'm trying to understand how easily it is to distribute games made in construct 2 as stand alone apps is and what form these distributions take when on another persons PC. Although one thing I like is apparently all node webkit apps made in Construct 2 are cross platform from the start meaning it is supported on multiple platforms (windows, mac OS X, linux) however I am hearing some bad news about newer versions of this node webkit slowing down peoples creations. And I notice a bit more lag when playing the ghost test in a browser than it would from the construct classic stand alone version.

The Node-Webkit export is a packaged app meaning everything you will need will be created for the three different platforms separately in a folder for you to decide how to distribute them.

The platforms will vary and have multiple files, such as the pak, and the exe.

If you like C2 will minify at the time of export which effectively obvusactes the code, not that the runtime would be easily deconstructed in the first place.

As to the speed, it will depend on the system, and on the game.

There are a few speed tests, some have C2 outperforming CC, and some vice versa, but CC usually only out performs on older systems.

That may seem a bit odd, but the reason is C2 runs on javascript, and older systems lack the power to cope with it.

Node-webkit exports standalone executables for Windows, Mac and Linux, in both 32-bit and 64-bit builds for all platforms. You don't need anything else installed to run them (although on Windows you should make sure the user has the latest DirectX components installed, which is normal for Windows games). Since it's based on Chromium, it guarantees your game runs more or less identically as it does in the browser, which is a major advantage that people often don't recognise when suggesting "native exporters".

The latest version of node-webkit does have a bug which was inherited from Chrome itself. Some people seem to panic when there is a bug, but it will get fixed (especially since I believe the issue has already been fixed in Chrome, it just needs to make its way to node-webkit).

See Exporting desktop apps with node-webkit for more info.

So I took an Construct 2 example file and quickly exported it to .EXE (I zipped it for download so just unzip it you will see it's a platformer example and there is a few DLL's etc and an EXE you click to run.)

http://tinyurl.com/o7oz2o3

I will remove it in a few days.

Edit: It's the Windows 64 one so not sure if you have Windows 64 bit, but you can check the files anyway.