Construct 3 NW.js desktop app

  • The desktop build still uses zips for NW.js exports, because extracting the files on a Windows machine breaks Mac and Linux exports, because Windows doesn't understand the special file permissions needed for executable apps on those systems. The zip file is configured to set the right permissions so it works if you extract it on the target system. See the tutorial Exporting desktop apps with NW.js.

    That doesn't apply to any of the other exporters, which let you export to a folder in a desktop build.

  • The desktop build still uses zips for NW.js exports, because extracting the files on a Windows machine breaks Mac and Linux exports, because Windows doesn't understand the special file permissions needed for executable apps on those systems. The zip file is configured to set the right permissions so it works if you extract it on the target system. See the tutorial Exporting desktop apps with NW.js.

    That doesn't apply to any of the other exporters, which let you export to a folder in a desktop build.

    Thank you for the explanation! I looked at the tutorial and tried to understand the best I could, so unfortunately there's no way around this? I only export for windows anyways (choose to export only the "win32" option), so I think it'd be nice if the option to export as a non-zip file could still be there somehow.

    Plus, C2 exports all 5 builds as non-zip files, does that mean the mac/linux builds exported in C2 were broken all along? Or does it mean things changed since then?

  • Updated the original post with new downloads based on Chrome 73 (NW.js 0.37.0). There's also a fix for the C3 runtime's worker mode not working in preview.

  • Thanks Ashley!

  • Thanks for keeping things up to date! Would really appreciate MacOS builds in the near future.

  • There is no way to open and insert an image, just drag and drop the image into the program.

    The effects button is stretched across the entire width of the app and works on both sides.

  • Is it normal for the NWjs build to not automatically register file type associations for .c3p and .c3proj files? This seems to work fine in the Microsoft Store (Windows 10) build.

  • I decided to try C3 and downloaded the desktop version, I went to link Dropbox and any attempt to enter my user name or go back just closes the app! So I guess cloud saves don't work with the desktop build yet?

  • One drive and Google drive work for me. Have

    Not tried Dropbox.

  • Updated the original post with new downloads based on Chrome 74 (NW.js 0.38.0).

  • Awesome, gonna try it out, hopefully no more crashes :S

  • Awesome, gonna try it out, hopefully no more crashes :S

    Nah still crashes, useless.

  • I've been using Construct 2 for quite some time, then Construct 3 kind of killed C2. I didn't like subscription model and I didn't like the idea of programming in a browser. While it's great for learning or prototyping, it's not the way to produce real games for real playing. So I sadly moved on.

    Today I discovered there is a desktop version of Construct 3! Great! Now I'm really thinking about moving back. I still think there is no better tool (for simpler sort games) then even-based Construct.

    But I'm reading here in comments that Desktop C3 is still not as "desktopy" as C2. Is it still the case? Has it improved in those few months? Is it reliable, fast and responsive enough to use for serious every-day development?

  • Unprofessional I've been making games for a living for about 5 years now using Construct and porting my projects to C3 from C2 was a huge hassle but definitely worth it in the end. My projects are pretty huge and C3 nowadays handle them decently.

    This is the project stats of one which should go on Steam...at some point.

    The current desktop version is bugged from nwjs and has an issue they'll hopefully fix soon. The desktop version is just the app wrapped with a bit more functionality.

    If you rely a lot on plugins I'd say you might have some problems, otherwise C3 for me was great. Kinda sucked since I started using it from beta and that was hindering me a lot but that's my fault.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Thanks Fawk!

    You gave me even more to think about now. I can't believe you have 112 event sheets, how do you manage that?

    So, it seems to me it does not make much sense to use desktop at all. Does it? Do you use C3 in Chrome or do you prefer desktop version? Yes, I need some custom plugins for sort of a scripting, but if I understand correctly it should be relatively easy to rewrite them for C3, right?

    Ok, so give me an honest answer, cause I have really nobody else to ask: does the web-based interface of C3 work for you? Do you prefer to work in a browser or would you rather have the desktop app, like good old C2? Or maybe it doesn't really make any difference? I love Construct 2, but I still have doubts about this browser thing.

    What does your experience tell you?

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