How do I preview the game outside the browser

0 favourites
  • 6 posts
From the Asset Store
This is a single chapter from the Construct Starter Kit Collection and the Student Workbook from the Workshop.
  • Hello, all videos I've seen are using the browser to preview the game. I suppose there is a way to compile the game as standalone Win EXE in the full version. Is there also the way to preview the layout during development as desktop binary rather than HTML5? I expect there will be huge performance difference between two of those when it comes to heavy projects. Running preview only in browser could be a big problem at some point. I couldn't google the answer for it and I'm not feeling like buying the full version just to test that. Can anyone confirm the feature or point me to answer? Thank you.

  • You can preview your game through NW.js instead of the browser

    https://www.scirra.com/nwjs

  • Phew, thank you, but that raise more questions. Now, when I know what to look for, I see NW.js is also used as one and only way to make Windows executable. I though, C2 is producing actual standalone binaries for the Windows, plus maybe with some dll dependencies, DirectX etc. Though this suggests, the game will always run through intermediate code using NW.js as the wrapper, which is basically the Chrome. However, as the NW.js seem to be the only way to make Windows executable and I've seen some pretty complex games made with C2 that had no issues with the performance, I guess it's alright not to worry about the performace beforehand.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Phew, thank you, but that raise more questions. Now, when I know what to look for, I see NW.js is also used as one and only way to make Windows executable. I though, C2 is producing actual standalone binaries for the Windows, plus maybe with some dll dependencies, DirectX etc. Though this suggests, the game will always run through intermediate code using NW.js as the wrapper, which is basically the Chrome. However, as the NW.js seem to be the only way to make Windows executable and I've seen some pretty complex games made with C2 that had no issues with the performance, I guess it's alright not to worry about the performace beforehand.

    As far as I know NW.js is currently the only make to produce a Win binary executable with C2, I have yet to have a performance issue with C2 using the nwjs wrapper but I also focus heavily on performance and the weight of my gfx, sfx etc.

    I.E. as soon as I build a mechanic for a game I immediately do a play-test and then look to see if there is anyway I can possibly optimize or shorten anything in said mechanic. But that is just my habit.

    Also there are plenty of resources on keeping your game optimized in C2.

    https://www.scirra.com/manual/134/performance-tips

    https://www.scirra.com/blog/83/optimisa ... -your-time

    http://www.burquitlambadgers.com/2015/0 ... ance-tips/

  • Thank you for the tips, I'll sure have a look at them once I get some knowledge of C2. Haven't done anything yet and already dealing with perfomance issues, lol. But I had to be sure to choose the right tool. Currently I don't have knowledge of any language useful for making games these days. C2 might be my fastest ticket in.

  • Experiment a bit first! You'll be surprised at how far you can get with 100 events.

    Generally speaking, most people do run into performance issues sooner or later, but nearly all of these problems have to do with how they set up their code (loops) and how they make use of their graphics in terms of resources/memory (too many/large sprites and objects). It is rare for projects to get to the scale where the chrome wrapper will make a noticeable difference in performance.

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