Controller problem

Kurai · June 2013

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!

tgraupmann · June 2013

Unity - Example - ShowUnityInput - Part 1

Kurai · June 2013

Ok, right now I've imported the Input settings from the Ouya Panel. It seems correct (but I've got 71 Axes instead the 121 I see in your video).

Then I've decided to take advantage of your OuyaExampleCommon script, so I can use easily other controllers.

I've written my input script again, taking inspiration from this post. For now I've just made a script which will load the main scene when pressing the O button. Simple as that; I've attached such script to my camera. And used this code:

void Update () {

if ( OuyaExampleCommon.GetButton(OuyaSDK.OuyaPlayer.player1,OuyaSDK.KeyEnum.BUTTON_O) )

{

Application.LoadLevel("flytest1");

}

Which should be pretty straightforward, but still it doesn't work.

I guess I still need a bit of help on this matter. Thanks!

tgraupmann · June 2013

Oh you know what I need to probably upgrade the 3.X project settings to the 4.X project settings so you can get all 121. I'll do that and check it in...

tgraupmann · June 2013

Make sure you call OuyaExampleCommon.UpdateJoysticks() in an fixed update loop. That way it gets the joystick name every 3 seconds.

Kurai · June 2013

Yeah, I've done that in my Ouya Game Object prefab :)

tgraupmann · June 2013

Well the GameObject has to be in the scene to update. A prefab is generally in the project view.

Kurai · June 2013

Yeah, I mean I did it in the script attached to the object which is in the scene (sorry for the misunderstanding!)

tgraupmann · June 2013

Okay and if you use the ShowUnityInput scene does the virtual controller light-up and work for you? It's always possible to need more mappings for new controllers...

tgraupmann · June 2013

Okay I backed up and upgraded the project settings for 4.X. So you should see 121 inputs in Unity 4.X.

Kurai · June 2013

Ok, I've set up the new Input settings, but nothing happens. I'm still unable to control the game.

I've tried the controller example and the problem is still there: on the controller list the pad seems to appear, but it doesn't show buttons/axis activity.

Everything in my Ouya panel seems to be set up in the right way: nothing is greyed out, and the projects compile and run without any problem (they don't show up in the make/software directory, though, don't know if this is normal or related in any way).

tgraupmann · June 2013

Look at your OuyaGameObject in your initial scene. In the inspector "UseLegacyInput" should be unchecked OFF.

Kurai · June 2013

It's unchecked. Still no luck :/

tgraupmann · June 2013

This is almost the same Q's as this thread maybe we covered it here:

http://forums.ouya.tv/discussion/comment/12652#Comment_12652

Kurai · June 2013

Yeah, I'm following that thread also. I think I did and double checked everything, but still it doesn't work.

The only different thing I do is that I put the OuyaExampleCommon.UpdateJoysticks(); call inside the OuyaGameObject in the scene rather than in the object checking for inputs. But this shouldn't matter at all.

I guess I'm going back to try some of the example scenes and see what happens.

Kurai · June 2013

Ok, ShowInput scene actually works.

Now I just need to understand what I'm doing wrong in my own project :)

ClarkGame · June 2013

Hey Kurai,
I just adde the solutions I found to a new discussion. Hope that helps.
Controlle Solutions

Kurai · June 2013

Thank you! I'm going to try it as soon as I can!

Kurai · June 2013

That works!

It seems to be still a bit clunky, though, I used GetButtonDown and the button responds after half a second or so. Tomorrow I'll try it on the game itself (right now is only to pass the first screen) and we'll see what happens.

Howdy, Stranger!

Categories

Controller problem

Comments