Custom Gamepad (and Touchpad) Layouts!

[Paul]

Sorry, the instructions no longer apply in the new front-end.  I'll update them.  You should be able to just unzip a layout somewhere, then point to that folder from the Settings->Input->Touchscreen->Custom layout folder (need to choose "Custom" for the Touchscreen layout option to enable it)

[jonjon]

Thanks for the reply. Just pointing the custom controller option to the right folder was the first thing I tried but on what ever build I was on at the time this wouldn't work.

... Works great now on rc6 though so thanks for the clarification

[wtdanceisthrough]

Hi there,

On my handset (Samsung Galaxy S3) I tend to find the "A" and "B" buttons are too close together - it is all too easy to press the wrong one or press nothing at all when you intended to press "B". Is it possible to get a layout where the controls are a bit more spaced out or does one already exist?

Also, I thought it would be useful to have a layout which perhaps only has the control stick and no other buttons but it is a lot bigger. It is currently quite difficult to make the precision moves required for walking across very thin platforms such as in 3D platformers like "Banjo Kazooie" - mostly because the control stick is small in the corner. If we had a layout we could perhaps switch to while in the middle of such a maneuver and switch back afterwards, we would be able to make these tiny adjustments required.

Thanks,
Adam.

[Paul]

I probably should make an XHDPI version of the virtual gamepad, since the small controls has been brought up before.  The difficulty is the "corner cases", where the app has to make a decision based on the screen resolution and dimensions, whether to use the tiny, small, medium, or large button images, and whether to use a tablet layout or a phone layout.  It still gets this wrong on some devices, and adding another choice to the mix increases the likelyhood of wrong choices being made.

That said, I can throw together a couple custom layouts that you can add manually.

[Paul]

A long-term solution for this problem will be to rework the code so that a single set of images (in xhdpi) are scaled down based on the screen density.  Then the only decision the app will have to make is whether to use the layout for tablets or for phones.  I'll probably do it by adding a new flag to the layout syntax, so that existing custom layouts won't stop working, but future ones can be designed for xhdpi and work on any device.

[wtdanceisthrough]

I probably should make an XHDPI version of the virtual gamepad, since the small controls has been brought up before.  The difficulty is the "corner cases", where the app has to make a decision based on the screen resolution and dimensions, whether to use the tiny, small, medium, or large button images, and whether to use a tablet layout or a phone layout.  It still gets this wrong on some devices, and adding another choice to the mix increases the likelyhood of wrong choices being made.

That said, I can throw together a couple custom layouts that you can add manually.

Hi Paul,

Any help you could provide would be much appreciated.

I am guessing any layouts you produce would also be backwards-compatible with earlier versions of the app? (see my other thread on button auto hold)

[Paul]

Yes, the syntax for the virtual gamepad layouts hasn't changed since Alpha testing, so currently all layouts will work on any version of the app.  Once I do add some new flags to the syntax at some point, then the new layouts that use it will not be backward compatible (but in your case, you won't need them to be -- since you are after button auto-hold behavior)

[DShiznit]

I just bought Mupen64+AE (after using the free one for half a year before then) and one of the things that attracted me most to it was the customizable controls. I've done scripted GUIs before in TGE, so this should be a cakewalk, but I'm wondering if there are any tools or guides that could help? I'm planning to make a tablet layout for Turok and other FPS games, with the C-buttons on the left and the analog on the right (I didn't see any like this skimming the topic but if there is one and I missed it feel free to let me know).

[littleguy]

See here.

The short answer is
 1. Copy one of the folders in <sdcard>/Android/data/paulscode.android.mupen64plus/skins/gamepads to some other folder on your sd card.
 2. In Mupen, go to Settings->Input->Touchscreen->Touchscreen layout and select 'Custom'.
 3. In the 'Custom layout folder' option below it, choose the new folder you created (the one containing pad.ini).
 4. In a text editor, open pad.ini and tweak the x= and y= values to reposition the button sets (values are in percent of screenwidth/height)
 5. Open Mupen and launch a game to see what the skin looks like.
 6. Repeat steps 4-5 until you have something that you like.

[williansti]

First hello to all, I would like to share with you, my contribution to the question of controls, hope you like it, I thought the style of ppsspp. I use a galaxy note 1





Download newbielink:http://www.mediafire.com/?x41bk7be8atzaxa [nonactive]

I could not believe mupen64ae I now see that the emulator is very good, I am your fan pauls, continue this excellent work, forgive me for mistakes I'm using translator...

greetings to all of Brazil!

[ThisIsNotMyName]

Can this be used to implement dead zones, or does that have to be coded in separately first?

[Paul]

Deadzones can be specified in a custom layout, yes.  Here is the relevant section from the documentation:

The first parameter "min" is the radius percentage that is is the "dead zone".  Touching within this zone will not move the control.  The next parameter "max" is the radius percentage where the control becomes "full throttle".  The final parameter "buff" is the radius percentage beyond "max" that is still part of the control.  Touching within this zone will be considered full throttle.  Touching outside this zone will not register as touching the control.  The values for "max" and "buff" should add up to at least 100, and can be higher than 100 if desired (be careful not to overlap with other buttons in the layout).

[ThisIsNotMyName]

Thank you. Not quite sure how I missed it the first time I read it.   

[Mikhail]

http://www.mediafire.com/file/u55pifc7w3aew5x/Shupad.zip

tidied up and packaged not to conflict with original

Any chance of a d-pad version?

[Zaion47]

Is it possible to get a clone of the N64oid on screen controls? I'm on the Galaxy S3