I'm having a strange issue with SNES9x when my TF101 is docked. Although the keys are set up right and SNES9x detects the keys properly when using the key configuration page, the main controller keys don't work when playing a game.
I've tried all sorts of reconfiguration, but the issues remains. The movement keys, save/load memory state, start/select keys all work, but anything that maps to A, B, X, Y, L, or R has no effect whatsoever. Does anyone else have this issue?
I've noticed it does work alright in SNESoid, but I greatly prefer SNES9x (Free, no ads, not as many permissions needed).
Not to necro an old thread, but, i am having similar issues and decided not to start a new thread
I can map the keys, but, the only ones that work are enter for start and space for select. I've tried a number of different configurations but none of them work.
Related
I recently noticed a weird issue with the HTC Touch Pro I have, I'm prety sure this issue is the same for all builds though. Wanted to try out a few games and start transferring over the ones I had on my Kaiser, but I noticed the keyboard on the Touch Pro gives out the same keycode for all letter, numbers, and symbol buttons.
Using a keycode app program I noticed almost all the buttons give out 0xE5 (299) code. No matter what button u push (except for buttons like caps or del.) its the same code. This makes mapping buttons in games impossible. Has anone else noticed this issue with apps or games??? I'm pretty sure its not just me..
Hi I was just wondering if anybody has had this problem before on a huawei u8350 or other android on froyo 2.2.2 or other. The phone is rooted When I press a key, any key including menu, home, back and all the letters numbers etc I get the same input as that key on any other key pressed after it. I think it was mainly/only 1 repeat but sometimes maybe more. So if i pressed A then B it would enter AA then AAB if B was pressed again. This also applied to the thumb controller. I have recently used some non market app's VGBA ( a gameboy advanced emulator packaged with lucky patch), FPSE ( PSONE emulator) I don't know if that has anything to do with the problem. I ran an avast virus scan, nothing detected and I don't think it could be a hardware problem as I have tried using various input options and the problem remained until I rebooted the phone. Seems fine now but I was just curious as to what might have caused this???? Thanks in advance
Anyone know how to map the analog triggers? So far I can't get any emulators to recognize the L R triggers.
Sent from my GT-N8013 using XDA Premium HD app
Supern64 recognized mine. The buttons on screen don't look like they are recognized but they are. It's the only one I've really tried so far.
I've noticed it too. I kept downloading different emus to be able to map the triggers. ppsspp(psp emu) has a GIT build that lets you map the gamepad
I noticed they don't work in some emulators too. Most importantly N64oid. It doesn't recognize the triggers or second joystick. Had to use mupen.I don't think they work in supergnes or myboy. It's annoying..
Edit - I forgot you need root to use tincore keymapper. I always root my stuff so I didn't even think of that.
The app Tincore Keymapper can do it. You need to have the app running while you play whatever emulator you want the keys mapped to. It can detect the right stick as well. It can also detect which emulator or app you are using so it can switch to that profile without you needing to change settings if you want multiple profiles.
A couple of pointers about that app if you use it.
The app doesn't seem to be able to detect the home key very well so it doesn't really work while the app is running. What I did was map the nvidia key (which tincore sees as the power button) to home while the tincore app is running. Not really a big deal since the nvidia key is really only useful if you are rebooting or planning on playing tegra games which wouldn't need the tincore app to be running.
The volume key needs to be mapped to volume_mute as otherwise it is going to get set as the "Select" key and your volumes won't work.
For touch based games, I have to use "Swap scale" and force the orientation into landscape under "device natural orientation" in the tincore app settings in order for the touches to be mapped to the proper screen location in touch based games. This wouldn't matter if you only ever use it for emulators though. If you don't select these your dpad or other buttons may not map to the proper location on the screen.
For the right analog stick to function without having a mouse pointer floating all over the screen you may need to disable the mouse pointer before you run the tincore keymapper. You can disable that mouse pointer in the android settings under controller.
Anyway, this may seem confusing but once you mess around with the app a little you will understand what I mean.
I had to download the app to my Galaxy S 3 and pull the apk out and sideload it to me Shield. The dev said he is working on getting the Shield to show up properly in the play store and he recommended side loading it for now.
I have tried Mupen, N64oid, and SuperN64 and I can't figure out what the right setup is. I would ideally like to get the c buttons mapped to the right analog stick, have the left analog control movement, get the Z button mapped to one of the triggers, and the L and R buttons mapped to the bumpers. Ideally, I'd also like to get quick load and quick save mapped somewhere too, maybe X & Y or the D-pad. The closest I got was Mupen's default setup, but I can't figure out what the Z and L buttons are mapped to, and I can't find any custom mapping area.
SuperN64
Settings>Input>Controller Not the toggle
triggers don't map tho
Closer...
chevyowner said:
SuperN64
Settings>Input>Controller Not the toggle
triggers don't map tho
Click to expand...
Click to collapse
I've managed to find the controller mapping area through dumb luck, and theoretically I've mapped them, but it seems like the changes aren't going into effect. I can see that all the buttons are mapped in the layout for the buttons, but when I actually play the game (LoZ: OoT), it's controlling the same way it was before I made any changes. (L & Z don't work, etc.) Frustrated!
nachokingp said:
I've managed to find the controller mapping area through dumb luck, and theoretically I've mapped them, but it seems like the changes aren't going into effect. I can see that all the buttons are mapped in the layout for the buttons, but when I actually play the game (LoZ: OoT), it's controlling the same way it was before I made any changes. (L & Z don't work, etc.) Frustrated!
Click to expand...
Click to collapse
Did you unmap the buttons that were already assigned? When you assign new buttons you are adding those to the default maybe causing conflict. Both supern64 and mupen work for me with all the buttons. When I first set them up I unmapped all the buttons then remapped them. I do have the mouse pointer turned off in the android settings. Not sure that matters.
Edit I was also using majoras mask, not sure that should matter though either.
Yup
I did unmap them. I can't get the L button to work, although I don't particularly care about that. I'm more concerned about the other buttons in general.
How do I switch the D pad and analog stick? My D pad is in the middle and the analog is to the left. Can someone help me with this issue
I have no problem mapping the triggers or the right stick in MegaN64. They were actually automatically mapped for me...
I can't get left thumb stick mapped either. Rift thumbstick automatically mapped as c-keys, d-pad mapped to movement. Left thumbstick = ignored. Cannot be mapped. Completely unusable.
So I found out that my new Galaxy S3 supports USB-OTG, and gamepads. Well I just so happened to have an old Xbox (original, not 360) controller lying around, so I cut off the xbox connector off the end of the cable, and replaced it with a USB cable (so very easy). It works, sort of. The buttons and dpad all work fine, but getting the analog sticks and triggers needs help from 3rd-party drivers/software.
Specifically, the issues I'm having are:
- There is absolutely no deadzone whatsoever in the Android OS gamepad drivers, so unless the game itself implements a dead zone, this makes mapping axes to functions very difficult. For example, the game Shadowgun: Deadzone, has gamepad support built in, but it requires that you map each individual button and axis; there are no premade configurations. So this means I have to manually map the left analog stick to move, and the right one to look, by tapping on the function, and then moving the appropriate stick. But the problem is that the moment I tap on a function to map it, it is instantly mapped to the trigger axis, because of how noisy/sensitive the trigger axis is, and the fact that there is no deadzone. There is no way around this. It is simply impossible to map any of the axes/buttons because of the lack of a deadzone.
- Some games, however, do come with premade gamepad configurations, so that I don't have to map each function individually. The problem is, these games usually don't allow any custom mapping, and they almost always get the axes wrong. For example, the game Dead Trigger will let you use your gamepad right away, without any options or configuration required. The game maps the left analog stick to move, just fine, but it maps up/down look to up/down on the right stick, and left/right look to the triggers?! And worse yet, the triggers are one combined axis, so this means that I am constantly spinning around in circles like a retarded chicken on a merry-go-round, unless I press and hold both triggers.
So what I need is an app that can A) Force a dead zone on the gamepad, and B) Re-map one axis to another axis.
Anyone know of any Android apps that can do this?
Oh, and they have to work on a non-rooted device, because my S3 is still under warranty, and even though I know I can just unroot it if I need to send it back, I'm still afraid that I might break it while rooted and be unable to unroot it because it is broken.
Thanks for any help!
Did you find a solution to this Problem? I'm having the same issue when using the Ouya Controller with another Android Device.