J4G Posted July 19, 2015 Share Posted July 19, 2015 I have a tile-based world around 10,000 tiles big. Each tile has a static physics body that needs to interact with bullets of varying shapes as well as a rectangular player. In theory I could get by with just rectangular and circular hitboxes (so Arcade is out of the question), but Ninja is deprecated so I'm not really interested in using it. Right now I'm sitting at around 5 ms of P2 processing time, which is impressive but still too heavy for my use case (I'm developing on a pretty good computer). I've tried various techniques of optimization, including destroying off-screen sprites, but that operation is pretty expensive. I'm not sure if the problems I'm encountering can be resolved by using a library other than P2, or if it's just an impossible problem due to the amount of computation required. I'd love to hear some input on this from others. Link to comment Share on other sites More sharing options...
substandardgaussian Posted July 20, 2015 Share Posted July 20, 2015 It's really tough to say much about optimizing, since it depends so heavily on your specific implementation details. If you absolutely must have such a large world and you don't want to be destroying sprites (or p2 bodies), have you considered setting the shapes in bodies that are offscreen into sensors? They won't trigger collisions, so if you didn't attach any contact events to them they effectively become immaterial to P2. Are you using impact events? If you are, you can try disabling them and instead use contact events to process collisions. Other than that though, P2 is pretty expensive since it's so general. I wouldn't rule out Ninja entirely to be honest, it's built for speed. AABB vs. AABB collisions will be present in Phaser 2.4, so of the "basic" collision types it would only really be missing AABB vs. Circle collisions. If your circles will mostly impact tiles or you can get by checking for overlap instead of a proper collision (eg. for bullets), maybe Ninja would be right for you. Or, heck, maybe implementing AABB vs. Circle collisions in Ninja will prove to be faster and better for your application than trying to squeeze more performance out of P2. J4G 1 Link to comment Share on other sites More sharing options...
J4G Posted July 20, 2015 Author Share Posted July 20, 2015 I don't think P2 has support for sensors, or it's not in the documentation. I'd be fine with destroying bodies expect it seems to be a pretty computationally expensive operation. Link to comment Share on other sites More sharing options...
wayfinder Posted July 20, 2015 Share Posted July 20, 2015 p2 does have sensors. it's a property of shapes J4G 1 Link to comment Share on other sites More sharing options...
Recommended Posts