If it's just a new editor and not a new engine I don't really see why it can't be made into a giant update.I always half-expected Construct 3's events to be C# or something instead of HTML5, but I guess I'm just dreaming.

The moderators are corrupt and ban for no reason, especially that condescending neckbeard asshole Kyatric. The forums are filled with fanboys.

Node-webkit had a bug in the latest version inherited from Chrome 38. I don't think we're going to do a colossal amount of work rewriting a semi-compatible native engine just to work around a bug which should hopefully be fixed soon.

C3 could very well export to exe, if an exporter was made for it.C2 (and hopefully C3) was made so that exporters could be made to use the xml events, its just that other platforms would require as much development as html5 has had.Originally the hope was that an edk would be made to help third parties make their own exporters, and plugs for said platforms.It just so happens that wrappers exist that bypass that step.

I think it's just kind of weird that Construct 2, which is a paid software doesn't have native application exporting, while this which is free and open source exports both native and HTML5. I actually gave it a try and it's quite wonderful for exporting, but it's UI is nothing even close to Construct 2.

@Ashley would it be possible for you or someone else to check out the source code of that engine and kind of convert it's native exporter for Construct 2?

The moderators are corrupt and ban for no reason, especially that condescending neckbeard asshole Kyatric. The forums are filled with fanboys.

Nesteris wrote:I think it's just kind of weird that Construct 2, which is a paid software doesn't have native application exporting, while this which is free and open source exports both native and HTML5. I actually gave it a try and it's quite wonderful for exporting, but it's UI is nothing even close to Construct 2.

@Ashley would it be possible for you or someone else to check out the source code of that engine and kind of convert it's native exporter for Construct 2?

As stated often enough a completely new exporter would require the recreation of every plugin. I think it's also the case in GDevelop that not every plugin/object works for every exporter.

I'd still love a native Windows exporter at least. Of course it would obviously ditch all the web specific plugins/functionality. Here's an idea though: hire 4ian (developer of GDevelop) to do a native exporter for C2 supporting the most important plugins.

PixelRebirth wrote:Here's an idea though: hire 4ian (developer of GDevelop) to do a native exporter for C2 supporting the most important plugins.

But you know - we live in a wonderful age where people can put their money where their mouth is - why not kickstart a native hardware accelerated exporter for C2 with a series of special plugins for some necessary functionality? I'm sure for the right price it would be quite possible.