Jordan Cassady
1 min readAug 1, 2020

--

Debugger for Unity: add missing launch.json for VS Code

Unity’s debugger extension for VS Code needs a .vscode/launch.json config.

After installing the Debugger for Unity extension for VS Code, it became apparent I would need to add a launch.json file to my project’s .vscode directory, since the extension wasn’t able to handle the install on my behalf. I believe this was because I had installed and ran the extension after opening my C# script directly from the Unity Editor, and therefore VS Code wasn’t able to locate my .vscode settings directory. I’m not completely sure.

Over on the debugger’s github page, I found issue #101 where a user posted a copy of the default launch.json while troubleshooting a similar issue. The below launch.json can be copied into your project’s .vscode directory if it’s missing for you as well:

# .vscode/launch.json
{
"version": "0.2.0",
"configurations": [
{
"name": "Unity Editor",
"type": "unity",
"request": "launch"
},
{
"name": "Windows Player",
"type": "unity",
"request": "launch"
},
{
"name": "OSX Player",
"type": "unity",
"request": "launch"
},
{
"name": "Linux Player",
"type": "unity",
"request": "launch"
},
{
"name": "iOS Player",
"type": "unity",
"request": "launch"
},
{
"name": "Android Player",
"type": "unity",
"request": "launch"
}
]
}

--

--