Ashley's Forum Posts

  • Thanks, should be fixed in next build.

  • Should be fixed in r143.

  • Can't reproduce with Space Blaster. Closing, please follow the bug report guidelines and include a working .capx example to demonstrate the problem.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Crashing on close is a known problem for which a bug report has already been filed; closing as duplicate. Please post a new report if you can reliably get a crash in the animation editor which does not involve closing C2 as a step.

  • OK, hopefully fixed for next build (r143). Let me know when it comes out if it works for you.

  • Closing, please report this issue to CocoonJS, the audio playback will be in their code.

  • I can work around this simply by setting the layer 'Transparent' property to 'No'. Does that work for you as well?

    Generally it's a bad idea to only have transparent layers, especially with 'Clear background' set to 'No' and especially in node-webkit, since it makes the background effectively undefined. In theory it should be cleared, but some graphics card drivers aren't very tidy about that and can end up garbling the display.

  • There is no consequence to this error. It is simply looking for a file to de-minify the jQuery source, but we do not provide it because it's not necessary. TBH Chrome should probably not log an error in this case.

  • Yes, you can.

  • No, the pattern (as described in the tutorial I linked to) is just to update, make changes, commit (for SVN anyway). It should only conflict if two people change the same thing at the same time (between update and commit). Normally working in parallel is fine, but you should have some level of co-ordination to try to avoid two people modifying the same thing at once.

  • You can already do custom out-of-bounds values by accessing the array using a function from the Function object, and implement your own bounds checking in events.

    I really wouldn't want to change the existing value, mainly because it would break lots of existing projects, but also because any value could be a useful value in someone's project. -1 isn't somehow less of a valid number than 0.

  • We haven't changed the AJAX object for some time. Perhaps cross-domain issues are to blame. Look up AJAX in the manual for more information about that.

  • Post a bug report to the bugs forum following all the guidelines, otherwise we can't help.

  • Re: future platform support - we haven't made any concrete announcements, because we don't have concrete guarantees about which platforms we can support yet. However I'd say it's likely we can support the Wii U, likely we can support the Ouya (via CocoonJS - they are working on support currently I believe), and I think there's a good chance we can support the XBox One as well, since MS have said it will be able to run Windows 8 apps which we already support. Sony have made nice sounding announcements about the PS4 but we haven't heard anything that involves HTML5/web technology, so it's hard for us to predict how that will pan out.

    Monetisation is a different topic really, but we are aware we could be doing more in this area and plan to do something about it soon. Our understanding is that it's easier to make money through IAP than through advertising, so that's what we'd be looking at first.

    It should be possible for teams to work on C2 projects - see how to collaborate on projects with SVN.

  • I am pretty sure this is not Construct 2's fault. I'm not an expert on Git myself, but if it's anything like SVN, simply forgetting to update before you start working then trying to commit at the end will cause things you have not changed to conflict with things other people have changed, because your copy is out of date (and it doesn't know if your intent is to roll it back). So accidents or misuse of source control systems cause that type of error.