Fixed issue with incorrect navmesh query results. It was a problem with navmesh bounding box calculation. to merge one AABB to another, use bb.merge_with(), not bb.merge(), as thi later will return new AABB, while former will increase size of existing AABB. 
So now I'm going for navmesh visualization and adding agent signal sending (hope it will work with Spatial+script agent)

Comments

Post a Comment

Popular posts from this blog

Image
Finally I fixed all navmesh generation errors and can go continue with the rest of features. (Navmesh is drawn in green lines). Now I need to add area tagging and connections, i.e. I move to tile cache now. After that I need to restructure code a bit so that navmesh build code goes to navmesh class, so to be able to run independently of node tree. The code is in navigation branch, have fun.
Read more
Image
Finally made tiny little agents work. OMG how many bugs remain, but I do have some progress. Obvious bugs left: For some reason navigations work only in positive quadrent (+x, +y,+z) When higher obstacle is on the path, agents behave like it is small wall they can jump over. Looks like geometry is cut off, need to test this. First thing I need to do now is navmesh debug display, so I could debug thing like this. For the rest: UI integration of everything. API for all agent controls. Probably this comes above, Agent error handling, including removing/adding which is needed when velocity control is not enough. Implement all controls possible and non-physical agent. Physics based control will be implemented later (need to understand more things better for that  Implement distant path checks later, so targets beyond 256 polygons produce no errors. But for now 1000 agents and no FPS drop. YAY! Everything is in repository. The script you can use to test code: ex...
Read more