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.
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…
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 act…
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 controll…
As I already said, unfortunately even expensive TV sets have this problem, unfortunately. Could it possibly be a PAL vs. NTSC issue? I live in europe. But I guess the differences in resolution/refresh rate are not present via HDMI?
A little update on that matter:
On my TV (as I said, a Panasonic g10, it's a 50" plasma panel) every single game I've downloaded suffers of screen bleeding. Every single one, apart from Ninja Party, which has got a screen resize tool in the option s…
I have to second the request for a screen setting option at system menu level.
My TV is a Panasonic G10, not exactly a basic model, but it doesn't have an overscan compensation setting and I've got overscan issues on many, many games. Canabalt, Beas…