You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Minor issue, but thought I'd document it as I noticed it.
The "Network" class was for Unity's old multiplayer system. It is still included for legacy reasons on platforms like Windows, Mac, Android, etc. But it is not included on the newer "Windows Store" build target for Windows 8.1 or Windows 10
The line in question is #21:
serverString+="Hosting at "+Network.player.ipAddress+"\n";
I tried searching around, but I didn't see an easy/direct replacement for getting the current device's actual local IP address (rather than something less useful like "localhost")
Luckily, since this is just debug information, I commented out the line and now things seem to be working nicely for Windows Store builds.
May be worth trying to find an alternate method to get the local IP in order to allow for maximum cross platform compatibility. Also because Network is deprecated, it may be removed in future versions.
The text was updated successfully, but these errors were encountered:
Minor issue, but thought I'd document it as I noticed it.
The "Network" class was for Unity's old multiplayer system. It is still included for legacy reasons on platforms like Windows, Mac, Android, etc. But it is not included on the newer "Windows Store" build target for Windows 8.1 or Windows 10
The line in question is #21:
I tried searching around, but I didn't see an easy/direct replacement for getting the current device's actual local IP address (rather than something less useful like "localhost")
Luckily, since this is just debug information, I commented out the line and now things seem to be working nicely for Windows Store builds.
May be worth trying to find an alternate method to get the local IP in order to allow for maximum cross platform compatibility. Also because Network is deprecated, it may be removed in future versions.
The text was updated successfully, but these errors were encountered: