Ashley's Recent Forum Activity

  • Please keep things on the feature suggestion platform, ideas in the forum will get lost. Sometimes ideas get caught by the spam filter so they don't immediately appear; if you let us know they can be approved.

  • It's complicated to make it work for user scripts. Getting it working again is on the todo list.

  • Very frequently the problem people have is they have misconfigured something, and then blame the plugin or Construct. We regularly help people get it working again by making sure they've done things like use the right IDs in the right places.

    There have been some bugs which really were in Construct. We do work hard to make sure these are resolved. However some issues are particularly difficult - the issue you linked to is tagged "difficult", but it also looks like it only happens in a specific set of circumstances, so it should not block other uses of the feature. We are a tiny team dealing with thousands of bug reports; please be patient, sometimes we need a bit more time to sort the thornier issues out.

  • NW.js only supports open media codecs like WebM VP8/VP9 or Ogg Theora. You will need to transcode your video in to one of these formats. This is not a bug and is actually explained in the manual.

  • See the note on the latest stable release which recommends the following three options:

    1. Use C3's mobile app build service to build C2 exports.
    2. Use an actively supported third-party build service like PhoneGap Build.
    3. Use the Cordova CLI. This is a free manual build tool that works offline. (This option is more appropriate for advanced users.)

  • See the note on the latest stable release which recommends the following three options:

    1. Use C3's mobile app build service to build C2 exports.
    2. Use an actively supported third-party build service like PhoneGap Build.
    3. Use the Cordova CLI. This is a free manual build tool that works offline. (This option is more appropriate for advanced users.)

  • We don't have the resources to integrate all possible third-party services. The other companies they mentioned are bigger and it's probably much easier for them to justify the developer time, but we're a tiny company and just can't afford to do that. To work around this problem, we have created a third-party addon SDK for other developers to intergate their services themselves. The Spine developers should use this. What they said about performance isn't right and looks like a way for them to try to get us to do their work for them - unfortunately we just cannot do that. Meanwhile Spriter have used our SDK to write their own integration and we got positive feedback from the developer, so I think we have everything set up well and with the full performance capabilities of the engine. We worked with Spriter to fill in any gaps in the SDK to ensure everything works well (although there are still some nice-to-have requests we have on our todo list); I am prepared to do the same with the Spine developers to fill any gaps and ensure they can implement a fully capable integration, but we cannot do it all for them. So long as there is no Spine integration I would recommend to use Spriter instead.

  • I can't comment without an example project to look at. Otherwise all I can say is: I guess that shouldn't happen.

  • Why not just try it and compare?

    It means you only need to do an export over local files instead of having to upload to Facebook and publish, which should be quicker. Note you should still use the Instant Games export, not the HTML5 export.

  • Fengist - I think you missed the bit where I wrote this:

    ...I'm just trying to find a way of doing it that doesn't oblige us to do a lot of wrapping around low-level JavaScript APIs. Construct is generally much more high-level than that, for example giving you Sprite objects, not just an OpenGL vertex buffer to fill out.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • BTW let me know if you do file an issue - I'd be happy to follow it and explain any Construct-specific details that come up (if any).

  • I think this idea in general is fairly close to something workable, but I'm just trying to find a way of doing it that doesn't oblige us to do a lot of wrapping around low-level JavaScript APIs. Construct is generally much more high-level than that, for example giving you Sprite objects, not just an OpenGL vertex buffer to fill out.

Ashley's avatar

Ashley

Online Now
Early Adopter

Member since 21 May, 2007
Last online 21 Oct, 2026

Twitter
Ashley has 1,829,225 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
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    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
  • x44
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs