Problems with loading symbols on Mac Studio
Hello. Since getting this mac for work I've had problems getting vscode to work right in Unity. It doesn't seem to know about a bunch of scripts it should so intellisense struggles and some scripts outline is simply empty. When I load up vs with the project, I can see the correct highlighting for a second, before it then corrects and isn't attached to unity at all. It also asks me about two different workspaces, which seem to change nothing.
I think this comes from a botched attempt at installing dotnet and further confusion caused problems trying to fix that (I'm not used to mac, yet alone the differences running on the new silicone). In the end I got it working on a test project, but not the actual long existing project I'm working with, and so gave up and worked with other tools just to keep moving. I can't do that now though so need to get this fixed and am lost with it.
My current thought is to try reinstall all my dotnet installs (since I know some aren't supposed to be there), but the uninstall tool isn't working. I download the tar.gz, run the given command, it shows me the help for the tool, then trying to run anything fails to find the command. Since it's been a while since last messing with this that's about as far as I remember what to try do. I know I already tried reinstalling vscode last time and that made no difference.
Any ideas are appreciated since this is now a major obstacle to my work. Thanks.
2 Replies
The Mac experience is going to suffer for a while, as VS for Mac is going away and VS Code doesn't catch up easily. Not only for Unity, but also for .NET and MAUI. Bug reports are welcome at https://github.com/microsoft/vscode-dotnettools/issues You might consider third party tools but they also have their own issues.
GitHub
Issues · microsoft/vscode-dotnettools
This is a feedback repository to capture issues logged for the C# Dev Kit and related extensions from Visual Studio Code - Issues · microsoft/vscode-dotnettools
Just an update, I kept messing around with disabling things and regenerating things. On my old little test project (of the same unity version) it would say it can't find .NET, and after making sure all my dotnet installs look right, environment path to DOTNET_ROOT included, I restarted my PC. Reopened it, let it do some stuff, and then it started working. I opened the main project - which is much bigger, older, and comes from other team members - and it's still no different. I have no idea what this means for where the problem is but at least it means it can work.