Almost very morning I have trouble initiating the connection between my Mac and Unity Remote, I often have to relauch several times Unity and Unity Remote, and sometimes I event have to reboot.
Anyone has an idea what could be causing this problem?
Almost very morning I have trouble initiating the connection between my Mac and Unity Remote, I often have to relauch several times Unity and Unity Remote, and sometimes I event have to reboot.
Anyone has an idea what could be causing this problem?
if you are using your mac to offer the wifi, ensure you are far enough away for it to work.
wifi connections don’t like it if the device sits “right next on the antenna”
Thank you for your reply.
I’m using a router (freebox – french) which is not in the room where I work (I nonetheless have perfect connectivity). Both the iPhone(3GS) and the Mac(MBP Unibody) are connected to the router.
I have bluetooth disabled.
EDIT : 3GS is 3.1, Mac is Snow Leopard
I constantly have problems with the remote. It locks up, it will find my mac but won’t connect, sometimes even Unity locks up when using the remote.
Sometimes it is worse then other times, but I can’t find any pattern in the problems.
I have bluetooth disabled on the mac and the iphone.
I try connecting with the wifi in my house (Airport) and I try by creating an adhoc network from my macbook. Neither makes any difference.
You’re fortunate to be getting any connectivity with Snow Leopard. There’s a bug in either Unity or Unity Remote that causes it to either hang or crash Unity or both. The Unity guys have said they’re working on the problem in a few other threads. Unfortunately, that doesn’t help you very much now.
I actually downgraded to Leopard as I needed Unity Remote. Of course, there’s also a lot of other issues with Snow Leopard as well (building and the lowercase renaming bug). These are also known issues as well.
You should report a bug with your experience so that they’ll have as much info as possible to track down the bug.
Yes Unity remote is complete crap. Why can’t I just hook directly up using USB cable? And I don’t use Snow Leopard.
Unity remote is easily the biggest source of wasted time on our projects. And now Unity itself crashes a few times per day when trying to use Unity Remote.
I just LOVE when unity remote refuses to relaunch, too. It just locks up on the load screen.
I think because they can’t. You can not just send any communication you want through the usb cable, it is restricited.
It works quite well for me btw, so I personally don’t think it’s complete crap at all ![]()
Always have touch and connection issues with UnityRemote. I try to use it as rare as possible.
I’ve never had any issues with remote or unity here… both work like they say on the tin.
I’m linking Mac/Remote via a Router in a distant room with Snow Leopard with no issues so I don’t think it’s a Unity/Remote problem you’re having.
I’ve had on again off again issues with the remote, but at the moment I’m using
Snow Leopard and the latest versions of everything (except Unity - 1.5.1) and I’m cruising pretty well.
My experience has been that one device worked really well for me, and another (others actually) didn’t. I fiddled around with the Remote code and managed to fix most of my problems (see here: http://forum.unity3d.com/viewtopic.php?p=268659&highlight=#268659 ) but if nothing else, my experience has been that:
The Unity remote issue is not necessarily a systematic issue that will impact all devices equally, instead it seems to be almost on a device-by-device basis. With two nearly identical devices (OS 3.1.2 3G and original iPhone), I was having two very different experiences. One worked well, and one didn’t.
Fooling with the Remote code got me much better results, but it could’ve been any number of things that actually “fixed” my problems, including just doing a fresh re-install using the latest build of Xcode. I’m too scared to screw up my devices again to do any solid tests to really fine tune what’s going on, though.
So take my experience with a grain of salt. If nothing else, perhaps deleting and rebuilding the remote (and perhaps changing some of the settings) may work, or maybe I just happened to get the Unity Remote Fairy on a good day!