Unity on OUYA - OUYA Developer Forums

P31 Facebook crash, "Don't keep activities" debug setting.

lgaliber — Tue, 25 Jun 2013 15:05:37 +0000

On launching the com.facebook.LoginActivity (via the Prime31 function "
FacebookAndroid.loginWithReadPermissions()"), the main UnityActivity seems to be destroyed underneath, causing a crash. This only seems to occur when the debug setting "Don't keep activities" is checked "on". Unfortunately, it seems that this setting is "on" by default (either on all systems, or many of them). Does anyone know if this is on by default on retails devices? Has anyone found a way around this?

Here is an example of the crash we're experiencing:

06-25 14:35:53.041: I/ActivityManager(306): Displayed com.badjuju.flipriders/com.facebook.LoginActivity: +204ms (total +251ms)

06-25 14:35:53.331: D/FacebookSDK.WebDialog(2105): Redirect URL: http://m.facebook.com/login.php[removed link details]

06-25 14:35:53.331: D/FacebookSDK.WebDialog(2105): Webview loading URL: http://m.facebook.com/login.php[removed link details]

06-25 14:35:53.391: I/Process(2105): Sending signal. PID: 2105 SIG: 9

06-25 14:35:53.421: I/ActivityManager(306): Process com.badjuju.flipriders (pid 2105) has died.

06-25 14:35:53.421: W/InputDispatcher(306): channel '42177fa8 com.badjuju.flipriders/com.badjuju.flipriders.OuyaUnityApplication (server)' ~ Consumer closed input channel or an error occurred. events=0x9

06-25 14:35:53.421: E/InputDispatcher(306): channel '42177fa8 com.badjuju.flipriders/com.badjuju.flipriders.OuyaUnityApplication (server)' ~ Channel is unrecoverably broken and will be disposed!

06-25 14:35:53.421: I/WindowState(306): WIN DEATH: Window{42b83ee0 com.badjuju.flipriders/com.facebook.LoginActivity paused=false}

06-25 14:35:53.421: W/ActivityManager(306): Force removing ActivityRecord{42241490 com.badjuju.flipriders/com.facebook.LoginActivity}: app died, no saved state

06-25 14:35:53.431: W/InputDispatcher(306): Attempted to unregister already unregistered input channel '42177fa8 com.badjuju.flipriders/com.badjuju.flipriders.OuyaUnityApplication (server)'

06-25 14:35:53.431: I/WindowState(306): WIN DEATH: Window{42b7f510 com.badjuju.flipriders/com.facebook.LoginActivity paused=false}

06-25 14:35:53.431: I/WindowState(306): WIN DEATH: Window{42a81170 com.badjuju.flipriders/com.facebook.LoginActivity paused=false}

06-25 14:35:53.431: I/WindowState(306): WIN DEATH: Window{42177fa8 com.badjuju.flipriders/com.badjuju.flipriders.OuyaUnityApplication paused=false}

06-25 14:35:53.431: I/WindowManager(306): WINDOW DIED Window{42177fa8 com.badjuju.flipriders/com.badjuju.flipriders.OuyaUnityApplication paused=false}

06-25 14:35:53.441: W/InputMethodManagerService(306): Ignoring showSoftInput of uid 1000: android.view.inputmethod.InputMethodManager$1@41fcbbc0

06-25 14:35:53.481: I/ActivityManager(306): Start proc com.badjuju.flipriders for activity com.badjuju.flipriders/com.prime31.FacebookProxyActivity: pid=2182 uid=10035 gids={1015, 1023, 3003, 1028}

06-25 14:35:53.491: I/InputDispatcher(306): Dropping event because there is no focused window or focused application.

06-25 14:35:53.491: W/InputMethodManagerService(306): Ignoring showSoftInput of uid 1000: android.view.inputmethod.InputMethodManager$1@41fcbbc0

06-25 14:35:53.581: I/Prime31(2182): launching proxy Activity to intercept SSO login

06-25 14:35:53.591: E/Prime31(2182): Something has gone terribly wrong. The Unity Activity does not exist. This could be due to a low memory situation

06-25 14:35:53.591: I/Prime31(2182): unkown exception occurred locating getActivity(): null

06-25 14:35:53.591: E/Prime31(2182): Something has gone terribly wrong. The Unity Activity does not exist. This could be due to a low memory situation

06-25 14:35:53.591: D/AndroidRuntime(2182): Shutting down VM

06-25 14:35:53.591: W/dalvikvm(2182): threadid=1: thread exiting with uncaught exception (group=0x414f9300)

06-25 14:35:53.591: E/AndroidRuntime(2182): FATAL EXCEPTION: main

06-25 14:35:53.591: E/AndroidRuntime(2182): java.lang.Error: FATAL EXCEPTION [main]

06-25 14:35:53.591: E/AndroidRuntime(2182): Unity version : 4.1.5f1

06-25 14:35:53.591: E/AndroidRuntime(2182): Device model : OUYA OUYA Console

06-25 14:35:53.591: E/AndroidRuntime(2182): Device fingerprint: OUYA/ouya_1_1/ouya_1_1:4.1.2/JZO54L-OUYA/328:user/test-keys

06-25 14:35:53.591: E/AndroidRuntime(2182): Caused by: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.badjuju.flipriders/com.prime31.FacebookProxyActivity}: java.lang.IllegalArgumentException: activity cannot be null

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2059)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2084)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread.access$600(ActivityThread.java:130)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1195)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.os.Handler.dispatchMessage(Handler.java:99)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.os.Looper.loop(Looper.java:137)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread.main(ActivityThread.java:4745)

06-25 14:35:53.591: E/AndroidRuntime(2182): at java.lang.reflect.Method.invokeNative(Native Method)

06-25 14:35:53.591: E/AndroidRuntime(2182): at java.lang.reflect.Method.invoke(Method.java:511)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:786)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553)

06-25 14:35:53.591: E/AndroidRuntime(2182): at dalvik.system.NativeStart.main(Native Method)

06-25 14:35:53.591: E/AndroidRuntime(2182): Caused by: java.lang.IllegalArgumentException: activity cannot be null

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.facebook.UiLifecycleHelper.(UiLifecycleHelper.java:53)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.prime31.FacebookPlugin.createUiHelper(FacebookPlugin.java:47)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.prime31.FacebookPlugin.(FacebookPlugin.java:39)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.prime31.FacebookPluginBase.instance(FacebookPluginBase.java:41)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.prime31.FacebookProxyActivity.openSession(FacebookProxyActivity.java:62)

06-25 14:35:53.591: E/AndroidRuntime(2182): at com.prime31.FacebookProxyActivity.onCreate(FacebookProxyActivity.java:41)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.Activity.performCreate(Activity.java:5021)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1079)

06-25 14:35:53.591: E/AndroidRuntime(2182): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2023)

06-25 14:35:53.591: E/AndroidRuntime(2182): ... 11 more

06-25 14:35:53.591: W/ActivityManager(306): Force finishing activity com.badjuju.flipriders/com.prime31.FacebookProxyActivity

Getting touch pad values from individual controllers?

jrdn — Tue, 25 Jun 2013 14:01:56 +0000

I'm currently developing a four-player game in Unity, intending to utilize the touch pad to control players on the screen. I cannot find any documentation about using the touch pad other than it overriding the system mouse, which I am very disappointed in. This is a core mechanic in our game and not being able to use the touch pad pretty much renders our 2 consoles and 8 controllers useless, which is something we don't want to happen. Please can someone help us out with a solution?

Trigger Input being overwritten by Bumpers

SirisDracken — Mon, 24 Jun 2013 05:23:34 +0000

I am using the ODK to manage input, and when running on the Ouya, I have noticed that while holding down the right (or left) trigger and then pressing and releasing the right (or left) bumper causes the input for the triggers to stop. This does not happen while running in editor and using an xbox 360 controller.

Here is the code that I am using in Update() to handle the trigger and bumper input:

if (OuyaInputManager.GetButtonDown("RT",player)){

value = 1.0f;

}else if (OuyaInputManager.GetButtonUp("RT",player)){

value = 0.0f;

}

and for the bumpers:

if (OuyaInputManager.GetButtonDown("LB",player)){

otherValue = 1.0f;

}else if (OuyaInputManager.GetButtonUp("LB",player)){

otherValue = 0.0f;

}

Has anyone else had this problem or can point me in the right direction to finding a fix?

Track pad causing crash after a few swipes

RaveTZ — Mon, 07 Jan 2013 22:05:36 +0000

I'm using Unity 4 and my Ouya has the latest firmware. Yet when I run anything from Unity, the app will crash after using the touch pad a few times. Any clues as to why? It doesn't seem to care which app I run.

Controller Solutions – (Con)Tribute to Tim

ClarkGame — Wed, 05 Jun 2013 16:40:46 +0000

Hey OUYA Devs, >> SCROLL TO BOTTOM TO FIND THE NEWEST VERSION
or better: HEAD OVER TO THE NEW THREAD

I read a lot of questions about controllers and during the last days fought myself through the new Ouya Unity Input (and before that through the Ouya legacy input). Thanks to Tim's great support the new input framework becomes better every day. It not only works on the OUYA but also solves a lot of controller mapping issues on other platforms. Tim has done an awesome job there. Still the examples have some (minor) bugs and the setup can be somehow confusing. That's why I thought, we devs should contribute to the plugin and upload our solutions.

Here is a proposal for a nice helper script. Right-Click to save as OuyaInput.cs to your disc.

I had a close look on Tim's ShowUnityInput.cs and the connected OuyaCommonExample.cs . In order to implement that stuff in our ongoing project I stripped these scripts down (killing all the example stuff) to a barebone static class that you can directly copy into a project and use instead of Unity's Input class. Most of this stuff is a direct copy of Tim's example, but I isolated the core code, commented it, fixed some axis invert issues and added new access methods. The static class now mirrors Unity's Input class closely on offers identical getters.

You can access the controller data via:
OuyaInput.GetAxis(string ouyaMapping, OuyaSDK.OuyaPlayer player)
OuyaInput.GetButton(OuyaSDK.OuyaPlayer player, OuyaSDK.KeyEnum ouyaButton)
OuyaInput.GetButtonDown(OuyaSDK.OuyaPlayer player, OuyaSDK.KeyEnum ouyaButton) //NEW
OuyaInput.GetButtonUp(OuyaSDK.OuyaPlayer player, OuyaSDK.KeyEnum ouyaButton) //NEW
// The new methods are returning true just for the frame the button goes down or up.
// So they mirror Unity's Input.GetButtonDown() and Input.GetButtonDown().
// In contrast to OuyaInput.GetButton() these can be used to retreive down/up EVENTS.

Examples:
// get the value for a left joystick's x-axis:
OuyaInput.GetAxis("LY", OuyaSDK.OuyaPlayer.player1)
// get the button state for a button on Ouya's O-button position (eg. XBOX360 A-button):
OuyaInput.GetButton(OuyaSDK.OuyaPlayer.player1, OuyaSDK.KeyEnum.BUTTON_O)
// get the button down event for a button on Ouya's U-button position (eg. XBOX360 X-button):
OuyaInput.GetButtonDown(OuyaSDK.OuyaPlayer.player1, OuyaSDK.KeyEnum.BUTTON_U)
// get the button up event for the click press on the right joystick:
OuyaInput.GetButtonUp(OuyaSDK.OuyaPlayer.player1, OuyaSDK.KeyEnum.R3)

In addition you want to call OuyaInput.updateJoystickList() in your FixedUpdate() method!
This makes sure that new joysticks are found or unplugging is covered.

Setup:
1. Just import the OujaSDK core package to your project.
(Plugins/Android, Ouya/SDK, Ouya/ProjectSettings, LitJson, ProjectSettings)
2. Check out the Menu >> Windows >> Open Ouya Panel and set it up (see Tim's videos).
3. Click Menu >> OUYA >> Use Ouya Project Input Settings.
4. Drop the script provided here into your project scripts.
5. ACCESS OuyaInput. methods instead of Input. methods.

Known issues:
The script is far from perfect (just a help for starters).
There still might be axis iversion issues that I did not discover (just fixed the ones i found).
GetButtonUp() and GetButtonDown() should not be called for the Triggers (they are analog and don't work based on Unty's Input.GetButtonDown() – they are treated like axis.

Credits:
This script is mostly Tim's work. But as these legacy input and mapping issues are very confusing I thought it would be good to melt it down to one clean static class that can be used directly. I hope this script is not full of bugs and does not confuse anyone. If there are any issues with this code, please tell me and I will remove it.

Unity 4.1.5f1 and Android SDK r22

Ninjapretzel — Sun, 16 Jun 2013 00:15:44 +0000

Are there support for these?

Since unity went free for android with version 4, and the recent updates to the android SDK breaking stuff (and then being fixed by unity), I was hoping that the latest SDK for OUYA would support the latest unity.

I am currently working on porting an android title over to OUYA, and we decided to move the project 'up' from Unity 3.5 to Unity 4.1, and that all went smoothly.

I was even able to build the project right to the ouya without the ODK installed, to test and make sure it would run, which it does.

I cannot for the life of me figure out how to figure out implementing the ODK into unity.

I made a blank project and set everything up as the FAQ had said

Bundle identifiers are synchronized

Min android is set to 16

Set up all paths and latest SDKs (android SDK/NDK, JDK), but there is still one line in the ouya panel that is grayed out: APT Path under android SDK.

There is no aapt.exe under \sdk\platform-tools\

NDK and Plugin compile just fine, but Compile Java spits out the "R.java cannot be found", when my package names are sync'd. I manually verified the OuyaUnityApplication.java and AndroidManafest files, and they have the correct bundle ID.

Is this just a thing where there is no support for it yet?

I would really like to get the ODK integrated so that our game can be on the Ouya market on launch.

Thanks -

JNI mk greyed out

MURAinteractive — Sun, 23 Jun 2013 04:40:11 +0000

On the Android NDK tab my JNI mk is greyed out. It looked like I needed to update to the 64 bit version because the NDK make preset path has a 86_64. So I went ahead and updated my ndk to the lastest off of the NDK page: http://developer.android.com/tools/sdk/ndk/index.html#Installing

That make the NDK Make no longer greyed out but the JNI mk is still greyed out.

How do I fix that?

Thanks for all the help!

Edit: Just noticed that the vids say you are using android-ndk-r8d and I'm using android-ndk-r8e. Should I be using that one instead?

Also I have been trying to get the .android file Selected by the "Browse Keystore" button but my .android file is a hidden file on Mac and won't let me select the file. (Because the Open window isn't showing it...) How would I make it visible?

Stick Press Not working if joystick is centered

carmineg — Wed, 12 Jun 2013 20:40:33 +0000

I'm trying to check if the joystick has been pressed using this: OuyaSDK.KeyEnum.BUTTON_R3

However, it doesn't work if the joystick is in the center. If I click it with the joystick to the top/left/bottom/right it works.

Any ideas?

-Carmine

Cannot Find Android SDK APT path

volvagia720 — Mon, 17 Jun 2013 12:37:24 +0000

I've just started getting ready to do some Ouya Unity. I've been following the first of the videos in the "Unity Package Videos" thread. I've got all of the java jdk, android ndk and all of the android sdk except the apt path. on the sdk i've selected and downloaded:
+ API14

+ API16

+ SDK Tools & Platform-tools

+ Support Lib

+ Modified Google USB Driver (for deploying to console)
What am I missing? AKA, why is the APT path still geyed out when everything else is in black?

Joystick axis does not reset after being used.

kinifi — Mon, 17 Jun 2013 19:11:18 +0000

Example: LX = Left Joystick X Axis and it equals 0 at start. If I move the joystick left LX = 1. If I let go of the joystick after it equals 1 then the joystick moves back to the middle and my hands are not touching it at all and LX = 1.54342E.

Any idea how to fix this?

New controls with NGUI?

derkoi — Sat, 15 Jun 2013 09:01:59 +0000

I'm trying to get the new control system to work with NGUI. I originally had it working via this thread which worked fine but stopped working when I turned legacy mode off to work with the new control method.

Can anyone suggest a way to make it work please?

Screen.SetResolution() cleanly?

OverpoweredGames — Tue, 11 Jun 2013 17:10:45 +0000

I'm running 720p and I set Screen.SetResolution(1280, 720, true, 60); in Awake(), but it has some visual artifacts when it launches. Any workaround?

Reliable way to detect if OUYA vs Android

carmineg — Fri, 14 Jun 2013 04:46:13 +0000

My device type always seems to be "Android" and never OUYA. Is there a reliable way or compiler directive that is built into the OUYA SDK to detect if it's an OUYA?

OuyaGameObject.onKeyUp() and others taking 4-40ms

Bovine — Fri, 31 May 2013 23:07:43 +0000

More profiling, the OuyaGameObject.onKeyUp() method is reporting anything from a few ms (which is somewhat unacceptable anyway) to 40ms which is terrible.

Any thoughts? :(

The ouya game object

dewlap — Fri, 14 Jun 2013 07:25:34 +0000

Hi there.
Is there any reason why the ouya game object cant be turned into a singleton? This would mean that if in the ide i wanted to press the play button to test say level 10 i dont have to remember to drop a inity game object in and remove it later so it isnt duplicated. Or am i missing the point?

Cheers
James

"Use OUYA Input Settings" doesn't seem to do anything.

carmineg — Tue, 11 Jun 2013 13:07:47 +0000

I got this to work be re-importing all of the latest projects form here:

http://tagenigma.com/ouya/OuyaSDK-1.0.0/

(also.. FYI my controller wasn't listed in that panel: MICROSOFT WIRELESS 360 CONTROLLER) it might just be safer to look for the words MICROSOFT and 360 and then just set it to xbox (instead of the case statement).

-Carmine

input menu

dragonkill — Sun, 02 Jun 2013 21:23:29 +0000

how i can make a menu with GUI buttons

and work with the controller

Input Lag Improvements?

aust — Mon, 10 Jun 2013 06:49:19 +0000

So, I've been running some tests trying to see why my Unity scene with one moving cube on one plane still feels sluggish when I'm playing it on the Ouya. I'm using the newest version of the Unity plugin from github, using Unity's Input API, and I'm not using legacy input. I don't have a high-framerate camera, so for testing I used audio.

I set up a simple scene with an audio sample and a listener, and set the audio (a generated middle C tone) to go off 500ms after either the press of a keyboard button or the Ouya controller's primary joystick hitting 1.0 on one axis. I tested by recording the sound of me hitting the key/joystick, and measuring the time to the tone, and then subtracted 500ms. (I originally had the audio sample play immediately, but I'd read that using PlayDelayed() would queue the audio and play it at an exact time. Unfortunately it did not, but the results in comparison the my PC's response time are the same either way.)

After several tries, here are the average response times:

PC

Key press - 154ms

Ouya

Key press - 212ms
PS3 Wired - 214ms
PS3 Wireless - 214ms (more variation in times)
Joystick - 270ms

Now, I think I can attribute the original 154ms of the PC to the fact that playing audio at an exact time is something that's just hard. If I had that camera, I'd give Unity the benefit of the doubt and say it could probably draw something on the screen faster than that in response to input. I did set Unity's audio settings to "best latency," but maybe there's some other settings or method of playing audio I'm missing that would reduce this time.

What I'm having trouble with is the Ouya taking 67ms longer to respond to the exact same input from the same wired keyboard in the same scene. On top of that, introducing the Ouya's wireless controller adds another 58ms of lag, for a total of an extra 125ms. The joystick test is even a little generous, because the value of the axis hits 1.0 before the stick clashes against the rim.

I understand some strides have been made recently in reducing input latency, and I really hate to be a downer since you've just made an improvement, but is this still something that's being actively worked on? Is this as good as it's going to get? Is it something inherent in using Android?

Or maybe I'm just doing something wrong; I would love it if I am, because to me this is still a pretty unacceptable amount of input lag. Is anyone else experiencing this?

EDIT: Added PS3 times.

Can't get BUTTON_SYSTEM or "SYS" to work (does button listener work?)

carmineg — Wed, 12 Jun 2013 00:42:08 +0000

All I'm trying to do is see if the system button was pressed one time so I can popup a menu to the user.

I'm tried everything listed in the other posts. I've tried adding a button listener (it doesn't seem to ever be called). I went into the code in OuyaGameObject and tried some debug statements and it doesn't seem like it's is called their either. It also doesn't seem like HandleButtonEvent is ever called inside of OuyaInputManager

DPad, O,U, Y,A all work.... I'm using OuyaExampleCommon.GetButton for those. However, it's clear the system button is not mapped in anyway in that function.

Please advise. I've spent hours trying to figure out something that should be really simple :(

-Carmine

SetResolution Causes Odd Windowing?

Bovine — Fri, 31 May 2013 11:08:57 +0000

Hi All

I've recently received my backer unit and installed a drop of our game on it. 1080p is too rich for the per-pixel lighting we have going on, so we're setting the res to 720p but...

We get this odd cut out and the 720p framebuffer isn't scaled to fill the screen.

Any thoughts?

Thanks

Ian H

IAP Questions

EMcNeill — Sat, 08 Jun 2013 00:54:18 +0000

Tim just posted a helpful video tutorial on how to handle In-App Purchases: http://www.youtube.com/watch?feature=player_detailpage&v=lJjGH_KIE7o

I still have a few questions, though. For one, it's recommended in the documentation that we "be sure to invoke a single request and wait for the response before invoking the IAP service again". Do the requests eventually time out with an error or cancel event or something? If not, what's the best practice when we've sent a request and don't get a response?

Also, we're instructed not to make requests until the IAP system is confirmed to be initialized. Do we have to request the initialization, or does that happen automatically?

OuyaInputManager to behave like Unity InputManager

Setsuki — Mon, 11 Feb 2013 11:53:40 +0000

Hello everyone,

I'm pretty sure the code I'm posting here has already been made, and maybe even already posted, but I can't find it anywhere.

If you're used, or want the down (getButtonDown) and up (getButtonUp) states to behave like Unity does (down is true only once), I made a small script for that. It's a mashup between Unity's philosophy and Ouya's, it's not deep, hardcore code ; basically, it's booleans that go true or false according to Unity's input behaviour. If you want a copycat of Unity's InputManager You'd better try @GoodHustle 's OuyaBridge https://github.com/getluky/OuyaUnityBridge

My script : http://pastebin.com/1GgZxL2Y

This script hasn't been approved by any of the official Ouya devs, and isn't official in any way.

it doesn't replace OuyaInputManager nor any of the SDK tools, you still need them.

How to use :

Simply attach the script to the object you want to control, configure the player number with the inspector.

In your control script, use it as a variable. Here is an example that writes the states on the GUI :

http://pastebin.com/d5HJ3t6N

Unity Crashing since OUYA Integration

Bovine — Sat, 01 Jun 2013 11:02:18 +0000

Hi All

Since starting integrating the OUYA ODK Unity crashes every time I try and go to a breakpoint. It was find before but I have recently upgraded to the newer version, 4.1.3f3.

Is anyone else having this problem? Is there anything I shouldn't be doing #if defing out? - that said I cannot get it to break in one of the samples even :/

Thanks

Ian H

Controller problem

Kurai — Mon, 03 Jun 2013 12:18:10 +0000

Hi there.

I know, that's a newbie question, but I've searched the forum and now I'm more confused than ever.

The question is fairly simple. How do I read gamepad input on Ouya?

I made my demo game, built it and then I ran it on Ouya. But it doesn't get any input from the gamepad.

These are my Input panel settings:

And I call the buttons on my player script like this:

if (Input.GetButtonDown(fireButton)) InvokeRepeating("Shoot", .001, fireRate);

By passing to the fireButton variable the string "Joystick1Button4".

But nothing works.

I'm puzzled because I cannot understand if I have to write a different code in order to read OUYA controllers (but reading the forum it seemed to me that the custom code is legacy now and that I can use the standard unity input API). Can you help me a bit?

Thank you!

OUYA & Playmaker

derkoi — Mon, 03 Jun 2013 17:56:26 +0000

I'm not a programmer & use Playmaker to make my games, I get by every now & then by programming Playmaker actions & I've managed to program a OUYA button action for my game. It works really well.

Anyway I've been trying all day to get the Axis controls working and I can't seem to get it working. I've been using various examples with no joy. Can someone point me in the direction of some code I can use that gets the X & Y Axis of the joystick & stores them in floats? Thanks

A way to use Unity input instead of OUYA input in Unity 3.x?

SwiftIllusion — Tue, 04 Jun 2013 23:29:05 +0000

First I need to say though I understand the efforts being put into the Unity plugin,
and I've read through http://forums.ouya.tv/discussion/713/ouyainputmanager-to-behave-like-unity-inputmanager,
regardless the OUYA input does not work like Unity's does, and I need it to
because I use Playmaker button actions for the input in my projects,
and I need functional 'get up' and 'get down' actions that act for the single frame.
My previous solution was to just not have the ODK in the scene, it was the
only method I could get to work, however now I'd like to have the ODK
but I can't seem to find any of the old examples that were attempting to
override the Ouya Input while keeping the ODK.
I didn't use any of them originally because all the examples were incomplete
or people just saying they got it working without showing how, but I thought
if I spent enough time looking at them I might somehow work it out,
but I can't even find them now?

I've looked at https://github.com/getluky/OuyaUnityBridge,
but that seems to be for Unity 4.x, and still requires programming,
it doesn't simply allow the Playmaker button actions to function as they should.
And the script in the first post here http://forums.ouya.tv/discussion/713/ouyainputmanager-to-behave-like-unity-inputmanager
doesn't affect the entire scene which is what I need, I don't want to have to go
through every single object and attach this script as I expect that would
make an impact on performance and would be very time consuming.

So I'm hoping, does anyone have any solution for this?
A solution that would allow me to have my button actions act as they should,
with the ODK in my scene?
I'd appreciate help for this greatly as it's the largest stepping stone I need to
get over to start making progress with my project.

Game now crashes on OUYA

derkoi — Tue, 04 Jun 2013 15:16:31 +0000

I updated to the latest version from Github following the video Tim uploaded & when I build & run my game on the OUYA it instantly returns to the OUYA menu.
I've tried removing all the new files & reinstalling the older versions but it still the same. I've tested all the package links & none are greyed out. I've rechecked my developer ID in the OUYA game object, that's fine also.

Any ideas please?

GIT Clone Subfolder Only (eg. Checkout just SDK without examples)

ClarkGame — Mon, 03 Jun 2013 12:12:19 +0000

Hi Tim,

I checked out your GIT repository for having the newest version of your Unity framework – works fine and GIT is very nice to have.

However I would like to integrate versioning of your plugin in our running project. In that way we would make sure that we can stay updated without that copy paste madness – after all that's what is cool about versioning tools. However in GIT it is not possible to check out subfolders only (as is in SVN). Therefore we always get a bunch of stuff that mess up our project (examples, additional assets etc.).

So wouldn't it be cool to create seperate repositories for the core folders only?
My proposal for seperate repositories:

Ouya/SDK
Ouya/ProjectSetting
Ouya/Examples
Ouya/StarterKit
NGUI
LitJson
Plugin/Android

In that way we could directly link our project with your SDK without checking out NGUI (we use UIToolkit) or the examples. Would be so cool...

Polygon count for OUYA?

GlesgaeGames — Sun, 28 Apr 2013 16:53:24 +0000

Hello, I've been thinking of developing for OUYA however, I'm just worried that OUYA won't be powerful enough for 3D. Could anyone tell me, how much polys they've been able to get for 60 FPS and 30 FPS?

Thanks for your time,

Sam Kennedy