The navigation mesh build appears to ignore the 'Min Region Area' setting.
Bug: The navigation mesh build appears to ignore the 'Min Region Area' setting.
Steps to repeat:
You can experiment with other more reasonable settings for 'Min Regin Area', but there will be no effect on the NavMesh.
June 16 Edit
The above test case is not valid. I was able to get a dev environment set up, and debugging demonstrated two things: A very high MinRegionArea value results in an integer overflow, causing the value to be interpreted as zero. Also, a reasonable value of, say, 500 or 1000 does work as expected. There is an issue that still exhibits with a landscape I'm using, but that doesn't lend itself to easy steps to repeat.
I was able to reproduce this issue on our end. I have written up a report (UE-31960) and I have submitted it to the developers for further consideration. I will provide updates with any pertinent information as it becomes available. Thank you for your time and information.
Make it a great day
answered Jun 13 '16 at 06:05 PM
Rudy Q ♦♦ STAFF
Follow this question
Once you sign in you will be able to subscribe for any updates here