Hi,
I'm using a Nintendo gamecube controller with USB adapter plugged into my prime dock. This works fine in games like shadowgun and a few emulators - ST, Frodo c64, Marvin spectrum, N64oid, Mame. However, I can't get it to work properly with nesoid, snesoid, genoid, gbaoid
The d-pad and analog stick work fine, but it won't map any of the controllers buttons. When I go to configure the controller and "press a hardware button" to pick button A for example - it takes the click of my joystick button, but then displays "unknown" next to the button, and doesn't recognise the button in the game. This happens for all the button assignments I can map the buttons fine to the keyboard, or use the on screen controls - but it just won't recognise the button press - displaying "unknown" each time.
any help/advice would be much appreciated. I'm tempted to try some other emulators - but not sure which ones to try.
See if anything on this site might help you:
http://wiki.greenrobotgamer.com/
kaiserpc said:
Hi,
I'm using a Nintendo gamecube controller with USB adapter plugged into my prime dock. This works fine in games like shadowgun and a few emulators - ST, Frodo c64, Marvin spectrum, N64oid, Mame. However, I can't get it to work properly with nesoid, snesoid, genoid, gbaoid
The d-pad and analog stick work fine, but it won't map any of the controllers buttons. When I go to configure the controller and "press a hardware button" to pick button A for example - it takes the click of my joystick button, but then displays "unknown" next to the button, and doesn't recognise the button in the game. This happens for all the button assignments I can map the buttons fine to the keyboard, or use the on screen controls - but it just won't recognise the button press - displaying "unknown" each time.
any help/advice would be much appreciated. I'm tempted to try some other emulators - but not sure which ones to try.
Click to expand...
Click to collapse
Hi,
you have to change the keyboard mappings in /system/usr/keylayouts/Generic.kb (hope, I remember the path correctly ) I redefined myself the buttons to numbers 1-8 and now is no problem to change it in snesoid etc. You need root to change this of course.
Or you can try the External Keyboard Helper from Play and redefine the keyboard there (didnt tested, but should work as well)
Hope, this will help.
Tomas
Related
So I have an asus transformer with revolver rom and bladez kernel. 3rd party xbox 360 gamestop controller.
I mapped all the buttons and joysticks with usb/bt joystick center. Everything works perfectly with shadow gun and other apps.
In N64oid I map the keys perfectly with no issues. When i start any game the controller does not work. Wierd thing is if I map letters to the buttons then when i use those buttons nothing happens until i quit a game. Then on the game select/folder browser screen i can see all the keys that where pressed by the buttons typed at the bottom like a search.
I have tried many different button combinations for the controller and several different N64oid versions with different kernels as well. The controller works fine without usb/bt joystick center but then the triggers and right joystick do not work, I would like to map the c buttons to the rigt joystick.
Please someone has had to had this issue before me and how do you fix it? Or is there another way for my to get my right analog stick to work?
Thanks alot guys
same happens to me, without the center i can play good with controller and wire, but with the center app nothing happens in the emulator.
has anyone figured out how to solve that problem?
Bump
Since the 4.2 update this app no longer works with bt.
Hello everyone. I was able to connect my PS3 controller to my tablet without the use of any apps or rooting. I use the Mupen64 emulator and wanted to have the right joystick act as the C Stick but it seems it isn't reading the right analog stick. I've also tried it with N64oid and that too doesn't work. So what is the deal?
Bizzare88 said:
Hello everyone. I was able to connect my PS3 controller to my tablet without the use of any apps or rooting. I use the Mupen64 emulator and wanted to have the right joystick act as the C Stick but it seems it isn't reading the right analog stick. I've also tried it with N64oid and that too doesn't work. So what is the deal?
Click to expand...
Click to collapse
I was was having the same prob and searched everywhere. Then I finally realized that the best thing to do was use a combination of the sixaxis app's touch emulation and mapping most of the buttons with N64oid (works better than Mupen64). So here is my configuration:
*Note - I took a screenshot of Mario Kart 64 right before the spinning Nintendo logo with the virtual buttons on since the screen is black, and is easier to map onscreen virtual buttons*
N64oid (ps3 buttons on the left, n64 buttons on the right):
Square = B
Cross = A
L1 = L
R1 = R
L2= Z Trigger
Start = Start
D-pad on ps3 is mapped to match n64 D-pad
Sixaxis app touch emulation I used to map N64oid's onscreen analog stick to the PS3's left analog stick (you MUST edit this button and check Relative Touch, or the analog stick will not work!), and I also mapped N64oid's onscreen C-Stick to the PS3's right analog stick. In N64oid, there is a section to hide the controls in the Virtual Keypad settings (after I did all the button mappings), and I checked all the boxes, so I would not see any virtual buttons during gameplay
I hope this helps. I did save my sixaxis profile, so if you need it, let me know
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I was attempting to setup my PS3 controller with my GalaxyS3 using the app Six Axis Controller.
I was to pair my controller, and get it to work wireless but I'm having some strange configuration issues.
It seems that the PS3 buttons have pre-assigned functions such as the Start Button which behaves like the GS3's home button.
This is causing conflict in some of my games.
Specifically on Dungeon Hunters 3 there are only on screen controls.
I went into SixAxis and setup a profile for the on screen controls.
However when I push the start button it still call the Home Key and kicks me out of the app.
It seems the keymaps do no override the pre-assigned mappings.
My question is,
Is there any way to disable these pre-assigned mappings so that there is no button conflict?
I should note, emulators work fine. If I go into an emulator and assign a key it sees it as a gamepad button.
The NES emulator for example accepts the Start and Select buttons just fine.
It only seems to effect native Android games with on screen controls.
Any ideas on how to resolve this?
Thank You...
I think I've figured it out.
There is a change you have to make to Six Axis Controller.
After creating your OnScreen controls, you have to set them to active in SixAxis.
To do so when you open SixAxis you'll see an option
Active Touch Profile
You need to select the profile that you want active in order for it to take over the button functionality of your PS3 controller.
Hope this helps others...
OK... So I have searched everywhere on this and almost every thread on OTG is about getting it to work... Or more specifically getting a SixAxis to work.... There's already plenty of info about Sixaxis and I'm not asking about it....
I have a Retrolink SNES GamePad, and an Xperia Pro MK16i.
I've connected the Snes Pad using an OTG cable and it works as a standard controller, where Dpad is cursor keys, Button1 is Dpad Select, Button2 is Back....
The issue is that when I hold Button4 (Y on the Snes), it releases the Dpad Left/Right, and then pressing the Dpad Left/Right releases Button4...
It will not let me press Dpad Left/Right AND Button4 at the same time (eg. Running in a Super Mario game)... The same thing happens with Dpad Up/Down and Button5 (L Shoulder Button on Snes).
All other buttons work perfectly together and have no affect on the Dpad.
Also this is not an issue with the GamePad itself... As I've tested it on both my Windows7 systems (one is HomePremium, one is Professional), and the Y Button works perfectly fine with the Dpad, as does the L shoulder button.
I have no idea what is causing this conflict, and any help would be appreciated.
I should point out they only have an affect on one axis, so:
Button4 can't be pressed with Left/Right, and
Button5 can't be pressed with Up/Down.
EDIT: I forgot to mention, I'm on the Stock GB ROM 2.3.4
Hi all,
I am trying to map some keys to play a game named War Robots on my Android Nvidia Shield TV device but I am struggling with one key but only in 'touchscreen mode'. Unfortunately in 'keyboard mode' the game doesn't seem to operate correctly and the robot turns in circles and you have to press the toggle to make it stop turning whereas in touchscreen mode (i.e. unplug the mouse and keyboard) the turning is perfect but I can't map a button on my controller to trigger firing all weapons.
The firing all weapons button when using a keyboard and mouse is mapped to Left Mouse Click or Shift or funnily enough the pipe symbol '|'.
This is what I have done so far:
1. Installed a keymap app on the Shield
2. Mapped all buttons (X and B controller buttons to Space and 'Q' for other special game properties) and have the 'Fire All' button 'Shift' triggered by the 'A' button on the controller.
When I start the game with the keyboard I test this and all mappings work fine and 'A' does seem to 'Fire All' but as soon as I want to go to touchscreen mode (by unplugging the keyboard and mouse) to get the maneuverability working the 'A' controller button no longer does anything although the other mapped buttons do still work on the controller.
So frustrating that touchscreen mode seems to just stop this one button and I have spent hours at this trying the other buttons that had mapped okay to 'Space and'Q' to the 'Fire All' to get around it but had no luck so maybe there is no way. I am not even sure if this touchscreen mode is unique to War Robots to be honest or it is standard Android.
Anyone know in Android touchscreen mode how to trigger a left mouse click or Shift button press maybe or any ideas for a workaround?
Thanks
p.s. this techy stuff might help some gurus on here as to how they do things: developer.android.com/stories/games/war-robots