Ashley's Forum Posts

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Jase00 - if Chrome is using up memory without ever releasing it, that is a Chrome bug, not a Construct 2 bug.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  You can already access the tile state using the "Compare tile state at" condition.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Fixed for next beta.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Closing as won't fix, this looks like a mistake in your events. Please also see the bug report requirements regarding providing a minimal .capx; this project has over 100 events, most of which are unrelated to the problem.

  The problem seems to stem from the first action of event 7 in the "Rope" sheet. It looks like you create a chain of objects going vertically down, then you just "set position" the last one to the destination position. As the physics tutorial describes, this effectively teleports the object, and since teleporting an object is a physically unrealistic thing to do the results are often also physically unrealistic. I think you need to find a better way to create the chain.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  The .capx link is not working for me, it freezes the browser tab. Filedropper frequently does not work for me anyway (links mysteriously just redirect to the home page). Can you upload the .capx to a more reliable host like Dropbox, Google Drive of OneDrive?

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Closing as not a bug. Browsers use garbage-collected memory, so they do not immediately release resources, only when they collect garbage. So you should not expect destroying objects to immediately release anything. If you have a lot of spare memory, e.g. 4 GB RAM with 2 GB free, and the browser is only using 100mb, it may quite reasonably decide there's no point wasting CPU time running garbage collection. If it does start to run out of memory it will then collect garbage to free up memory, preventing any crashes related to running out of memory due to uncollected garbage.

  You can verify this is the case: create 100mb worth of objects, destroy them, open Chrome's dev tools, go to the Timeline tab, and click "collect garbage". The memory use instantly drops down to ~30mb.

  If you experience any crashes it is very unlikely to be caused by this, so you need to find what the real cause is and report a bug based on that.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Thanks, should be fixed in the next beta.

• Try Construct 3

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

  Try Now Construct 3 users don't see these ads
• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  It is incredibly difficult to debug anything other than trivial .capx files. This project has 58 events, most of which are probably irrelevant to the problem. Please see the bug report requirements for information about submitting a minimal .capx and then file a new report. Closing.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Closing; please see the bug report requirements

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Closing, please see the bug report requirements.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  Thanks, should be fixed in the next build.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  According to Google the 64-bit build of Chromium is in some cases faster more stable. However it doesn't run on 32-bit OSs. So you should probably go with both.

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  We're open to suggestions, but note that:

  • we continually get far more suggestions than we can possibly reasonably address, so we cannot do everything
  • suggestions about a specific color to use are pretty irrelevant and distracting at this point, it seems totally trivial next to architectural suggestions
  • vague suggestions are pretty useless - saying things like "A bit of each good feature of Unity/Unreal Engine" does not actually suggest anything specific, what exactly are the good bits and how do you want them to work in the context of Construct 2? Otherwise I have no idea what you are talking about.

• You do not have permission to view this post

• • Ashley Construct Team Founder
  • 
    Moderator
  • • Joined 21 May, 2007
    • 
    • 672 topics • 31,107 posts
  • 1

  • 19 Jun, 2015
  • Quote

  I can't reproduce, it works fine here. Are you using the latest version of NW.js?