Search Issue Tracker
Fixed in 2019.3.X
Votes
24
Found in
2019.3.12f1
Issue ID
1243277
Regression
Yes
ReferenceOutputAssembly key is set to false in project references
Steps:
1. Set External Tools to Visual Studio 2017 in Unity Editor
2. Open attached project
3. Double-click on any script in Assets -> Examples -> Scripts folder
4. In the Visual Studio 2017 solution Expand NavMeshComponents project
5. Double-click on NavMeshAssetManager.cs
6. => Studio highlights the types it cannot find in red
Reproducible with: 2019.3.12f1
Not reproducible with: 2018.4.22f1, 2019.3.11f1, 2020.1.0a1, 2020.1.0b8, 2020.2.0a9
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
- Crash on mdb_xcursor_init1 when opening a specific project
- HDRP Decal Projector uses “Default” layer as main layer in “Rendering Layer Mask” instead of “Decal Layer Default”
- Cameras Overlay menu has unnecessary empty space at the bottom
- Sprite Atlas Asset UI issues
- Palette Settings link to the documentation isn’t working
Resolution Note (fix version 2019.3):
Fixed in 2019.3.13f1