Yes, Brent is right; Though I was picturing something like multi-bodies or irregular shapes - Box2D has the ability to report the collision point as it obviously needs to calculate this information to do its job. It’s just that Corona doesn’t return it properly. [import]uid: 8271 topic_id: 32176 reply_id: 128333[/import]
Thank you both for the clarification regarding the impact point. That does seem essential to doing collision based physics!
That is interesting how deep the topic of platform collision is for such a staple of so many 2D games.
Without having attempted anything yet, I’m leaning towards an approach that checks whether (player.height + object.height)/2 >= object.y - player.y if player.y is less than (located above) object.y
I have made a nice top down 2D game prototype and may shift the focus of my effort back to that since I’ve also been grappling with how to best handle jumping in a platformer:
http://developer.coronalabs.com/forum/2012/10/22/approach-handling-player-movement-platformer-style-game
The challenge I have with my 2D game is that I’m using individual storyboard scenes for each “room” of my world and I get a small memory increase (~8kb) with each new scene I visit. Not a problem for 10 or 20 screens worth of gameplay but not do able for the 100 to 200 that I’d like to be able to use…
http://developer.coronalabs.com/forum/2012/10/20/storyboard-scenes-and-memory-use
[import]uid: 105707 topic_id: 32176 reply_id: 128337[/import]
Btw, you could also check the velocity of the player’s object - ie: if its moving up, let it pass through the platform, if it’s moving down, don’t. [import]uid: 8271 topic_id: 32176 reply_id: 128386[/import]