![]() I suspect it may be something in the usb order that might be tripping things up but due to everything being named I cant see why its a problem. I dont mind having to unplug the N64 controller (In fact I'd prefer it) when I "Back out" of N64 wheel on Hyperspin so that I can resume normal business with my xin mo. All without it changing random buttons on every other system that also runs through retroarch. How can I get retroarch to not only load the core remap file for each system BUT ALSO recognise which controller I want to use for that system. I dont even know where it has got the mapping from. But even on disconnect it has somehow managed to rip up all my other controls (all dedicated mapped to other cores, not default) for the xin mo on other machines. Well they are until you plug another controller in.Īfter faffing considerably I managed to get my fake N64 USB controller working just fine, saving only to the N64mupen core. Then you save to core remap options and all should be well. Then if you load a core and the buttons dont feel right you can use the remap options to further complicate your abstract mapping. You map your controller to its abstract retropad which is tricky to get your head round but it is doable. So you set up a nice default mapping by literally pressing the buttons and watching them map to the screen, and if it doesnt suit a machine, you just input for that machine and away you go. Its abstract layers upon layers, trying to map them over to what you want but it is doable. I have a xin mo controller as my main arcade controller but not so long ago managed to pick up one of those usb N64 controllers so I can "properly" set up the 64 just like it used to be (or as close as can be).Ĭonfiguring controllers on certain UI's such as retroarch can be a complete pain. Ive recently been setting up some systems and I am working my way through all of the ones that use some retroarch core as the emulator. It doesn't seem to like me.I'll ask here as its quite the mission to access and post a topic on retroarch forums directly. I think I am doing everything correctly? I was able to get Hyperspin and MD.emu to integrate fine, as well as every other emulator I am using except for Retroarch. It displays 1.2.2 in the bottom left corner of the screen. I am using the current version of Retroarch that is available to download from the Google Play Store. I have this line in my Sega CD.ini file:ĥ. If I use MD.emu with Hyperspin, the games load fine except for the lower compatibility.Ĥ. The XML database file was built from the actual files in the directory, and I have confirmed all file names are matched up with the actual files. Parameters=cores/genesis_plus_gx_libretro_android.soģ. Configure the following cores in Retroarch. The part about actually loading the HSA config somehow didnt sink in and I did always load the main config in Android/com. Install Hyperspin, Mupen64PLUS FZ, Yaba Sanshiro, PPSSPP from Playstore. This will allow you make the config file Hyperspin launches the same as the normal one Works in RetroArch 1.3.6 & 1.4.1 Hyperspin launched games use retroarch.cfg located in root data. As stated in the opening post, these are my lines in my Sega CD.ini file which I basically copied into there from the help thread on this forumĮxe=com.retroarch/.RetroActivityFuture Download the image to your PC with your favourite client (I used qbittorrent) Extract the contents to a folder called Hyperspin on the root of the USB drive. It is in the cores folder and it works fine to run the games in Retroarch in BIN/CUE format using the CUE files to load them.Ģ. I do have the Genesis Plus GX core installed.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |