Search Issue Tracker
Fixed in 2017.3.0f3
Votes
0
Found in
2017.3.0a3
Issue ID
940269
Regression
Yes
Individual installers unnecessarily detect and show a warning about Visual Studio 2017 running
Steps to reproduce:
1. Create a new Unity Project
2. Create a new script and open it in Visual Studio 2017
3. Go back to he Editor and open Build settings
4. Download an installer for a Build target(e.g. WebGL)
5. Run the installer
Expected result: the installer warns the user about Unity versions running
Actual result: installer also warns the user that Visual Studio is running, which should only happen if you want to install VS along with the main Downloads Assistant
Reproduced on 5.6.0f2, 5.6.3f1, 2017.1.0p3, 2017.2.0b6, 2017.1.0a3 individual installers(Build targets or Editor installers)
Not reprodudeced with 5.5.4p2, 5.6.0b1 or regular Download Assistant across any versions
Verified FIXED 2017.3.0a6
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- DisplayDialogComplex crashes with a long content string containg Cyrillic chars
- "Draw Additional Lights Shadowmap" calls increase when custom MaterialBlockProperty is used
- Crash on _platform_memmove when importing the "Dragon Crashers - URP 2D Sample Project" to a new 2D project
- "Shader is not supported on this GPU" warnings and and shaders are not loading when building the project for non-Chromium browsers
- [iOS][URP] The screen flickers and the "Execution of the command buffer was aborted due to an error during execution" error is thrown continuously
Add comment