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. 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. I built and ran a Windows build of my game waiting on the settings window.

Unity player windows 10