![]() ![]() So basically to sum things up I can play n64 no problem straight from retroarch and able to enter and exit the config menu, but if I launch a game from hyperspin and try to access the retroarch menu retroarch stops working. Mupen64plus works on my shield TV no problem and its the downloaded core from retroarch. I've read that some say it works some say it doesn't. If you want to change a certain key or delete. After loading a game, go to the RetroArchs menu to make changes in the Core Options (set core specific input options, cheats, change shader settings, etc). I've been reading around and not sure if it is due to mupen64plus. When mapping keys on your controller in RetroArch, you do not have the option of editing one or several keys. I was able to remap the controller for NES, but when I hit the shield button to remap the config for the N64 retroarch stops working and I get kicked back to the hyperspin menu. SNES works great didn't Ned to do anything to it, but didn't like the placement of A and B for both the NES and N64. I thought I'd do some fine tunning and remap the controller scheme. If the virtual buttons you're setting on the per-core input screen in the quickmenu. I was able to successfully get the NES, SNES, and N64 in working order with the box art everything. The important thing is to understand conceptually is that first you bind your physical controller to various 'virtual buttons' (called 'RetroPad' I think) in the main retroarch config, and then bind those virtual buttons to console buttons on a per-core basis. For RetroArch cores, you can create your own Game Controller mapping for the game. So this weekend I was able to install and configure hyperspin and retroarch. Go to Emulation -> Configuration (Citra -> Preferences on MacOS) -> General, set your Emulation Speed slider to your desired speed and disable Use Alternate. To access the Emulator, you can go in the Retrobat System in the System View. Thanks to you guys I am able to enjoy retro gaming on my shield TV. I can also avoid using the controller in the OS and in RetroArch menu, so it’s still available to the core when emulation starts. Unplugging/plugging back the controller makes it work. You may also have to open up the controller config file itself to add a line that maps the Xbox guide button to the home button on the Switch controller. Hello everyone, first time here on the forums and I would like to say everyone has done an awesome job in creating hyperspin and the tutorials on how to configure it. Long story short: looks like RetroArch can’t find the controller if it’s used in the OS, and the core can’t find it if it’s used in the menu. RetroArch will see the Switch Pro controller as a 360 controller, so you'll have to change the mapping for it manually to get the face buttons line up. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |