Search Issue Tracker
Fixed
Fixed in 1.1.7, 2.0.4
Votes
0
Found in [Package]
1.1.3
2.0.0
Issue ID
NAVB-39
Regression
No
Building NavMesh with NavMeshSurface does not bake areas into NavMeshTriangulation when BuildNavMesh() is called in Awake()
Reproduction steps:
1. Open the attached project “NavMeshAwake”
2. Open Scene “Assets/Scenes/Game.unity”
3. Open Script “Assets/Scripts/MultiNavMeshVisualizer.cs” and uncomment all commented lines
4. Enter the Play Mode
5. In the Hierarchy window, expand the “NavMesh Visualizers” GameObject
6. Select the “NavMesh Visualization” GameObject
7. In the Inspector, observe the number of materials attached to the selected GameObject
Expected result: GameObject contains 3 different materials
Actual result: GameObject has less than 3 materials
Reproducible with: 1.0.0-exp.4 (2021.3.27f1), 1.1.3 (2022.3.1f1, 2023.1.0b19, 2023.2.0a18), 2.0.0-pre.3 (2023.2.0a18)
Reproducible on: Windows 10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Texture Compression default texture format is set to PVRTC when building via script BuildPipeline.BuildPlayer
- [Android][GameActivity] APK built with Development Build enabled gets flagged as having Malware
- Default name of manually created Global Light 2D GameObject differs from the one included in the initial project Scene
- Option for "Acceleration Structure Build Flags" cannot be toggled when Lightmaps have been Generated for a Mesh Renderer
- Lights in Batch keep resetting to 0 in the Light Batching Debugger when a new GameObject is created and the mouse cursor is hovered over the Inspector window
Add comment