Lordmonkus

In all my experiences with Retroarch and controllers it automatically sets bindings without issues other than maybe some oddball layouts. Version 1.3.6 and earlier are the most confusing but I have noticed in the nightly builds (and presumably in the 1.4.0 release) the naming of the buttons in the RA setup are much more logically named. As far as the PS4 controller is concerned I did hook mine up a few nights ago to try it out with Retroarch and it detected it just fine. I did hook it up with the USB cable though and not wirelessly but it did detect and name it "wireless controller 1" (this was using the 1.3.6 stable install). The best information I can tell you for version 1.3.6 stable is that in the controller remapping if you look on the left hand side that refers to the core controller and they are named the same way that systems controller was named. So for example a Genesis 6 button controller would have A B C X Y Z Mode and Start. The button labels on the right hand column is named after an SNES pad layout but with the addition of analog sticks, 2 extra shoulder buttons and analog stick buttons. The buttons on the SNES pad would use the layout of: YX BA I did notice in the nightly and again presumably will be in the 1.4.0 stable that the naming on the right match up with the controller detected. I noticed this when trying out a nightly build and my Hori FC pad which is a Playstation controller and the buttons are labeled as such X,O Square and Triangle. I hope this makes some sort of sense

Ok I did a quick and dirty tutorial, I hope it helps out.

Did you try the FCEUMM core ? There is very little difference in the 2 cores in terms of compatibility.

Generally custom configs really are not necessary but it certainly is the most powerful and offers a ton of extra customization. One good example of where it comes in handy is in a core that emulates multiple systems with different needs such as the Genesis GX core. It does the Genesis, Master System, SG-1000 and GameGear and you may not want the exact same config and shader for all of them. So in this case you can have different custom configs for each of the emulated systems. But for cores that only do a single system like Nestopia or Snes9x I find there is very little need unless you want to have different shaders for different games, again something that I personally do not need so I just don't bother with.

Famicom games themselves will work just fine with Nestopia but the Disk System games will need a bios file. I need to go get some lunch right now but I will check back in when I am done and see if you made any progress and may I will do a quick tutorial video on this topic as well. I am 99% certain there is something small wrong here.

Ok now I see you have Famicom Disk System highlighted, is that the system you are trying to get working ? Have you tried the FCEUMM core ?

Indeed.

That's what it sounds like.

That is only because that is the actual name of my NES platform, yours may be different so make sure it matches what ever yours is named.

Can you post a screenshot of your Edit Emulator window ? Here is 2 screen shots, 1 of my Retroarch Edit Emulator window and one of my Associated Platforms window for Retroarch.

Try removing the -c "nestopia_libretro.cfg" and see if it loads.

Are you roms zipped ? If they are do you have several roms inside the zip file ?

It works fine with my Logitech F710 wireless controller but I have run into an issue where about 50% of the time when I exit a game I do not have control of BigBox until I press an arrow key on my keyboard which gives BB a "jolt" and the controller works again. I thought I had this issue solved a couple of days ago but it has come back up. I will have to try and different controller and see if that helps.

The PC-FX is like any other core in Retroarch use the mednafen_pcfx_libretro.dll core. I ran into issues with the PC-FX and it was a mix of finding the correct bios and correct format disk images.

Did you download the Nestopia core ? Is your core name correct in the command line parameters ? Is the platform name correct in the associated platforms window ? While this file I am attaching is not necessary to run games with the Nestopia core it does help with compatibility. It is just an xml file and contains no copyrighted data. Drop the file in your Retroarch \system folder like a bios file. NstDatabase.xml

Is your version of PinballFX2 and older one or is it up to date ? This does not work on older versions.

I have no idea in the world why you would need to do this sort of thing to fix it. I have never seen this issue before and I have used many builds of Retroarch going back to 1.2 including nightlies. I can almost guarantee the problem is in the command line parameters in Launchbox for Retroarch in your setups. Quadruple check your cores you have downloaded and the names of the cores you have in your associated platforms command line parameters. There have been times when I have been pulling my hair out trying to solve a problem with loading and even though I think every thing is right I almost always find a small typo.

It's in the core options for it.

Ahh you were using custom configs. While they can have their use and Brad likes them I personally never bother with them, I have just never had any use for them but that is just me and my setup. Yes, turn on per core settings and save configuration on exit. The pic below is how mine is setup in my stable install which I use for the bulk of my Retroarch emulation. I do have 2 other installs for specialty configs like Vulkan cores and testing..

In the 1.36 stable there is an option in the configuration menu to save per-core settings but in the nightlies and presumably in 1.4.0 release this has been changed so that with a core and a game loaded you can save out a config for that core in the core settings found in the quick menu.

Well if turning off v-sync fixes your speed issues and there is no screen tearing problems then that is a good thing, v-sync can cause input lag. Are you using the stable 1.3.6 build or one of the nightly builds ?

It's possible that your settings are not being saved when you close Retroarch. What version are you using ? 1.3.6 stable or a nightly build ? Are you using a 4K TV ? The reason I ask this is because someone was posting on the Retroarch forums about a very similar issue of speed and he was using a 4K TV. One of the devs (I think it was a dev) mentioned that some 4K TVs lock their refresh at 30 Hz and with V-Sync on it would slow the game to half.

I can guarantee that there is a setting in Retroarch that is causing your issues. What sort if display are you using ? Is it a 4K TV ? Try turning off V-Sync in the video settings.

Ok that CPU should be more than fast for the BSnes cores. Here is the guide: Part 2 is probably where you would want to start.

It's probably a certain setting. What sort of CPU are you using ? What's the speed of it ? I did a pretty big guide on Retroarch if you haven't checked it out I suggest giving it a look. Sound issues tend to be related to a slow than required CPU or too aggressive of settings for the CPU you have.