Ashley's Recent Forum Activity

  • You can't request permission in 'On start of layout'. See the manual entry for it, you must use a user input trigger.

  • Thanks for the feedback, it's interesting to see people's thoughts on C3 especially in regards to the wider market.

    For what it's worth, from my perspective points 1 to 3 are basically feature requests, and I think at least 2 and 3 are already filed on our feature suggestion platform. These all sound great and only reason things like this are not already done is we're a very small team with limited resources, and we're also being asked for literally hundreds of other feature requests. I estimate there's about 10 years work logged on our feature suggestions platform, so we have to prioritise pretty ruthlessly. FYI suggestion 2 is probably best achieved through a layer tree rather than a flat list of layers, but as with many suggestions it's pretty complicated and we have to balance it with everything else.

    Suggestion 4 should already be possible. If you disable all behaviors, stop animations, and don't run any events involving an object, then the engine does virtually nothing with it. The only thing left that it does is a tiny check every frame to see if it's visible and on-screen for drawing. This is usually negligible, but if you have the unusual case of thousands of such objects scattered across the layout so that this check is using a measurable amount of CPU, then the render cells feature should fix that. It organises objects in to cells to organise their rendering and only check instances already near the screen. This brings the engine overhead of a far-away instance to exactly zero: the engine will do absolutely nothing with it, unless your own events do something.

  • Construct's event system is itself implemented in JavaScript. So JavaScript code can do everything the event system can and more. It's a strict superset. So there are lots of things you can do in JavaScript that aren't possible in events, such as using browser APIs that are not exposed in the event system.

    The main advantage of event blocks is they are very quick and easy to set up. There are things event blocks can do in a few clicks that could take you weeks and weeks of very difficult programming to achieve in JavaScript. So naturally it's a trade-off.

  • The manual isn't updated until the next stable release, and the Physics APIs are currently only available in beta releases. In the mean time you can use debugging in dev tools to explore the available APIs.

  • You need to request permission before using motion/orientation.

  • As ever, without a project to look at, all I can say is it should work, and if it doesn't, the error message it tells you is presumably correct in its diagnosis and you should do what it says.

    I also noticed that functions are global now, you can call them from any eventsheet even if they are not attached, is this by design or a bug?

    This is by design.

    • Post link icon

    This looks like a duplicate of this thread so closing. Posting the same thread is against the forum rules, please see the Forum & Community guidelines.

  • As I said, if you can reproduce a case where Construct seems to get it wrong, please file a bug following all the guidelines. It's the usual way that we deal with problems and the process is designed to maximize the chance we can fix the problem.

  • I manually removed a few files from our releases that aren't needed for the purposes of Construct, including:

    • pnacl (Portable Native Client), a browser plugin that Construct doesn't use (and Chrome will remove themselves in future anyway), including the .nexe file
    • All locales other than en-US
    • The tools chromedriver, nwjs, payload (these are separate to dev tools and aren't generally needed in Construct)

    I did ask the NW.js developers for info about which files are essential, but they said to just use trial and error, and I've noticed the set of files changes sometimes between releases too. So basically you can find out which files are essential by deleting them and seeing if the app still starts! I'd watch out though since some files may be optional and could break features. For example the app may still start if you delete notification_helper, but then it seems likely notifications won't work any more. So it's worth doing a little research to try and figure out what the purpose of the file actually is, and if it doesn't sound important and the app starts without it then it can be removed.

  • Actually, I can't find anything that's wrong, it all seems to be working correctly. If Construct is doing something like inconsistently copying some properties but not others, please file a bug following all the guidelines.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The instance properties are stored in the instance. So if you delete it, those properties are gone.

    When you create a new instance, Construct will copy the properties of an arbitrary existing instance. If none exist, it will try to use the properties of any previously deleted instance. If there are still none, you get the defaults.

    So the properties you get depend on whether there are other instances in the project, or whether you previously deleted instances.

    I think there might be a small inconsistency in how behavior properties are handled though, they don't seem to refer back to deleted instances. I'll look in to that a bit further.

  • I've updated the original post with the new approach to releases as I outlined in January. This means you can now download your own NW.js versions to use with Construct 3, allowing NW.js updates to happen without our involvement. It also means for the first time you can choose NW.js platforms other than Windows 64-bit, such as Windows 32-bit, Mac and Linux. Note however that no testing has been done with the editor the NW.js versions of Mac or Linux, so I can't guarantee how that will work. However NW.js has good cross-platform portability so in theory it should work the same as on Windows.

    Hopefully this new approach works out smoothly; let me know if anything seems wrong.

    Note NW.js 0.45.0 based on Chromium 81 came out this week, so to update to that version, use the new approach. New NW.js versions, including beta and patch releases, are announced on the NW.js blog and on their @nw_js Twitter account.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,448,011 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x109
    Coach One of your tutorials has over 1,000 readers
  • x63
    Educator One of your tutorials has over 10,000 readers
  • x3
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x36
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs