Ashley's Forum Posts

  • It works fine here. It's impossible to help without comprehensive details about exactly what you are doing - see the bug report guidelines for the kind of information we need.

  • That's what the addon SDK is for.

  • Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

  • Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

  • No, don't use the Platform Info object. See the example Detecting input method for the best way to do this.

  • Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

    • Post link icon

    Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

  • SVGs are currently rasterized to a texture for rendering in WebGL, so I'm afraid at this time they still use equivalent memory to a bitmap image.

  • I don't know what your question really means, but please note the Construct source code is not open source and so you cannot use or publish it separately to Construct itself. Further we strongly advise against ever modifying any of the Construct addons themselves anyway, even within the confines of Construct itself, because it creates nightmare compatibility problems. In effect if you change so much as a single line of code you void your warranty and we can no longer provide you support in any capacity whatsoever.

  • I have to emphasise that I wrote all of that assuming we had unlimited resources. In reality we have limited resources and we'd be lucky to do a fraction of that. Please do not assume all of that is coming.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

  • Sorry, we had a brief outage on the build server. Apologies for the inconvenience, it should be back to normal now.

  • Oh, and if we could throw dozens of developers at it, then console support too.

    Also in most of these areas you can see we've made some kind of effort towards them, but there is always a long way further we could go!

  • It's an interesting question and one I've not given much thought to, because nearly everything about running a small company like ours is basically about ruthlessly prioritising extremely limited resources between hundreds of possible things that we could be working on. However if we had unlimited resources, a few things I'd like to see would be:

    - making C3 a comprehensive animation tool as well, based around the timeline. This would involve scene graphs, full vector support everywhere images can be used, and more advanced animation features. Basically what Flash used to be for animation on the web.

    - full support for using C3 as a pure coding IDE in addition to event sheets (note this is taking nothing away from event sheets, which are still an essential part of the product). Basically the best of both worlds, excelling in both programming and non-programming.

    - full international support, with the full C3 manual and all tutorials translated in to lots of languages, and support teams all over the world able to provide good support in a wide range of languages and countries

    - widespread use of C3 in education internationally, with comprehensive curricula for teachers to use for a wide range of education systems around the world (including in a wide range of languages)

    - pretty much everything filed on the suggestions platform, including some basic 3D features, ability to make plugins/behaviors etc in events, and the long tail of everything else everyone wants.

    It's nice to dream, but we have very limited resources. I don't think many people appreciate how much everything we do is driven by opportunity cost - i.e. doing one thing means not doing everything else that could be done. So is the thing we're doing the most important thing that we could be doing? It's a really hard judgement and often impossible to tell. I know some people may feel impatient when asking for features that were asked for a long time ago but still haven't been done, but imagine 20 similar features with lots of people asking for those, each one taking 6 months (so there's ~10 years of work being asked for). If we pick two and spend an entire year doing them, 18 are still left behind, and that's 18 sets of users still impatiently asking for the same things. It's impossible to do everything.

  • If you get familiar with debugging script, then you can use it to explore APIs before they are documented, as shown here: