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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Add comment