Edited by _g3nki at 2016-01-19 01:20 |
8Bitboy 2016-01-17 18:43
We design the controller's layout of NES30 Pro as the Nintendo layout, so when press the key A it se ...
Thank you so much for your kind reply 8Bitboy.
I understand what you mean about the confusion. Especially during the mapping process in i.e. emulators. Don't get me wrong, I am very sincere while writing this. The NES30 Pro and FC30Pro are really really good controllers, no doubt about that, solid quality, great feel and very functional! however it does not follow the guidelines for an Android TV compatible controller. There are two problems with this, first, Android TV controllers are becomming the standard on the OS. The NES30 Pro and FC30Pro won't work with all games as long as the developers are not activly working on making their game compatible with non-android-tv-controllers. Second issue is the button mapping. As a game developer I strongly believe that 8Bitdo should map the keys the other way around on android. I am currently creating a game for both Android and IOS and as a developer I will always expect the buttons to be located on the same pace as on the conventional controller, no matter what letter or symbol is defined on the controller. Many games, even the most popular games, show screenshots of controllers with the placement of the input, without letters or symbols (Asphalt 8 is one example where the 8bitdo controller doesn't work as intended by game developers). When I play first person shooters, like Half Life 2, I activate the flashlight instead of using reload button, which can be devestating.
I even needed to remap my controller for snes and nes emulators because it did not follow the android convention. Otherwise it would work out of the box. Sure, I get that it can be confusing during the mapping-process and if you look at the controller. But to be perfectly honest, if everybody did according to the guidelines. mapping wouldn't even be needed unless developers wanted to give this freedom to the players. The nintendo layout of the buttons should be seen as "decorative" rather than a functional hazard.
To summarize: I strongly believe, as well as google, that "button location" is much more important on android than the letters/symbols on the controller because of the open hardware eco system that android has. Most developers don't even use the letters today, instead they show the location of buttons during tutorials in order to cover all kind of controllers. Even Google have guidelines for this to game developers. This is a convention which I think 8bitdo really should not go against. Or at least offer a firmware that has the correct mapping, and hopefully one that makes the controller fully compatible with android-tv devices (which is starting to become a platform standard).