Erika Posted May 28, 2015 Posted May 28, 2015 Hey everyone, I had wanted my first post here to be something legitimately interesting but I guess I'll have to settle for a silly controller issue... Ugh. Basically, I've got an XBOX 360 wireless controller working fine with RetroArch, except that as it stands, pressing the large XBOX button in the middle of the controller toggles the menu off and on. All I want to do is remove this functionality, but I can't for the life of me figure out how. In the menu under settings, Input Options, Menu Toggle, it reads: Auto: (10 btn) Key: (f1). I want to keep the f1, but remove the 10 btn input. It can be changed to other inputs on the controller, but not removed. I tried navigating to the RetroArch config CFG file for the system in question (Sega Genesis) and making sure that input_menu_toggle_btn = "nul" was set, and I did the same thing in the main retroarch.CFG file, but it has absolutely zero effect. I even tried navigating to the autoconfig folder and going through any CFG file with XBOX or 360 in the name to change something there, but nothing had any effect. It seems like there is some overall automatic setting somewhere that is superseding any changes I make, but I can't figure out where on earth that file is. In the main RetroArch CFG file there is a line that reads, "joypad_autoconfig_dir" but the field is blank. How do I solve this issue? I've only been playing with Hyperspin/RetroArch for a couple weeks, so I guess I'm just not skilled enough to figure this out on my own, haha. Any help will be greatly appreciated!
Awakened Posted May 28, 2015 Posted May 28, 2015 Setting input_autodetect_enable = "false" in your main config should do it. You might have to remap all your controls manually with that off though. And pressing Start when highlighting a mapping should clear it.
Erika Posted May 28, 2015 Author Posted May 28, 2015 Thank you so much! That did it. I set the input auto detect to false in the main config, and the system config. I did have to map the controller again, but that was no problem at all. Everything seems to be in order now! Thank you!
andlat Posted May 28, 2015 Posted May 28, 2015 I know this isn't directly related, but I'm just curious if you use any particular controller for those games with an atypical number of input buttons. (I'm looking at you, N64) I already have N64 controllers and a PC adapter, I'd just... like a more elegant solution I suppose.
Erika Posted May 28, 2015 Author Posted May 28, 2015 Honestly, I haven't setup N64 yet, so I haven't played with the different possibilities to see what works best on a wireless xbox360 controller. The main issue seems to be the placement of the 4 yellow C buttons on the N64 controller. I've come up with two different setups for this. The first option is to map those C buttons in place of the D pad on the 360 controller. The benefit to this is that most games use them for camera controls, or secondary functions (like equipping an item). The downsides are that you have flipped the placement of the buttons in comparison to the original N64 controller, and you lose the ability to use the D pad (although, I hardly ever remember using the D pad back when I played N64). The second option, is to map the 4 different C buttons to the right analog stick directions. This seems to be most people's preferred method. The benefit to this is that you maintain a similar button layout to the original N64 (where most people control the single analog stick with their left thumb, and move their right thumb around to hit different buttons... Or in this case, different buttons and the right analog stick). The downside to this is that the accuracy of your inputs may be reduced by using the analog stick. I haven't tried it out yet, so I'm not sure. I'm hoping that when I do some play testing with different configs, it will become apparent what works best... But it may end up being a compromise in the end either way. We'll see, I guess.
newoski Posted May 28, 2015 Posted May 28, 2015 Hi, I didn't read through everyone's posts, but I can provide a 100% working solution to the XBOX 360 / Guide button UNmapping question: In your configs, locate the following line: input_player1_l_btn = highlight that entire line, including anything after the equals sign, and replace it with: input_player1_l_btn = "99" There is no button "99" on an XBOX controller, therefore, the XBOX/guide button is mapped to a nonexistent function and functionally unmapped. Let me know if you have any questions
Recommended Posts
Archived
This topic is now archived and is closed to further replies.