The first one is player 1 the second player 2, etc.Ģ. This works just fine because each device has a different NAT IP. The normal most common use case is that the same controller is deployed to many phones. Can you explain your usecase a little bit on why you'd want the same controls on seperate instances on the same machine? Currently, we support both of the usecases below but I want to hear a little more about your goal before I make an addition to the project.ġ. Since all 3 of your instances are on you mac they have the same LAN NAT address and are essentially 1 player (player 1 if this is a single player game). Easy WiFi Controller handles the connections for you automatically but it is IP based since that is the most logical for the majority of usecases (using each phone as a seperate controller). The Unity 4.6 version will then be mailed.Ĭlick to expand.Ah, this makes sense now. If you are willing to deal with the limitations, a Unity 4.6 version can be obtained through the support email if you have already purchased the product and have an invoice number. In the store we only support Unity 5 or above because of the above reasons (needing pro, limited examples, etc). so you only have access to 4 out of the 16 examples (just the very basic ones not the roll a ball or any of the examples that used Unity 5 features. If you have pro on Unity 4.6, the core of the product will work but many of the examples use the Unity 5 shader, materials, prefabs, etc. NET sockets were a pro only feature which is why we decided to target Unity 5 and above only. There isn't a technical barrier on Unity 4.6 but back in Unity 4. It has always been using the newer Unity GUI introduced in Unity 4.6 so older versions like Unity 4.3 that could only use onGUI were never supported. If however you usecase is both multidevice and multiplayer then I'll have to think about how to best modify the current API to make that Easy Wifi Controller (current version) currently requires Unity 5 or above. Is your game multi device but yet single player? If so I could add an entry similar to Unity's 'Get Input from every Joystick' setting and then it would work just fine. I certainly have no problems adding an API to make this smoother, but I'd like to hear more about your usecase so that it fits all of your needs. My original design was built more around your typical game where every player is using their phone/tablet as a controller and obviously in that usecase it makes sense that each of the 'controllers' be the same. If you spread the controls over two separate controls (you must have a lot of controls!) you are currently in your game going to want to assign some of the controls to player 1 and some to player 2. So two different players are given two different player numbers.

Each distinct device is given a player number when they connect. Click to expand.I tested this tonight and it does work albeit in a kind of workaround way.

My controller is saying i am player 2