It has been at least since 4.15 and when I installed VS 2017. Every time I open a Visual Studio from UE4, that label appears and does not want to go away. Ever.
Annoying. The way I get around it is just to load VS2017 first with the project…yeah, silly, but I hate when that happens. Although, I’ve not noticed it as much now that I’ve been on 4.17.2…??
I’m having it in 4.17.2
I upgraded my project to 4.18 and upgraded my Visual Studio from 2015 to 2017 and now I have this bug too. So it still exists in 4.18.
I have this issue too in 4.18. Didn’t have it in 4.17.
The same thing happens to me like ItBurn. In 4.17 works fine, but in 4.18 the label stays a long time.
Also: When finally open Visual Studio, UE opens a second instance of VS.
Same begun with 4.18 and VS 2017 both.
I am having the same issue. It started when I updated from 4.17 to 4.18.0. It opens Visual Studio fine, but it doesn’t seem to “connect” to it. Building in VS2017 doesn’t hot reload in the editor. Compiling in the editor doesn’t save the changes made in VS2017, and so doesn’t compile them. I’ve tried repairing Visual Studio, running the editor and Visual Studio in administrator mode, but nothing helps. It seems to be a bug in the editor. This is what the log tells me:
LogVSAccessor: Warning: Visual Studio is open but could not be queried - it may be blocked by a modal operation
LogVSAccessor: Warning: Couldn’t access Visual Studio
LogVSAccessor: Warning: Couldn’t access module table
The same is happening to me, but sometimes, Unreal opens other IDe that i have: sublime or visual studio code. It is very annoying
Happens here too.
Eventually, It will load a VSCode instance also, and then another vs2017. One of the guys on discord said he’d made a fix but hadnt m,ade a PR for it as wanted to explore the problem some more. I’m not using the source build as it didnt solve my initial issues of ■■■■ intellisense.
Eventually, the loading toast goes away.
Also spams “LogVSAccessor: Warning: Couldn’t access module table” once its failed to do its job properly.
Just commenting here to say that RaichuBender described the exact same problem I’m experiencing perfectly. These issues started occurring after “upgrading” (yeah right) to 4.18 from 4.14 and do not go away when reverting to 4.14. I wish I never would’ve tried this 4.18 garbage. They completely broke UE4 and I can’t believe that the turnaround on a fix for an issue of this severity is so slow.
I’m trying a few more fixes of my own before throwing in the towel and switching engines entirely. Will report back if I figure anything out.
Edit (copied from a similar post of mine): So many different attempts at this and I think I got it working. Sorry for my cranky post, I was scheduled for a biopsy today, plus my livelihood depends on this engine working. Now that I’m back from the doctor, I had a little bit more of a clear mind to finally figure it out. Going to rest now (this problem has had me awake for over 24 hours), but I will come back and post step-by-step what I did to get UE4 functioning as intended! Sorry for the wait, but if you want to take a crack at it, it involved a fresh install of VS2017 (I was previously working with VS2015), deleting Intermediate Saved and Binary folders as well as the solution file .sln (copy them off somewhere else & create system restore before making changes!), giving admin privileges to both UE4 and VS, and rebuilding/regenerating everything. That’s as much as I have in me for now, but I will retrace my exact steps when I come back to this post. Ben the instructor’s answer at this link "Could not be compiled. Try rebuilding from source manually." - #3 by VytautasR - Ask - GameDev.tv was a good guideline and helped fix most of my major synchronization issues (haven’t tested the minor ones yet e.g. the original toast problem; will report back)
Edit2: Ok, I have a little bit of fight left in me to test the toast issue. Currently 30 min & still hasn’t vanished. Will update if it changes within another 30.
Sorry for double post. If any of you are also affected by this issue, please vote at Unreal Engine Issues and Bug Tracker (UE-51608) so it can go up the bug priority list!
Edit1 continued: I also changed the editor preferences to VS2017 after the install, but you guys probably already know that.
A little helpful workflow tip from Gamzie1 on reddit:
It’s only happened since 4.18 - I’ve
just coped with it tbh. My way of
working when I get to my PC is open
the vs project first and launch the
debug editor target with ctrl + F5
(launches without attaching debugger)
then I make sure this is the instance
of VS I use. Every time it opens a new
process for VS I just close it (the
one unreal opened) down. it sticks
saying “opening VS” in the bottom
right hand corner of the editor for a
little while but does eventually go
away.
Update 2: It has now been an hour and a half and the toast label is still stuck on “Loading…”
Shutting it down and going to bed.
cool solution!
BTW, it appears that the issue is fixed in 4.19 Unreal Engine Issues and Bug Tracker (UE-51608)
I’m still using an older version of Unreal on a custom built version (4.16.1), but the way I’ve been able to workaround this (somewhat) is the following:
- Open up my Unreal project
- Click on a C++ file to open Visual Studio
- Wait a moment, then close Unreal
- Leaving the Visual Studio instance opened earlier open, reopen your Unreal project
- Click on a C++ file in Unreal. You should see that it went straight to the earlier opened instance and the two are on the same page (finally!)
Report it as a bug.
This was already done (see Ke9an’s comment from Nov. 15 2017)
Edit: including link to reported bug Unreal Engine Issues and Bug Tracker (UE-51608)
Its marked as fixed but its not. I’m still having this problem.
This is still happening to me in 4.19 preview.