Ashley's Recent Forum Activity

  • This looks like a copy-paste of what you put on the feature suggestions tracker. Not all replacements are valid: the replacement object has to have the same instance variables, behaviors and effects. We can't make invalid replacements valid. If you think this is a valid replacement which isn't allowed, please file a bug following all the guidelines.

  • Sorry, there's a small bug where the countdown accidentally counts down to the start of the last day, not the end. The gamejam will carry on through Sunday, and I'd imagine the countdown will say something wrong during Sunday

  • Because of what I explained in my earlier reply.

  • Right click the project item in the project bar and select tools -> view spritesheets.

    I am really against any micro-management features like tweaking how spritesheets work. It is time consuming when we have stacks of other far more interesting and useful things to be working on, creates difficult bugs which only happens with certain combinations of settings, is confusing to new users, and users who don't have an intimate understanding of the engine can easily actually make things worse for themselves by naively choosing the worst option. We already see this a lot with the "downscaling quality" option, where people choose "high" for no reason, which adds probably 50% to the memory usage of the game for no benefit. It's really hard to explain to people how to use these options correctly.

  • What about collision detection with various other elements which do move

    In this case the collision checks will be far more significant, making the performance overhead of the individual objects negligible.

    [quote:2srdfutv]If so, is it possible, when disabling collision detection, to actually have that bit skipped so it does not share the vertex info to reduce that bit of overhead?

    See my earlier reply.

    but then why does Construct particles use that method?

    Because particles are an obvious and easy isolated case in the engine where you might actually create several hundred of the same "sprite" (although the individual particles are not really sprites).

  • You could always do a manual cordova build with the exported files, rather than using our build service.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • The option to disable collisions for sprites, does it remove the mentioned overhead of vertex info sharing ?

    No, but for real-world games this probably makes no meaningful difference. Also if a sprite is decorative and doesn't move, it never has the overhead of recalculating its collision box, which is much of what bunnymark is profiling.

  • Honestly, I don't think performance measurements at 50-55FPS are useful. You should run it all the way down to 30 FPS and measure there.

  • Sorry, they're not currently available. Besides, we really don't like people adjusting official addons.

  • Android 5.0+ already covers 70% of devices. This time last year it only covered 43% of devices. By this time next year, pre-Lollipop support will probably be more or less irrelevant.

    On top of that, Crosswalk is no longer actively developed, probably for the same reason, so there is little we can do if people run in to problems with it. Then there's a lot of people out there who go around the Internet saying "Construct 2 generates bloated APKs, it adds 20mb of overhead", which only happens if you select Android <5.0 support, and isn't true if you select Android 5.0+. It seemed to be a significant point to a number of users and impacted the reputation of C2's mobile export (unfairly IMO, since you could easily remove it). I'd rather make a fresh start with Construct 3 and never generate APKs with any overhead.

  • Maybe scirra should add such optimization tips to the manual.

    We've got that. It's been there for years. People still make the same mistakes, not everyone reads the manual.

    [quote:3a4n02ln]1.Construct is does not have any internal optimization regarding drawcalls.

    Completely, utterly wrong! We have very heavily optimised this part of the engine with a sophisticated batching engine based on years of engine development experience. C2's renderer is even better at batching than our old C++ DirectX 9 engine.

  • Please use the issue tracker for bug reports and follow all the guidelines to ensure we can help.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,775,581 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
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs