Ashley's Recent Forum Activity

  • Oh, right, in C3 as long as you extract the zip on the target system it will set the correct permissions, so you shouldn't need to worry about that.

    nacl_helper_bootstrap is the wrong file. The file will be named either nw or the name of your project (I can't remember which right now)

  • Good idea, updated the C2 and C3 manuals to mention this.

  • Change the 'background color' project property.

  • This is currently by design. The top end is currently exclusive, so it's essentially doing the comparison lower <= n < upper. This is because otherwise adjacent ranges become overlapping. For example suppose you have:

    Is between 0 and 90 degrees: do A

    Is between 90 and 180 degrees: do B

    It seems reasonable to expect that it would only ever do A or B. However if we make the range inclusive, it becomes possible for both conditions to be true at the same time, when at exactly 90 degrees. This may be a bit of a surprise, and is also tricky to work around: you have to make the second condition "is between 90 + tiny amount and 180 degrees". Then there's a possible secondary bug where if the object is pointing just in between 90 and 90 + tiny amount (which is easily possible with floating point precision, e.g. doing a calculation that results in 90.0000000000000001 degrees), then neither condition is true, which is even more confusing.

    So I don't think this should be changed. It would also be a non-backwards-compatible change, which could break projects. Perhaps we could add an extra parameter to make it an inclusive check.

  • It still runs the events, but it's very quick, since it immediately finds no instances to run then moves to the next event. You can optimise it by putting them all in a group and disabling the group, which will not even try to run the events, but that tends to be a micro-optimisation that doesn't benefit much.

  • It's not currently planned. But I'm not sure why you say "more than 50 megs is OS integration". If you target Android 5.0+ then you get almost the entire 100mb for your app's data alone with very little overhead. As far as I'm aware not many games are running in to the limit.

  • You could use the SDK to write a plugin to do this, and not break minification. It'd also integrate more nicely with events.

    I'm a bit skeptical of unloading objects - in many cases it won't reduce the peak memory usage, so won't help avoid out-of-memory crashes. What are you doing that requires this?

  • Construct 2 is mature software; we've fixed thousands of bugs over the 6 years it's been released. These days, genuinely over half of all bug reports are just mistakes in events. We can't deal with thousands of reports if we have to sift through hundreds of events every time, so we hold everyone to the bug report requiremenets. It's not just you, we do this routinely. The linked thread explains the rationale in detail.

  • I think this is caused by the same underlying issue as this bug: when hitting a surface it can sometimes stop with a small gap, since it stops as soon as the next step (which at high speeds is a visible distance) goes in to a solid. However with a lower acceleration, it then starts accelerating in to the small gap, and then hits the solid again leaving a smaller gap, which it can then accelerate in to again... this causes the "blinking" effect as it alternates between moving and stopped.

    I've fixed the other bug for the next build so it stops within 1px of the obstacle it hit. Since this eliminates the gap and there's nothing to accelerate in to, it seems to also fix this issue as well. So it should be working in r248.

  • It's stopping as soon as its next step would go in to an obstacle, which with a high speed/acceleration can leave a visible gap as the step size is large. I've adjusted the next build to search for a much closer position when this happens so it should always be left adjacent.

  • Should be fixed in the next build.

    Note the debugger shows the correct values; the text object sometimes applies a small amount of rounding. Since math calculations on CPUs aren't exact, it was calculating a value like 0.000000000000001 as the Y speed, which ended up causing "is moving" to be true because it was nonzero.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Closing, please see the bug report guidelines. You have 175 events, so the problem could easily just be a mistake in your events. Please create a minimal .capx as the bug report guidelines describe if you want it to be investigated. If you need help getting events right please post in the "How do I" forum instead.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,774,105 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