Search Issue Tracker
Won't Fix
Votes
0
Found in
2022.2.0a17
Issue ID
UUM-6991
Regression
No
[NavMesh] NavMeshSurface cannot be referenced in Editor or Script
1. Open the attached project "internal_tower_defense.zip"
2. Open the "Main Scene" under "\Assets\Scenes"
3. Select "Manager" GameObject
4. Try to attach "NavMesh Surface" GameObject to "Manager" "Nav Mesh" field
4 (Alternative). Open the Manager script and attach the "NavMesh Surface" GameObject component to "Manager" "Nav Mesh" field
Expected results: NavMeshSurface can be referenced in Editor or Script
Actual results: NavMeshSurface cannot be referenced in Editor or Script
Reproducible on: 2019.4.40f1, 2020.3.36f1, 2021.3.5f1, 2022.1.6f1, 2022.2.0a17
Comments (1)
-
ststrohe
Jan 25, 2023 12:00
I wanted to use the Navmesh Surface component of the "NavMeshComponents" GitHub Folder. I had the same problem because the AI Navigation package was installed on my Project via Packed Manager and Unity wanted to use this component. Removing the AI Navigation package fixed it for me.
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
This issue is caused by the usage of both NavMeshComponent experimental project and AI Navigation package. One of the 2 systems need to be uninstalled to work properly.