Overlap events not working anymore after setting up nav agent radius
We have this huge project with different sized units, that are controlled by detour crowd controllers that get their movement orders by the player (RTS like gameplay).
We use nav mesh walking for the units and units are constantly getting stuck on edges because the agent radius on the character movement component was alwas -1 with disabled "UpdateNavAgentwithOwnersCollision". So why not checking this checkbox to use the capsule of the unit as agent size.
It worked - no more stuck units BUT the capsule is suddenly not detected by triggers (OnOverlapBegin and -End) anymore (which makes no sense to me). When I spawn a unit in the base (which also has a collision sphere) it fires overlapBegin and overlapEnd at the same time but is still in the sphere. Why? what am I doing wrong? I setup different SupportedAgents for different sized units in the NavSystem settings and only have one collider on each unit.
(When I change some settings and the unit is not connected to the nav mesh, the triggers suddenly work again)
Pretty sure I had the same type of problem. Try changing the collision settings on your units and on your walls. Make it so triggers act as something like "Destrucible" and set collision on your units to only overlap with "Destrucible" objects. This property setting should be easily editable and testable...this is how I made my overlapevents work with certain units, while ignoring other overlapevents of different units.
answered Sep 06 '16 at 04:51 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here