3 commits

Author	SHA1	Message	Date
elsid	05b54cbfb8	Cull navmesh objects by scene bounds ... If object is too big iteration over all tiles covering it can take too much time. Limit bounds to a square around a player position to cover only tiles that will be present in navmesh based on max tiles number option. Each object is associated with a set of tiles its present in. Culling can reduce this set but it has to be update when bounds change position. Do this in TileCachedRecastMeshManager::setBounds updating the set and adding/removing objects to the corresponding CachedRecastMeshManagers.	2022-02-03 22:09:37 +01:00
elsid	aaf6c82e33	Do not write shapes to navmeshdb when writing is disabled	2021-12-16 22:57:35 +01:00
elsid	96eb8d7be9	Write generated navmesh to navmeshdb ... Perform all request to db in a single thread to avoid blocking navmesh generator threads due to slow write operations. Write to db navmesh for all changes except update as it done for memory cache. Batch multiple db operations into a single transaction to speed up writing by not executing fsync after each insert/update query. All reads are performed in the same transaction so they see uncommited data.	2021-12-11 00:22:04 +01:00