OUYA-ODK Controller Questions

goodhustle · January 2013

FYI, I'm on Unity and getting started with modifying the provided plugin for real input use of a single controller, but running into problems and now have some questions in general about the controllers in the ODK.

1) Are KeyDown events supposed to be firing repeatedly when a button is held down, or just once in a press/release cycle?

2) Is it unsupported to hold multiple keys down at the same time? Holding two keys down results in repeated KeyDown events for only one of the keys. Releasing that key does not result in repeated KeyDown events for the other key.

3) Is the mSeq private member in KeyEvent an Android standard, or is this an OUYA-specific extension?

4) Can you provide a documentation reference for everyone which states the mKeyCode for each button on the controller? It would be very handy. :)

5) It looks like GenericMotionEvents contain axis data for ALL axes, is that so? And if so, are GenericMotionEvents fired if all axes are at zero?

6) Do controller events work on a polling cycle, and if so what is the polling rate?

Thanks!

tgraupmann · January 2013

1) Once on down, once on up

2) Multiple buttons should be supported.

3) That's all AndroidSDK. I sent the whole structure to Unity for debugging to debug the interface on multiple controllers.

4) Every controller is different. But there's a doc on that.
https://devs.ouya.tv/developers/docs/controllers

5) I think the axis event fires on change, so if it changes to zero it fires. Although it's never exactly zero. It's zero by default as well.

6) There's no polling for controller events yet. They fire at will which isn't necessarily good performance.

goodhustle · January 2013

@tgraupmann Re: 1) I'm definitely seeing repeated down events when holding buttons down, not just once on down. I suppose this could be a Unity SDK thing on the Java side, but I wasn't sure.

tgraupmann · January 2013

It's probably on the Unity side. Some controllers were funky where the right/left trigger were button events. Or a button event was an axis event. If you look at OuyaInputManager.cs that's one way to deal with multiple events.

SeonR · January 2013

I cant get the correct mappings working when I build to the console with the OUYA controller. I have done Ayrik's changes to the case statement, and the correct Joystick name is appearing on the console, but every mapping is wrong.

I am sure I am in the correct switch case as I display some debug data to the screen from that case statement.

I am on OSX, Unity 4.0... anyone else seen this?

tgraupmann · January 2013

You need the OuyaGameObject.cs with the OUYA controller mappings.

SeonR · January 2013

I

tgraupmann said:
You need the OuyaGameObject.cs with the OUYA controller mappings.

I did that from the Ayrik's changes in the big Unity Ouya thread. I copied the Xbox ones over to a new case statement, changed it's name to match the controller name, I can see that the correct case statement is working on device, but the mappings are still wrong.

goodhustle · January 2013

You can also try my OuyaInput package posted in the big Unity thread. It doesn't have the latest OuyaGameObject changes but it has configurable key and axis emulation.

Dreamwriter · January 2013

SeonR said:
I
tgraupmann said:
You need the OuyaGameObject.cs with the OUYA controller mappings.
I did that from the Ayrik's changes in the big Unity Ouya thread. I copied the Xbox ones over to a new case statement, changed it's name to match the controller name, I can see that the correct case statement is working on device, but the mappings are still wrong.

Ayrik's post also included keymapping numbers you need to change in that case statement, to make the buttons match up correctly.

Howdy, Stranger!

Categories

OUYA-ODK Controller Questions

Comments