#Visual studio code unity debugger windows 10
#Visual studio code unity debugger windows

The problem is when trying to discover the players through multicast, one of the network adapter is throwing an exception (WSAENOPROTOOPT 10042) when setting the IP_ADD_MEMBERSHIP socket option.įor me this was Microsoft Wi-Fi Direct Virtual Adapter.

#Visual studio code unity debugger windows

The executable is with all permissions in Windows Firewall. Setting up multicast option: 225.0.0.222: 58997Įrror launching player connection discovery service: Unity player discovery will be unavailableĪn unknown, invalid, or unsupported option or level was specified in a getsockopt or setsockopt call Output of GetUnityPlayerConnections.exe (run as admin and user): The command 'netstat -ano' show this output for the Windows Player PID: Windows build process not listed, only EditorĮrror pop up: 'Could not find target error. With Ctrl+Shidt+P => Unity Attach Debugger The same thing may be true for Rider as they start by injecting a plugin dll into your project repository to enable their extension support to work.Ĭan't attach Windows Player build (64 bits neither 32 bits).

But I do also know that VSTU is injection libraries to support debug attaching in another way so maybe there is something they are doing that changes this behaviour. Which is causing my head to be very confused. Whether that is due to an error between the player and your firewall, seems unlikely as you are able to see the connection in Visual Studio. It is definitely something in the network layer which makes it much more difficult for me to fix. There is no internal errors happening that I can easily detect. But it is very clear to me that the connection between the Windows Player and the debugger extension is not working. 0.0.0.0:54997.īut I must say that I am getting more and more confused by this problem.

#Visual studio code unity debugger windows 10

If you run the command netstat -ano from your command prompt on windows 10 you should be able to see the process that have opened multicast connections i.e. These should be unblocked by the firewall. Your Environmentįor info the it is trying to set up a multicast connection on these 4 ports: 54997, 34997, 57997, 58997. opening the 'Select Unity Instance' window, then start the game, then come back to that window). My guess is that you re-use the same implementation in VS Code, but in VS Code we can't do the trick I mentioned above (i.e. If I start the game after I opened the 'Select Unity Instance' window, then the Windows Player appears in it and I can start to debug. If I start the game before to open the 'Select Unity Instance' window, then the Windows Player does not appear in it. I am not sure but in Visual Studio 2017 Community, when I do 'Debug > Attach Unity Debugger', a 'Select Unity Instance' window appears. When using 'Start Debugging' a dialog opens and tell us that:Ĭould not find target name 'Windows Player'. When using 'Unity Attach Debugger' the windows player is not suggested in the list. When using 'Unity Attach Debugger' or when using 'Start Debugging' with the option 'Windows Player', we would expect the debugger to successfully attach to the Windows build. Then open VSCode-UnityDebug.sln in Visual Studio.I built and ran a Windows build of my game waiting on the settings window. To build this repository, clone it then get all submodules: git clone In addition, evaluating the variable using the debugger console will reveal the same result. To view the entire value of this string add it to the watch fields. Strings in the variable view is truncated to 100 characters, with appended ellipsis. Select the Unity process you wish to attach the debugger to. Wait a bit for the Unity processes list to appear at the top of the VS Code window. In the command palette type 'Unity Attach Debugger' New in version 1.1.0 it is now possible to select which Unity process you want to attach to from a quick pick menu. Enter play mode in Unity and the breakpoint should hit in VS code. You can now debug your C# scripts in VS Code by setting a breakpoint in a C# script from your project, switching to the debug view and clicking the green triangle button to attach to Unity. vscode/Launch.json file in your Unity project folder and can select which Unity target you wish to debug. vscode/Launch.json file in your project that you must delete first. If you do not have Unity Debugger in the list, then you already have a.

In the drop down list select “Unity Debugger”.

Select the debug view on the left and click the cogwheel. Open your Unity project folder in the Visual Studio Code. Use Visual Studio Code to debug your Unity C# projects. This extension is not officially supported by Unity Technologies.

Unity Debugger Extension for Visual Studio Code