???
I didn't say traffic is the cause of the issue.
I'm talking about why they made deadzones on purpose.
I think they had to reduce the traffic to reduce the energy consumption, and to avoid the flood of events.
This is natural, but the method was …
airman said:
My
unit needed an update on first startup; I have seen others saying they
did not need an update when they turned it on. Not sure if that's an
indication. Maybe someone who already had the update will chime in with
their contro…
I thought this issue could be fixed by software update...
I will not replace the controller, because it hurts OUYA's finance.
If the issues are really fixed on the retail one, I will buy it in addition.
OUYA is not only their business, but also our …
efroemling said:
The modified FingerPaint example is using getAxisValue() in dispatchGenericMotionEvent() (see line 43 in FingerPaint.java). There are some calls to event.getX() further down but those are just left over from the original de…
efroemling, you are using normal Android API (event.getX()), but it is not the best way to get raw axis values.
Would you please try in this way?
(except deadzone processing)
https://devs.ouya.tv/developers/docs/controllers
I am afraid that they only think they have already fixed it.
We will have to test again with retail version controllers.
We are The Developers.
So, they cannot deceive us.
What I want to say to Julie is,
Just be honest.
Just explain it.
Just apol…
This is maybe a driver issue of OUYA controller .
OUYA's system programmer should read this article.
http://www.third-helix.com/2013/04/doing-thumbstick-dead-zones-right/