Search Issue Tracker
By Design
Votes
0
Found in
5.5.0a1
Issue ID
780291
Regression
No
[VS] Searching in documentation in VS2015 leads to Online docs, but concrete look-up leads to local docs
Searching in documentation in VS2015 leads to Online docs, but concrete look-up leads to local docs
To repro:
0. VS2015 is set as default editor.
1. Open attached project and open ColorizeBell script.
2. Select, e.g. SpriteRenderer.
3. Press Help -> Unity API Reference.
4. Note: UnityFolder/Editor\Data\Documentation\en\ScriptReference\SpriteRenderer.html is opened in VS2015.
5. Return to script and select List.
6. Press Help -> Unity API Reference.
7. Note: http://docs.unity3d.com/ScriptReference/30_search.html?q=List is opened in VS2015.
Actual result: Behaviour is inconsistent within the product -> similar operations give different results.
Expected results:
If offline docs are installed - VS2015 should open them in any case.
If offline docs are not installed - VS2015 should open online docs in any case.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Add comment