Search Issue Tracker
By Design
Votes
0
Found in
5.4.0a5
Issue ID
752730
Regression
Yes
Baking NavMesh with 3d Colliders produces no visible results
Baking NavMesh with 3d Colliders produces no visible results
To reproduce:
1. Open attached project
2. Open 2DMesh.unity scene
3. Select Cylinder game object
4. Click Bake button on NavMeshSurface component
Expected result: A Visible nav mesh appears
Actual result: No nav mesh appears
Notes:
BackgroundSprite object has a 3D Collider which should be baked;
NavMesh Surface Component is set to FitToScene;
NavMesh Surface Component is set to Physics Collider geometry;
By design because: The component had Use Children Only enabled, which makes it so, that the component only looks for bakeable surfaces in it;'s children objects.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment