After the recent update first I wasn't able to find the OUYA device, but I've finally fixed that, however now I've run into this new problem. Everywhere I've looked all I can find are people saying it's just a configuration issue in the OUYA ODK, but I'm not actually using that...soooo?
I'd greatly appreciate any advice if anyone knows how this could occur without that ODK, just by having updated the OUYA console.
EDIT: So even though I had exited firefox thinking it might be a memory problem, that wasn't enough and I had to exit a bunch of other programs and that was the solution, certainly didn't expect it to need so much.
Comments
The general process is import the OUYA Unity plugin. Set a unique identifier, and hit the sync button.
I have some intro videos.
https://www.youtube.com/playlist?list=PL4mjXeDqRBMSlXJEH1l5LueMPfFOCpvJf
OUYA Inc | Android Developer
Skype: tgraupmann_prey
http://github.com/ouya/docs
http://github.com/ouya/ouya-sdk-examples
Check out the latest docs for your game engine: [setup] [adobe air] [android] [clickteam fusion] [construct 2] [corona] [libGDX] [game maker] [html5] [marmalade] [monogame] [unity] [unreal]
Use caution when setting [persistent wireless mode].