The A* algorithm won’t figure out where you placed physics objects, it will only work its way around objects that your explicitly stated it can’t go through. For example 1’s in your array will represent areas it can’t use and 0 would be areas where it can find a path. Have you set up your array correctly to show the algorithm where the obstacles are?
Attaching physics bodies your moving with A* works fine and i’ve got a fully working tower defense game using it, if thats what you meant.
Also, before you go much further with A* you need to know that it can lag horribly with lots of enemies on the screen if you have to keep on recalculating there paths. I was going to release my A* tower defense game as a template, but when i tested it on device with lots of enemies on the screen the performance was pretty bad. That doesn’t mean it can’t be done efficiently, it just means that i obviously didn’t lol. [import]uid: 69826 topic_id: 34839 reply_id: 138458[/import]