I’m sure it did not used to be this bad but you attach the debugger in Visual Studio (Windows) and the editor is locked up (with overlay messages…) for 30 seconds or so and this is on a high end PC! (big project though)
So what is the editor doing for so long when the Visual Studio debugger is attached and is this quicker with other IDEs, is it a VS related issue or the unity editor is just really slow at doing something?
It can be a number of factors. The first is that Unity itself now defaults to running in release mode rather than debug mode, which is great! If you are trying to debug for the first time since opening Unity it likely has to switch over to debug mode, recompile, and reload all domains. This should only hapen the first time during that session though.
I’ve also noticed Visual Studio in particular lately is obnoxiously slow and its remote debugging with Unity is even worse. If you are running VS 2022 you really need to have a super high end machine or you need to disable all thr AI crap that it is running most of the time in the background. How to do that in totality is a pretty large task in-and-of itself but you can start by going in to VS’s options and disabling all of the Intellicode stuff. It’s disable all the fancy auto-guess-what-you-want-to-type but forbme personally that usually just slowed me down anyway.
As an alternative you could just try something like VS Code. I personally can’t stand it since it lacks basic support for customizing code formatting and its auto-complete is just about the worst thing I’ve ever had to work around. But if you can deal with that then you’ll generally find a much snappier experience all around.