koobas.hobune.stream
Why does Play In Editor close my currently Running Standalone Copy
I am currently trying to test networking functionality in a prototype for a client. I also just changed my Operating System.
I was running Unity 5.5.0f3 on Win7 Home Premium this morning and I loaded up the project. I was able to successfully build and run a standalone version of the App. While this standalone version was running, I pressed the Play button in the Unity editor to get another game client running so that my play in editor (PIE) client and my standalone client could connect with each other. I was able to successfully do this, and I have been able to follow this process exactly for the past two weeks to successfully test my multiplayer functionality.
After upgrading to Windows 10 and reinstalling Unity 5.5.0f3 this afternoon, I am running into a problem where if I start a standalone instance of the project and subsequently press the Play button, then my standalone instance of the project simply stops running. There are no warning messages or any other notices; the standalone client's window simply closes, and then my editor launches the PIE client.
Conversely, if I am running a PIE instance, and then launch a copy of the standalone build, the PIE client stops (ie. The gameplay stops, and the play button switches from a blue highlight back to grey.)
I don't really know what other information to give that may be relevant, but does anyone else have an idea of why I can't seem to have a standalone instance of my App and a PIE version running at the same time?
Also discovered that attempting to open 2 copies of the standalone build results in the first copy being closed before the 2nd being open, so that doesn't work either.
