Unity Remote 4 (further refered to as Unity Remote) is an application that allows you to use your target device as a remote control for your project in Unity editor. This is useful during development since it is much quicker to test your project in the editor with remote control than to build and deploy it to the device after each change.
Unity Remote 4 is a completely rewritten replacement for old Unity Remote 3 and Android Remote, which unifies different platforms with a single implementation and also adds new features. We are phasing out old Unity Remote 3 and Android Remote for iOS and Android, and will remove them in the future.
Currently Unity Remote supports these devices:
The following data from device is streamed back to the editor:
Unity Remote can be downloaded for free from the following links:
Follow these steps:
At this point editor automatically connects to Unity Remote app and will start streaming video output to device, as well as receiving input from device.
Currently Unity Remote doesn’t support multiple connected devices of the same kind (ie two iPhones or two Androids), and it will automatically pick the first device it finds. But it’s fine to have one iOS and one Android device connected at the same time, and select which device to use in Edit->Project Settings->Editor under Unity Remote settings before pressing Play button.
When you use Unity Remote, the game actually runs in the Unity editor while its visual content is streamed to the target device. Since the bandwidth between editor and device is limited, the stream is compressed and you will see unavoidable artifacts. There is no way to change that. Unity Remote’s purpose is for a quick approximate check of how your game would feel like when run on the device and for other quick tests. For real experience use the usual means to build and deploy the app on the device (use
in the Unity editor).To establish connection to iOS device through USB, Unity uses a 3rd party utility (iproxy) which sometimes misbehaves. You can try the following to fix the problem:
In most cases reconnecting or restarting iOS device is sufficient to fix the problem.