Setting up C.T.R.L.R in RetroArch - M.O.J.O. General

Hi everyone!
I noticed that some of you are having problems getting the C.T.R.L.R to work with RetroArch. Here is what I did.
Go to Settings > Input and uncheck Configuration Autodetection > Enable. Scroll down and open Player 1 Custom Binds. For each button open the configuration menu, select Detect and press the appropriate button on your C.T.R.L.R in GameSmart mode. It's useful to continual switch between mouse mode for easily operating the configuration menu and GameSmart mode for assigning the single buttons.
At the end your configuration should look like this:
Up Button: Dpad Up
Down Button: Dpad Down
Left Button: Dpad Left
Right Button: Dpad Right
A Button: Button B
B Button: Button A
X Button: Button Y
Y Button: Button X
Start Button: Button Start
Select Button: Media Play Pause (see annotation below)
L1 Button: Button L1
R1 Button: Button R1
L2 Button: Unbound (see annotation below)
R2 Button: Unbound (see annotation below)
L3 Button: ThumbL
R3 Button: ThumbR
Better use one of the media buttons instead of the Back button for Select to be able to access the RetroArch GUI during gameplay if Settings > Input > Back behavior was set to GUI toggle.
The button setup menu doesn't recognize the L2 and R2 buttons. Nevertheless they work properly in cores which support them.
If you have got a second controller repeat this procedure with Player 2 Custom Binds.
Using analog sticks
Support for analog sticks depends on emulation cores. From the RetroArch GUI set Settings > Input Options > Device Type: Joypad w/ Analog and Analog D-pad Mode: Dual Analog. Then check the Core Options for a controller type option, for example Dualshock Analog Toggle: Enabled on Mednafen PSX or Pad 1 Type: Analog on PCSX ReARMed.
Unfortunately PCSX ReARMed only supports the left analog stick as an alternative for the DPAD and only for the first controller. Using both sticks equivalent to turning on the analog mode on an original PlayStation Dual Shock controller doesn't seem to work.
Issues
Currently I don't get the anolog sticks to work with emulation cores even if I set Settings > Input Options > Device Type: Joypad w/ Analog and Analog D-pad Mode: Dual Analog. If anyone has an idea please let me know.
Troubleshooting
Sometimes your second controller isn't recognized by emulation cores even if it works in the main menu. Quit RetroArch, restart it and start a game using your second controller. Now both controllers should work. Please note that not every core supports multiple controllers, for example bSNES does, SNES9x doesn't.

Kokosnuss said:
The button setup menu doesn't recognize the L2 and R2 buttons. Nevertheless they work properly in cores which support them.
Click to expand...
Click to collapse
Good thread, I don't use retroarch, I found it not as up to date as the main emu apps but it's a nice 'all in one' app
But re L2/R2, these are analog triggers and some emulators don't recognize them, switch the CTRLR to PC mode, it changes R2/L2 to digital and should work 'digitally'
re the 'anolog sticks' that's really strange search google, see if the emulator supports PS3/4, x360, etc analog sticks?
It could be limited (programmed) to only moga pads etc and hasn't (yet?) implemented google's controller standard.
Ask on their forums for google controller standard support.
There's many apps that haven't caught up, it's still newish 1-2years old now.

Just use the latest nightly build, it doesn't need to be configured
https://www.dropbox.com/sh/91sakv0qdyxjx9f/AAAKWBfDHBtIQtNfnp4rlyXea?dl=0

Thank you for your feedback.
@gwaldo
When I switch to PC mode the back button doesn't work as back button. Therefore I prefer using GameSmart mode.
@opiate81
I didn't have any luck trying nightlies so far. Will wait for the next stable release.

Okay, I found a solution for using analog sticks. See edited post.

Related

How to get LG Expo keys to work in FpseCE and MorphGear

Before you get too excited this isn't a fix to the key mapping issue, it is simply me explaining how I've set up the keys to make games be playable on both emulators. with this set up they do work pretty well though.
FpseCE
First of all your going to want a frameskip of 0. With the snapdragon processor I've found that for the games I've tried at least it just makes them slower to add a frameskip.
Now for the keys. First open up the phone and then push the top left of the screen to go into portrait mode with the keys open. Your going to want to set the controller type to dual shock. Once that's done go into multikey. Push buttons 1-8 in order and unselect any buttons that are already highlighted and in use. then go back to 1 and start setting up your keys. This is how I set up mine.
Mutikey PS Controller Key Expo Key
1 Square Left
2 Circle Right
3 Triangle Up
4 X Down
5 R1 Camera Button
6 L1 Applications Button
7 Start Space Bar
8 Select Backspace
For racing games I switch the X and the R1 button because for some reason every time I pushed another key while holding X it would make me press X again to go again. Switching those two keys fixes that problem.
If you want to try and set up it differently for a certain game here is a list of all the keys that work for the LG Expo. (Left, Right, Up, Down, Space Bar, Enter/Ok (two buttons act as the same entry), Backspace, Camera Button, Application Button, Volume Up, Volume down)
Then go out of mutikey by pushing the back button on the phone. Go back to the controller and push the down arrow to set up the analog stick. Click on the box below the left analog stick until it shows a PSP looking device with the screen lit.
Push back on your phone and go into screen mapping. I prefer the 5 by 3 grid. Tap on the middle left most spot and change the control to left analog stick, an L with a circle around it. Make sure the input type is the arrows pointing both ways meaning it will only stay pressed as long as you press it. Then go to icon and change it to a target looking icon with a circle and a circle around it.
Now you're ready to play. Make the game full screen again and now your screen is the analog stick. Anywhere on the screen will actually activate the analog stick. What I do is put my thumb under the image on the screen so I can check and see which way it is facing without lifting my thumb.
MorphGear
The keys that work with MorphGear are the same as with FpseCE and those are (Left, Right, Up, Down, Space Bar, Enter/Ok (two buttons act as the same entry), Backspace, Camera Button, Application Button, Volume Up, Volume down).
I only play GBA games with my phone, so for other systems you may need to set them up differently, although these should work the same for the GB, GBC, NES, and many SNES games if not some others.
For up, down, left, and right I use those same buttons on the keyboard. I then use the Camera Button, Application Button and OK buttons for A, B, and R in different variations depending on the game I'm playing. Then use Volume Up and Volume Down for Start and Select. I put the Space Bar as the L button, but I don't intend on playing games that use it for anything else than occasional use.
If you were to play games that consistently use the L button you could either use Ok and Space Bar for A and B and then use the Camera Button and Application Button for the R and L buttons. However many games would also require you to press A and B at the same time so you would probably have to switch the A and B and the Start and Select buttons. it would be a bit weird holding the phone to play games with the A and B at the volume keys (most of the reason I avoid games that require use of the L key), but it would be playable.
Well, I hope all this helps.
You had me pretty excited there for a minute. Thanks for the info though.
Thanks for your excellent post! Would it be possible for you to upload your fpseCE configuration file? I am having problems getting fpseCE working, every rom i load just exits the program...
thendless said:
Thanks for your excellent post! Would it be possible for you to upload your fpseCE configuration file? I am having problems getting fpseCE working, every rom i load just exits the program...
Click to expand...
Click to collapse
First of all it might just be the version of fpsece you're using. I had some issues with that myself for a bit. Make sure you're using fpsece 0.10. You can get that here.
http://perso.numericable.fr/schtruck/FpseCE_010.zip
I've also attached my fpse.ini file as well in case it isn't just the version you are using. You are still going to need to edit the keys for your games like I mentioned in my first post to get those properly working.

Nyxboard remote (XBMC)

Just a heads up for any XBMC fans with a Nyxboard remote - it works pretty well by default with the OUYA.
The Good:
- the power button suspends the Ouya (something I never got working with my old Linux htpc)
The Meh:
- the color buttons need to be remapped (they all send a "left arrow press")
- the back button needs to be remapped (it doesn't seem to send anything)
- the remote doesn't appear in the XBMC Input Devices/Peripherals submenu
Misc:
- If you're using any other android launcher (I'm using Nova a bit) the remote won't be detected by Android or XBMC until you start the OUYA launcher. It's strange, but also confirmed in the "official" OUYA developers forums.
I'm going to play around later with custom a custom xml config for remapping.

[Q] Mame on Mojo

Is there a setting that enables you to use the controller without having to use the screen controls as well? Seems like I have to use the screen controls for "coin" and then "start" with the controller. I can't seem to map "coin" and "start" to the controller in Mame. Thanks!
oldatarigamer said:
Is there a setting that enables you to use the controller without having to use the screen controls as well? Seems like I have to use the screen controls for "coin" and then "start" with the controller. I can't seem to map "coin" and "start" to the controller in Mame. Thanks!
Click to expand...
Click to collapse
You can assign coin and Start to the CTRLR - just use the settings screen of the emulator you're using to assign them. If you're running out of controls then I usually set Coin to the Play/Pause button of the media controls.

Mic and Home buttons on remote -> ZoomIn and ZoomOut

Hi everbody,
I was playing with a USB keyboard that I connected to my fireTV and I have noticed something that I haven't read in the forums yet.
- The key used by the FireTV remote control for Home button is the Multimedia Key for "ZoomOut" in the browser.
- And the Key that is used to trigger the Microphone corresponds to the "ZoomIn" in the browser.
Maybe these ones are useful to @rbox (I know that he has already the Xposed module to overwrite the Home button), but maybe the mic can be associated with Google Search instead. Or with the voice search in kodi. That way we get rid of the keyboard.
Or maybe they are useful to @elmerohueso to create another addon to map them.
On my side I just connected a flirc and I am programming it with power button, volume from my AVR, subtitles search, etc.
However, I love the fireTV remote and I believe that there is no real need for a keyboard if the voice funcionality can be replaced by a voice keyboard.

Call of Duty: Mobile with Joy-Con support?

Hi.
Is there any way to do this?
Apparently Call of Duty: Mobile requires a Dual Shock 4 or Xbox One controller in order to work. This defeats the purpose of playing it on a Switch. Which I'm ashamed to say, is a big reason I bought and installed Android on my Switch. To play CoD:M on it during down-time at work (I work night-shifts).
I was wondering, since this is a custom FW anyway, is there any way to trick it into thinking the Joy-Con controllers are actually Xbox One controllers? So it would be registered as such in Android as a whole? The Screenshot-button could be the Xbox-button. Many, if not most/all games with controller support, support Xbox One controllers. I see no downside to that.
If not, is there any working overlay program out there? I tried Mantis Gamepad Pro. l connected it to my PC and activated it. It found the Joy-Cons. I added CoD:M as a game. Started it.
Game started, I went into Practice Room in order to set up my overlay.
There's a semi-transparent green overlay-button in the top left corner, so I press it and try and add a button, and get told to "Press a Button". So I physically press a button on my Joy-Con, and that button pops up as a Virtual Button. I drag the VB over the icon on the screen indicating the action it does (let's say, physical button = RT, VB = dragged over Shoot-icon). Now this is working great, I'm placing the analog sticks, pushing all the buttons and placing them where I want them. It registers my buttons.
But when I close the settings by pressing the semi-transparent icon in the top left corner of my screen (the green icon is still there, but the button layout disappears) and actually try and PLAY the game, none of the buttons are registered when I press them. Nothing happens.
It's like.. so close, yet so far!
I think I have all the settings correct, and I've enabled the app to be on top of other applications or whatever.
If anyone has ANY idea how I can get CoD:M working on my Switch with lineage-17.1-20210510-UNOFFICIAL-foster_tab-signed, that would be awesome!
Thanks for ANY response! Anything helps!

Categories

Resources