Jonathan Cornaz

Hi, Yes, the velocity should be calculated by the engine. You should be able to read that velocity if you want to. Are you saying it doesn't work, and the...

@Kerollmops would you mind sharing how to reproduce the behavior you observed?

Yes, that's something I had in mind as soon as I heard it would be possible with the new version of rapier. In theory it should be as beneficial for...

I also opened an issue in rapier: https://github.com/dimforge/rapier/issues/299 I mark this issue as "upstream" for now until we know if rapier agrees to address it. If rapier rejects the proposal,...

> I think this one is also could be resolved in Rapier. Is it worth mentioning this issue as well? that is kind of a different issue to me. But...

> Sure, the cause is different. I just assumed that grouping this two issues together may result in a better designed solution for events. I understand, and surely it is...

Thanks for the proposition. I think having aliases for creating 2d shapes might indeed be more user-friendly. But I am not so entousiast about having a different component type, because...

To be honest, I'm also wondering if it is not against the disign principle of "it should look like it is part of Bevy". After all, Bevy doesn't really have...

> Bevy's breakout example is in 2d, and uses Vec2 a lot, for sprites for instance. It also uses Vec3 with z set to 0, for transforms. That's not an...

Thanks for the feedback. What API and behavior would you prefer instead?