Then, open Unity, select Edit/Preferences, hit “External tools” and from the drop down “External Script Editor” select “Visual Studio Code”. But please hear me out and go ahead, install Visual Studio Code. I have lived in it for a little short of two decades. Wait! Read on! Yes, I am partial to Visual Studio as well. I presume it works, but when you often need to test and deploy on a device (like me), you will need to change configuration often and this in itself will take time - and it will make the deploy to a device yet even longer than it already is. The first solution has been suggested to me by Edd Smith. Set Visual Studio Code to be your External Script Editor.Change the project setting to Windows Standalone, and only change it back when you need to build on a device.It’s maddening.īut there are ways to get around it. And all the while it’s doing that both Unity and Visual Studio itself are not responsive. Visual Studio asks you to reload the project, all 99 (or 101, depending on your settings) are unloaded and reloaded, you might even get some errors as extra. You might wait well over 15 seconds, especially with scripts. This has an unintended and very unwanted side effect: adding files to your solution becomes slow. Solution: Visual Studio 2019 and Unity 2019.4.x LTS are very slow when adding/changing filesĪlthough I like to stay at the minimum recommended version for the MRTK (currently 2018.4.20f1), for the app we are currently developing for my employer we need to target ARM64 and for that you need 2019.4.8f1 (until short, the latest LTS).
0 Comments
Leave a Reply. |