Open GoogleCodeExporter opened 8 years ago
Remove CFG folder besides rom folder to return to default mappings. Right stick
is mapped to a,b,x,y because dual sticks games are using this bindings.
Example, robotron or smash tv. You have an option to change the default
mapping for thumbs. All other buttons are preconfigured on automap option.
Mame4droid uses a minimum set of buttons from mame, that is, left stick and
buttons a,b,x,y,r1,l1 ... This is fine for the touch layout emulation and it is
ok for compability across devices and controllers. To be able to support dual
stick games I'm doing some tricks like use the a,b,x,y buttons as right
stick. So yes, to can only use left stick, right stick for dual stick with the
trickery I have said and buttons a,b,x,y and two triggers.
Original comment by seleuco....@gmail.com
on 9 Aug 2013 at 11:51
What about games that doesn't use Dual sticks? Like Marvel VS Capcom Or World
Heroes, Games that uses 6 button input or 4 Button Input.
The a b x y l r buttons are all thats needed for MVC , but the triggers are
mapped too, and can use to map 3X punch Or 3X Kick Akin to Console Port (PS3 Or
Xbox) But can't cause there mapped to specific buttons already and Dunno how to
unmap it. (Left Trigger + B button = same map)
Sorry if I don't get what you said before, I was wondering if it was a problem
with the app, or just me, the Gui (App and Mame) are both confusing. Other than
that, Its a satisfying experience. Thanks for the emulator by the way.
Original comment by secretou...@gmail.com
on 10 Aug 2013 at 2:42
I dont understand when you says left button trigger + b button same map Left
trigger should be left trigger. Please delete cfg folder besides rom folder and
try again.
Original comment by seleuco....@gmail.com
on 10 Aug 2013 at 7:39
The Left Trigger And B button is the Same input button (Regardless of Gui
setting)
And I deleted the CFG Folder already, I am using the default mapping.
And the Right Trigger and Right Bumper is the same input.
Original comment by secretou...@gmail.com
on 10 Aug 2013 at 7:00
It's strange. I will take a look this week.
Original comment by seleuco....@gmail.com
on 11 Aug 2013 at 8:04
I have upload a new version to google play. Is it working now? Do a full
uninstall before updating...
Original comment by seleuco....@gmail.com
on 12 Aug 2013 at 8:19
Saw the update, Noticed the new Nvidia shield Auto detect Controller.
Nice update by the way, but now Trigger has same map as bumper.
No its not a problem, well not a huge one, just a concern.
Its more like a Xbox Controller, Ever played Street fighter on Xbox?
X = Low punch
Y = Med Punch
RB = Hard Punch
A = Low Kick
B = Med Kick
RT = Hard Kick
LB = 3X Punch
LT = 3X Kick
All I noticed is that The Right Bumper and Right Trigger is same map input. (On
the Nvidia Shield)
Simply, all I was asking is that the trigger buttons don't have the same
function as another already existing input.
Original comment by secretou...@gmail.com
on 12 Aug 2013 at 9:08
Heavily apologize for any inconvenience, or regard to hostility, no Im not
demanding anything, and I understand I didn't make the program and you don't
have to do anything about this, but it would be much appreciated.
Simply put, if The trigger buttons was independent (not mapped with other
buttons)
I can just use the Ingame Mame GUI to add the multi map buttons to use the 3X
Punch which is useful for Some Fighting games. (Marvel Vs Capcom, King of
Fighters)
Where super combos are easier.
All in all, still very impressive emulator for Android Platform.
Original comment by secretou...@gmail.com
on 12 Aug 2013 at 9:13
[deleted comment]
All suggestions are welcome.
Currently I have maximum mame buttons that I know I have in all devices ant
touch controller. That's means only l1 and r1 are passed to mame core.
That's why bumpers have the same values as triggers, but you can change in
automap options to be coin or start and other preconfigured values.
I'm not plan to add more buttons to mame core, becose I will add a lot
complexity and incompabilities for future net play support in different
devices.
Original comment by seleuco....@gmail.com
on 12 Aug 2013 at 10:17
Original issue reported on code.google.com by
secretou...@gmail.com
on 9 Aug 2013 at 9:26