A few of us in the office have noticed recent problems with Unity and VS Code, and I’m just wondering if we’re alone or if other people have noticed the same thing.
The main problem is that Intellisense regularly breaks. It will work for a while, but invariably (sometimes minutes later, sometimes hours) ‘Go to Definition’ will just stop working, with the blue horizontal ‘working’ bar at the top just continually pulsing without any resolution. Closing Code and restarting it from the ‘Open C# project’ menu item in Unity usually fixes it, albeit temporarily.
The other issue is that opening a file by double-clicking on a compile error will almost always open an extra VS Code window, usually prompting a warning that the current open workspace will be closed.
These issues have been happening for a while now, and have persisted across different machines and through uninstall/reinstalls. Has anyone else seen anything similar? Is there somewhere better to post about this?
I also tried VS Code as an editor for Unity at different points in time since it came out, hoping for a smooth experience. I had some weird issues with VS Code not picking up classes in other scripts, and was getting a little annoyed with the multiple Code windows opening up when double clicking the console or double clicking scripts in the project tab as well. I did manage to figure out how not to make that happen which I’m not remembering now, but it required doing things in certain steps (or not doing certain things) that seemed too much of a hassle, and ended up going back to Visual Studio.
Hopefully one day these things will be sorted out and I’ll be able to use VS Code for editing any type of file without workarounds.
None of those problems on macOS - but apps only launch once there unless they have special flags for multiple instances. The only bug I see occasionally is that Unity will report the debug link is broken, even though I’m not actively using it. Some problems might be caused by the C# extension which is supported directly by Microsoft too, so try poking at their GitHub repos. I typically get quick responses when I do
