Search Issue Tracker
Fixed in 2018.3
Fixed in 2017.4, 2018.2
Votes
4
Found in
2017.1.0f3
Issue ID
944759
Regression
Yes
Assertion failed on expression: 'verts.size() > 0" is shown when NavMeshObstacle has Carve enabled
To reproduce:
1. Open the project, attached by the user (NAVMESH ASSERTION.zip)
2. Open "test" scene
3. Enter Play mode
4. Observe the Console output
Expected: no assertions are shown when NavMeshObstacle has Carve enabled
Reproduced in 2017.1.0f2, 2017.1.0f3, 2017.1.0p5, 2017.2.0b9, 2017.3.0a6
Did not reproduce in 5.6.3p1, 2017.1.0f1
Could not reproduce in 5.5 due to some errors in the console
Fixed in: 2018.3.0a10, 2018.2.9f1, 2017.4.14f1
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Scene View] Gizmos dropdown disappears while toggling Windzone checkbox with its tooltip open
- Crash in StackAllocator::TryDeallocate when calling ParticleSystemRenderer.BakeMesh
- Modifying scoped registries in project manifest does not update Package Manager UI window
- Models change their position in scene when upgrading project
- Texture 'Read/Write' option does not double the memory in Profiler
monsterbluesHome
Jun 17, 2019 04:47
This was also fixed in 2017.4.14f1
amirna2
Aug 26, 2018 00:01
It started happening for me as well after upgrade from 2018.2.5. I have absolutely no idea why and definitely this either should be fixed if it is an error in the Engine or the assert removed as it doesn't affect game play whatsoever.
Xepherys
Mar 10, 2018 19:57
Additionally, this issue is still present in 2018.1b.
Khyrid
Jan 20, 2018 07:50
This is the only place on google that the " Assertion failed: Assertion failed on expression: 'verts.size() > 0' " error is mentioned and there is no answer.
This is really annoying, is there at least a way to disable the errors?
So far I have to disable all the navmeshes in my level one by one until I find if it is causing an error. Then if I change it around a little, the error goes away.
I should not be bothered by these errors, they do no affect the game in any way. Please Unity disable these errors from showing up. Forget the cause of them.
Xepherys
Sep 17, 2017 19:08
I also began seeing this exception when I applied multiple NavMeshes to a scene (one each for multiple agents).