I understand all of that, but the fact is there are plenty of tvs that don't do 1080p, and my whole point was that the output to my 1080i television looked absolutely dreadful (worse than standard def). I have, however, since tested it on another…
Only problem I could foresee would be hooking up a bank account/credit card to things, though most banks today will give you a credit/debit card at any age.
To add to what arcticdog said, you also have to remember that developing android/ouya is actually a convergence of several different technologies that you are trying to learn at once. If you were just setting out to learn java, that would be one th…
So I guess a better answer to your question mite be:
it's exactly as easy as making a game for android phones (maybe easier since you don't have to deal with 1000 different devices),
So far, my experience, it's been slightly more difficult than …
You can actually find out right now - if you make a game for android, that will be about the same level of difficulty as making a game for ouya. For an easy start, try making a puzzle type game, like connect 4, using the canvas class (or opengl if …
I'm pretty sure the first index is 0, however it can be hard to tell, as the state returned does not seem to function properly for the majority of the controller.
Anytime state querying is what he's looking for, but like him, I am finding that it only works for the o u y and a buttons. The dpad, l1, r1, triggers, etc, are completely ignored as far as I can tell.
if(controller.getButton(OuyaController.BUTTO…
I have a pretty nice (Maybe not top of the line, but above average) flatscreen from around 2010 with hdmi inputs that only does 1080i, as well as a projector screen television from a few years earlier.
I don't think it's safe to make those sort o…
I've been using the controller a lot recently, and have to say, after several hours of playing with it:
My hand felt tired. Much of the play was on the dpad and analog sticks, not even using the triggers. Unfortunately, I can't quite nail down wh…
While it does "work" on 1080i, it looks worse than standard-def. From what I can tell, it is skipping scan lines when it goes out to 1080i, and this is causing entire pixels to not be drawn (we had one and two pixel white borders on some of our spr…
When what it actually says:
"No. In order to level the playing field, we are only accepting new work having been created between the initial CREATE announcement on January 7th and the end of the jam on January 23rd, or old work that other people do…
I don't think the battery position is bad (I really like the balance in fact), so much as the way its accessed. When you consider the sort of negative stigma this is going up against, and first impressions and all that, it's not great to literally …
As programmers, I think we can all agree that if someone is not doing something the same way we are, doesn't like a method that we like, or worst of all, outright disagrees with us, they are clearly a total noob who should learn how to program.
I'm afraid I still don't see a reasonable argument against a pause button, unless I've missed something. The idea of overloading the system button with pause and system functions is automatically increasing the learning curve for your average joe, …
You have to assume that all tv's can over-scan. Rest assured, this is an inherent problem with doing ANYTHING for a television.
http://en.wikipedia.org/wiki/Safe_area
