Skip to main content

Unity Multiplayer Networking pitfalls

So recently I need to find a way to get two Unity projects on different machines talking and sharing data. The data shared is nothing like multiplayer games, far from it, it was just a notification of an event flag that became true on one machine. So if a special event happens on one machine then the other machine will also know. This is just sending a string or an int as a flag, simple!

My first attempt was to use Unity's Unet Multiplayer Networking system. It looks easy enough to use right ? So I followed the Networking tutorial here. Turns out it was not as smooth as I'd hoped...

  • The server only works as standalone. So we need to build the application and run as standalone. Not a big problem, but for those who don't read the manuals (like me, hehe) this is the first obstacle. Just running on the Editor will not work.
  • However, it does not work between computers. I was running a mac and a windows machine and although they could see each other just fine (ping worked) the Unity projects could not talk to each other.
  • After many hours googling, I tried everything I found, disabling firewall, antivirus, tutorials, sample codes etc. It just didn't work.
During my search I saw many people posting the same thing, basically it doesn't work between different devices on a local network. I guess there must be something I did wrong somewhere but the documentations and tutorials do not cover multiple devices on LAN.

So the next thing I tried was to use the transport layer (LLAPI) as discussed in this post. I got it to work on the same PC, but not over the network. It turns out that in order to get it to work you need to connect the two devices to each other. In other words,  if you have devices on 192.168.2.10 and 192.168.2.12 you need to have 
connectionId = NetworkTransport.Connect(socketId, "192.168.2.10", remoteDevicePort, 0, out error);

on the machine with the IP 192.168.2.12 and conversely,
connectionId = NetworkTransport.Connect(socketId, "192.168.2.12", 4999, 0, out error);

on the machine with the IP 192.168.2.10.
Oh, and last but not least, the two devices need to run the same version of Unity. If the versions don't match, the connection may fail silently.

With the above setup, I managed to get two PCs on LAN to send messages back and forth as P2P.

Hope this post helps.

PS : The repository of this test project.

Comments

Post a Comment

Popular posts from this blog

Object detection with Google Colab and Tensorflow

This is just a memo of the challenges I faced when running a model training on Google Colab, while following a great tutorial here . Mind the versions Tensorflow is currently at version 2.2.0 but most tutorials are still using the contrib package, and there is no known easy way to update the code to remove dependency on contrib. So my best bet is to downgrade the tensorflow version to 1.x. Since Google Colab only gives the options of either 1.x or 2.x and we cannot specify the exact version, I ended up with version 1.15.2. Even with the command :  %tensorflow_version  1.15.0 I ended up with : 1.15.2 Another pitfall was the version of numpy. Installing numpy gives us the version 1.18.3 but for some reason this generates the error : TypeError: 'numpy.float64' object cannot be interpreted as an integer Downgrading numpy to version 1.17.4 solved this for me. It seems we don't need ngrok for tensorboard With the command :  %load_ext tensorboard W...
Post a Comment
Read more

Installing a custom ROM on Android (on the GT-N8013)

It's been a while since my last entry and since it is a new start in 2019, I thought I'd write something about "gone with the old and in with the new". I've had my Samsung Galaxy Note 10.1 (pnotewifi) since 2014, and it's one of the early Galaxy Note tablet series. It has served me well all this years but now it just sits there collecting dust. My old Samsung GT-N8013 I've known a long time about custom Android ROMs like CyanogenMod but has never had the motivation to try them out, until now ! Overview of the process For beginners like me, I didn't have an understanding of the installation process and so it looked complicated and it was one of the reasons I was put off in trying the custom ROM. I just want to say, it's not complicated at all!   Basically you will need to Prepare an SD card and install Android SDK (you need adb ). Install a custom boot loader ( TWRP is the de facto tool at the moment). Use adb to copy custom...
15 comments
Read more

Using FCM with the new HTTP v1 API and NodeJS

When trying to send FCM notifications I found out that Google has changed their API specifications. The legacy API still works but if you want to use the latest v1 API you need to make several changes. The list of changes is listed on their site so I won't be repeating them again but I'll just mention some of the things that caused some trial and error on my project. The official guide from Google is here : Official Migration Guide to v1 . The request must have a Body with the JSON containing the message data. Most importantly it needs to have "message" field which must contain the target of the notification. Usually this is a Topic, or Device IDs. Since my previous project was using GAS, my request had a field called "payload" instead of "body". Using the request from my previous project, my request in Node JS was as follows: request ({ url: 'https://fcm.googleapis.com/v1/projects/safe-door-278108/messages:send' , method: ...
Post a Comment
Read more