Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.1.0a5
Issue ID
1022131
Regression
Yes
Unresponsiveness due to reloading Visual Studio project
For larger projects this reload takes a long time (~20-30 seconds of unresponsiveness). The bug is easily noticeable when using Visual Studio on Windows, as the blue bar at the bottom will tell you that the project is reloading.
To reproduce with attached project:
1) Click Assets > Open C# Project to launch visual studio
2) Open 'SampleScene.unity' and enter playmode
3) Double click on error message in the console
4) Observe Visual Studio will Reload the Project
5) Exit Playmode + Enter Playmode
6) Click on error again
7) Notice Visual Studio will reload the project again DESPITE no code changes?
It appears that since ~2018.1.0b8 visual studio stopped giving the user the option to ignore a project reload, but would still want to do it. The project reload regression appears to have been initially introduced in 2018.1.0a5 - although here the reload will only occur after a number of attempts (can be over 5 repetitions of entering playmode / clicking on the error). From that version up the problem appears to have become progressively worse.
---
From the User:
VCProjects loaded from the Unity Package Manager are detected in Visual Studio 2017 are too frequenlty being marked for reloading. This process takes up to a few minutes and really impedes workflow because during this process Visual Studio is locked up. This has been happening on Unity 2018.1.0b11, 2018.1.0b12, 2018.1.0b13, and the special version 2018.1.0b12 for ECS testing.
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
- Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Aetherurgist
Jul 10, 2018 16:38
The reason for Won't Fix?
msfredb7
Jul 02, 2018 16:25
Oh ok, I found a thread with workarounds:
https://forum.unity.com/threads/issues-with-visual-studio-unity.514304/#post-3409391
msfredb7
Jul 02, 2018 16:19
Severity 3 means there's a workaround. So ? What is it ?
It would've been nice to have an explanation for the "won't fix"...
sier_ua
Jun 18, 2018 20:41
I'm experiencing the same problem.
RikuTheFuffs
May 30, 2018 09:58
I have the same problem, which is slowing down our workflow a lot. Is there any reason for the "won't fix"?
ewoutee
May 24, 2018 13:24
Why is this marked as wontfix without any explanation? I'm sure other people are having this issue.