collision events not firing / no collisions

[dgpark...@gmail.com]

Hey guys,

I'm trying to simply recreate the breakout demo on my own using typescript and for some reason I can't get any of the collisions to work.

I've just got the ball and the paddle right now and no matter what I try I can't seem to get it to bounce off the paddle.

All the event handlers seem to be registering properly (confirmed by inspecting the eventDispatcher object) also the lose condition and the side bounces behave as expected.

I've pretty much read through the entire "I just want groceries" code and have tried to replicate how you guys are doing it in there at one point but it had no effect.

Any help in getting this resolved is greatly appreciated, this is really starting to bum me out :(

repo link: https://github.com/dgparker/excaliburjs-breakout

Thanks,

Dylan

[Kamran Ayub]

Have you enabled active collisions? By default collisions are passive. Passive throws events but doesn't react.

--
You received this message because you are subscribed to the Google Groups "excaliburjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to excaliburjs...@googlegroups.com.
To post to this group, send email to excal...@googlegroups.com.
Visit this group at https://groups.google.com/group/excaliburjs.
To view this discussion on the web visit https://groups.google.com/d/msgid/excaliburjs/61564cc2-11e0-49ff-b286-fec82cbf1c31%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[dgpark...@gmail.com]

Not sure what happened to my last response it's saying it got deleted for some reason.

But yes I have tried setting the collision types to active but it doesn't appear to change the behavior.

[Erik Onarheim]

Hi Dylan,

I took a look at this last night and I think I have a work-around for you. There is definitely a bug in excalibur here I've opened 2 issues:

 * https://github.com/excaliburjs/Excalibur/issues/948

 * https://github.com/excaliburjs/Excalibur/issues/949

The main issue is that excalibur calculates the default geometry for the box collision area in the ex.Actor super constructor, unfortunately it does not get automatically recalculated when the dimensions change.  

The workaround is to supply those (x, y, width, height) to the super constructor

class Paddle extends ex.Actor {
   public game: ex.Engine;
   constructor(game: ex.Engine) {
     super({
        x: game.drawWidth / 2,
        y: game.drawHeight - 40,
        width: 200,
        height: 20
     });
   //   this.game = game;
   //   this.setWidth(200);
   //   this.setHeight(20);
   //   this.x = this.game.drawWidth / 2;
   //   this.y = this.game.drawHeight - 40;
     this.color = ex.Color.Chartreuse;
 
     this.collisionType = ex.CollisionType.Fixed;
 
     this.addInputListener();
   }
  ..
}

The second issue I noticed was that the ball left the screen and didn't fire the offscreen exitviewport event at the right time (this happens on my laptop because I have a hidpi screen and the offscreen logic is incorrectly accounting for hidpi devices that multiply canvas resolution). 

The workaround for this is instead of using the 'exitviewport' event use the post updated to check the cooridinates

this.on('postupdate', (e) => {
  if(this.pos.x < 0 || this.pos.y < 0 || this.pos.x > this.game.drawWidth || this.pos.y > this.game.drawHeight) {
     alert('You lose!');
  }
});

Hope this helps.

These 2 bugs are relatively easy to fix, I'll try to get them into the v0.16.0 release that's going out sometime this week.

Let me know if there are more issues,

Erik

[Erik Onarheim]

Google groups is marking some messages as spam for some odd reason, must be why some were deleted. Feel free to ping me on other channels too if this continues, I've found a way to whitelist authors so fingers crossed.

On Tue, Apr 3, 2018 at 7:06 AM <dgpark...@gmail.com> wrote:

Yes, I've tried setting both the paddle and the ball to active but that doesn't appear to change any of the behavior or raise any collision events. 

Currently it's setup the same way as the breakout getting started project where the paddle is collisiontype fixed and the ball is passive but you handle the collision by registering an event handler on the precollision event.

--

You received this message because you are subscribed to the Google Groups "excaliburjs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to excaliburjs...@googlegroups.com.
To post to this group, send email to excal...@googlegroups.com.
Visit this group at https://groups.google.com/group/excaliburjs.

To view this discussion on the web visit https://groups.google.com/d/msgid/excaliburjs/32afe5e4-37f6-4114-9491-e4315dd6266c%40googlegroups.com.

[Erik Onarheim]

We released v0.16.0 last night, geometry recalculation didn't make the cut in time. I'll be our first priority in v0.17.0

[dgpark...@gmail.com]

Awesome i'll upgrade tonight then. No worries, the work around right now isn't all that bad. Once I'm finished I'll post the working version up on github and pages so you'll have a decent typescript beginner tutorial that's up to date.