Debugging Unity 3D with VSCode
Debugging Unity 3D with VSCode
How to debug Unity 3D using Microsoft's VSCode code editor tool.
Join the DZone community and get the full member experience.Join For Free
Bugsnag monitors application stability, so you can make data-driven decisions on whether you should be building new features, or fixing bugs. Learn more.
I’ve written several articles on the use of VSCode with Unity through its evolution but time and tide waits for no man as the behemoth of technology marches on.
If you’ve not heard of Microsoft’s new multi-platform lightweight code editor before, go and check out its homepage (https://code.visualstudio.com/), it’s chock full of fantastic stuff to make you drop MonoDevelop or any other lightweight editor. You can also check out my previous articles here and here.
Microsoft VSCode has taken many great strides since last I donned my writing hat, most notably:
- It’s now completely open sourced! — Check it out on GitHub here (https://github.com/Microsoft/vscode)
- A new extension system has been added, allowing community devs to write plug-ins and language extensions to the editor without rebuilding it.
- Debugging support for web apps has improved greatly.
- Git and source control support has been improved.
There is a lot more but these are my favorite highlights. If you have read my previous articles on the subject (here and here), you will also know that it has some great support for Unity, which has only gotten better now that Unity themselves have pulled in to the race:
The Story So Far
Since the early beta releases we’ve been able to configure VSCode manually as a code editor within Unity, slowly but surely through the beta phases this integration has been improved to add file and line support when calling VSCode.
Back in Version 0.8.0, this took another bold leap forward with the first Unity asset (well, the only really) aimed at providing increased integration between these two products.
Made by a community developer and with some assistance between the Unity and Microsoft teams, they automated a lot of the menial setup required to make the most out of the integration, namely:
- Support for Windows, Mac and eventually Linux.
- Streamlining Editor preferences setup.
- Setting the necessary command-line arguments when starting VSCode, which improved as VSCode did.
- Creating the nessasary workspace settings to improve the VSCode UI when launched from Unity.
- Updating the project files to be more Unity/VSCode compatible.
- Debugging support for MacOS.
VSCode Editor Screen
Plus a host of other little tidy up / backend tweaks needed to ensure it all worked seamlessly.
Before and After Workspace configuration in VSCode
The only real limitation in its use was that debugging was only supported on a Mac (granted Mac owners didn’t see this as an issue ), UNTIL NOW!!
Let Me Stop You There
The train never stops when it comes to technology (even Cobol still lives!, granted Flash and Silverlight are headed to the graveyard), especially when a project becomes opensource but is still heavily contributed by the project originators, which in this case is Microsoft. They are certainly on a mission to make the fastest and most powerful cross platform editor out there.
Recently Unity Technologies themselves also wrote an extension for VSCode to allow debugging of Unity projects from more platforms:
With this extension installed you can now simply attach your VSCode project to Unity in a very similar way to what is possible already with the Visual Studio Tools for Unity with Microsoft Visual Studio (which also replaced the default code editor on Windows and is now bundled with Unity).
This includes such support as:
- Better intellisense
- More code completion and language support for MonoBehaviours
- Editor attaching
- Breakpoint support for the Editor and platforms
Unity have also made the extension itself opensource on Github (like so many of their other new initiatives, the UI and 2D updates to name a few), so if there is something you feel is missing or could be done better, you can either build your own or submit a pull request and send it to Unity to add.
Getting Set Up
Enough talk, let’s get this up and running in a few short steps, it’s easy enough but the information is slightly scattered throughout the interwebs and pages.
The short path to get this running is as follows:
- Install Unity (But let’s assume you have done this already)
- Install VSCode — Download it from http://code.visualstudio.com for your OS
- Open your Unity project.
- Download the VSCode asset from dotBunny from the Asset Window (or import the asset if you have downloaded it manually).
- Open the Editor preferences using the Edit –> Preferences option in the Unity editor menu.
- Click on the VSCode tab on the left and check “Enable Integration”.
- Click the “Write Workspace Settings” button (only needs to be done once per project), this will create the VSCode default workspace configuration for Unity.
- Open VSCode for your project by opening a code file (you can do this manually but you will then have to manually select the unity project folder).
- When VSCode is open hit the F1 key (this opens the VSCode Command window shown below)*Note, you will need an internet connection for this part!
- Type the command “ext install” in to the command window and select the option “Extensions: Install Extension”.
- This will display all the available extensions on the VSCode marketplace (there are a lot aren’t there!), to filter the list simply append filter criteria to the command so that it reads “ext install unity”.
- Now simply click on this extension and it will be installed in the background. When it’s done you will receive a notification to restart VS Code.
Almost there, we now have all the necessary components installed, however to enable debugging, there is one final step.
- Click on the Debugging icon in the toolbar on the left hand side of the editor (this shockingly bring up the debugging view).
- Then click on the cog icon to bring up the debugger selection.
- Finally select “Unity Debugger” from the list to enable it.
If all goes well you should see a new “Launch.json” configuration file in the viewer showing you the current debugging options available.
If anything goes wrong or it doesn’t look right, then simply return to the folder/files view (top left folder icon) and delete the Launch.json file, then repeat the above steps which will recreate it.
You should be able to determine from looking at the default launch configuration that it only supports the Editor by default, however you can extend this to support projects too if you wish, just check the marketplace support page for more detail — https://marketplace.visualstudio.com/items/Unity.unity-debug
All done, if you return to the Folder/File view you can set breakpoints as you would do in any other code debugger and have VSCode break on that line when it’s hit.
Let’s see it in action:
I don’t think this is the end for VSCode’s integration with Unity, especially not with everything being opensource, so the future is looking very bright for Unity developers!
Published at DZone with permission of Simon Jackson , DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.