Ashley's Forum Posts

  • That's a good point Yann, using families as a second independent object-picking list is probably the best unintended feature of families!

  • Try "Every 60 seconds" instead of "Time = 1 minute". Alternatively try storing 'time' in a global variable on start of layout and checking if the time is 'time + 60'. The game time is from the very beginning of the game, so the second time around the time will be 2 minutes and counting, which will not satisfy the "time = 1 minute" event ever again.

  • Are you literally typing in: Health + 1 ?

    You know instance variables have to be accessed with a dot?

    These all work:

    Self.Health

    Sprite.Health

    Family1.Health

    if you just type in "Health" it will look for an event variable by that name, and none exists, so the error is correct.

  • You have a weird collision polygon on the object: there seem to be *three* collision points on top of each other on the long edge of the triangle. This is crashing the physics behavior - I'm not sure why it does, it's the Box2D library that can't seem to handle it. I don't think there's anything I can do to fix it myself, but you can easily work around by deleting the point on the collision polygon that's in the middle of the long edge of the triangle (you need to delete it 3 times) then it works fine.

  • If you do not enable a fullscreen mode, it is by design that it appears with the border: it's displaying the canvas inline in an existing HTML page.

    I'm not sure why the canvas appears at the wrong scale in Safari, but I noticed you're checking in preview mode, is it the same after you export?

  • This probably won't be fixed because if you want to reference one layer no matter where it is, as suggested you should use its name. Using a number is for referencing a layer by index regardless of its name. For example you might want to spawn an object on layer 0 to always spawn it on the bottom layer regardless of what layers you move around in the layers bar. So I think this behavior will stay.

  • You do not have permission to view this post

  • ranma, I'm confused, what about the "Error: this.xa.hq is not extensible"? Where does that occur?

  • dre38w that link does not work here, did you put it in the 'Public' folder? If not it's private and only you can access it.

  • ranma your exported project works fine here, what are the repro steps?

    It might be worth making a new thread if it's a separate bug, since this thread is already a bit confusing with different issues.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hmm, looks like a bug in IE9 since it works in other browsers. I found a fix though, should work in the next build.

  • Is this new to r79? If the game freezes, check for browser errors - are there any? If you can it's extremely helpful to have a .capx or at least an exported project online which has the issue so we can check it out ourselves.

  • Sorry for the trouble everyone. However, please read How to report bugs and always follow the guidelines - the original post ("C2 wont run my projects") is not a useful bug report, the first thing I did was export the Physics demo and it worked fine. I believe the real issue is this one where if you don't have a jump-thru object in the layout the Platform movement hangs, which is to do with the fix to the jump-thru behavior in the changelog for r79. If you can't wait, you can download a fixed runtime.js for the platform movement here, or just go back to using an old release (that's why they're there!). Unfortunately being a small team we can't afford a whole test lab to extensively verify every build before it goes out, so sometimes these things sometimes slip through the net and get released. If you are concerned about breaks in future you can simply wait a few days after a new release to make sure it's OK for production use. We've also been meaning to formally split releases in to stable and testing branches, but having a million things on our todo list and new features regularly being asked for, it's one of many things that's not quite done yet I'm afraid! But I think this case means it should be a new priority to get that branching sorted out.

    I'm also going to have a look at the other new bug reports, hopefully it will just be straightforward to get fixed and release an update soon. Sorry again for the trouble and I hope r78 can tide you over in the mean time!

  • You do not have permission to view this post