Destructible Components always effect nav mesh even when collision disabled
Expected result: when collision is disabled, the area should be marked as navigable.
This appears to be due to the following function:
In the constructor of DestructibleComponent, hasCustomNavigableGeometry is set:
This means that even if collision is disabled, the mesh will still be considered non-navigable. Is this intended?
I'm hesitant to change this flag as the comment for it is:
This doesn't mention anything about it's behaviour regarding IsNavigationRelevant.
Thanks, Isaac inbetweengames
asked Jan 06 '16 at 07:42 PM in Bug Reports
I was able to reproduce the navigation issue and have entered a bug report (UE-26121) for investigation.
answered Jan 27 '16 at 10:06 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here