RetroPad Binds section of RetroArch reset at each game launch.

Ares

I had been configuring the controls without opening an N64 game. I had assumed I had to make a subjective choice how to map the N64 buttons to their modern equivalents. It somehow didn't dawn on me that the emulator would have no way of knowing how I made those decisions. I didn't realize I could open an N64 game to get actual N64 labels for the controls so that I could see what I was doing. I guess I am overtired from all this. I have been trying so hard not to make any mistakes because I know you have no way of testing any of this properly. I guess I screwed up anyway. I am so sorry.

Linked below should be the correct layouts. I opened an N64 game in order to map things properly, then closed the N64 game down in order to map the select button:

https://purplemoonlight.net/upload_temp/ares.zip

The Z button is unbound on SDL because it didn't register. Also, with Xinput, I am seeing the D-Pad and Control Stick movements as showing up the same in the GUI. I'm not sure why that is.

Bizhawk

I have no idea why you are seeing duplicate buttons. Here are the screenshots of how they are being assigned in the GUI:

SDL:


And Xinput:


Maybe it is possible to load the config files on your own machine, even if you don't own the controller, and can see how that shows up in the settings.

Mupen64

Here are two config files for Mupen64 in which I have mapped the controller's select button to "Start" and all other buttons are unmapped:

https://purplemoonlight.net/upload_temp/Select.zip

Simple64

In SDL mode, the Z button fails to register in Simple64, Mupen64, and Ares. It only seems to register properly in SDL mode Bizhawk. It registers fine on all emulators in XInput mode. I'm not sure what's causing this, but wherever it affects the Z button, it affects the RZ button too. It may have something to do with them identifying themselves as axes instead of buttons, but I don't know.

I am so sorry I keep messing up. This should be simple. I don't know what's wrong with me.

Thanks a lot for your time & effort.

For information i will not bother configuring these emulators in sdl for which Z does not register, i guess for this controller xinput will be the way to go.

I'll look into all this later today ! Thanks

"Thank you so much for all the hard work put into this project! RetroBat is a fantastic tool for retro gaming enthusiasts, and it's greatly appreciated. If anyone is looking to show their appreciation in a fun way, a personalized thank you card can be a great idea. It's always nice to recognize the effort behind these awesome projects. Check out RetroBat here: https://retrobat.forumgaming.fr and consider sending a thank you to the team!"

Hello,

Please find enclosed an updated file for the n64controllers ==> https://drive.google.com/open?id=1RuMXYm46pkg5z-uy86IPQ-f_nsPRLgrr&usp=drive_fs

Luna Murasaki ==> can you try and see it that works (mostly in xinput mode) for the multiple emulators ?

Sorry for my late reply. I am dealing with a lot of personal problems that have me very emotionally and practically overwhelmed.

I'm not sure what to do with this file or how to test it. I'm also not sure what to test it on. Mario 64 won't let me test the L button or the control pad. If you could recommend a game that would let me test all the buttons quickly without me getting too deep into it I'd appreciate it.

This file should be placed in retrobat\system\resources\inputmapping (you already did that and tested in the past).

Then you put your controller in xinput mode and try to launch games from Retrobat with the different n64 emulatores

Well this is not going well.

I attempted to start Mario 64 in the various emulators. No matter what emulator I pick for it, it starts up in Retroarch. I thought maybe there was a bug that was ignoring game-specific settings, so I went to the per-system configuration in the menu and tried changing the preferred emulator there. It still always starts the game in Retroarch. I can say that in Retroarch, neither the SDL or XInput modes are working at all, but that may be because the same problem is ignoring my attempt to turn the Autoconfigure controllers option back on. I don't know.

And yeah, I realized too late that pasting in that json file was something you asked me to do before. I am just so tired that I am starting to get scrambled. I am sorry about that. I am sorry these problems keep causing me to fail to handle something so damn simple.

I don't know how to proceed at this point. What should I try?

I think you will need to share your emulatorlauncher.log file, as it's not normal that everything starts RetroArch

Created a fresh log where I changed the emulator back and forth for Mario 64. It doesn't seem to show anything that I can see. It just looks like I've selected to start Retroarch when I haven't.

Note the "button 30" thing is because I edited the config file to use that as the hotkey so that the hotkey wouldn't trigger. I don't believe it's related to this because I was able to change emulators just fine before with this done.

https://purplemoonlight.net/upload_temp/emulatorLauncher.log

I run MAME games on this and it is respecting my choice when I change to MAME2016 for specific games. So I'm not sure what the scope of this problem is. I will do more testing.

Okay, so it looks like the problem is happening solely to Mario 64. I can't seem to fix Mario 64, so I will go ahead and use Chameleon Twist for the test.

I have discovered more on the nature of the bug - if I explicitly tell it to launch a game in RetroArch, it will then launch the game in RetroArch forever, no matter what other emulator I try to set it to. I don't know if this is an actual bug in RetroBat or something related to my configuration. I was able to fully test Chameleon Twist by setting it to the RetroArch cores for the North American version of the game and trying the other emulators using the Japanese version of the game.

In RetroArch, the A button, L button, R button, Z button, and Start button function correctly. However, the B button doesn't do anything, the left C button functions as the B button, and the other C buttons don't do anything. I don't know a game to use with which to test the control pad - Chameleon Twist doesn't use it.

In all the other emulators I tested, the controller is entirely unresponsive.

At this point I have no choice but to greatly slow down the pace I'm working on this because I just have too many personal things stacked up that I have not been taking care of so I wouldn't recommend holding back the new release waiting on me to take care of this - I certainly don't want to be dealing with that kind of pressure. I am not ready to outright give up though - not yet. I'm getting close to it though.

Maybe someone would be willing to tell me where the configuration file is stored that contains the specific launch settings for each game. Then maybe I could delete the Mario 64 and Chameleon Twist entries and I'd at least be able to access those games properly again.

Hello,
Please do one by one, as it does autoconfigure exactly the same way as the files you sent me.

Let's start with retroarch, can you run a game from RetroBat by choosing Retroarch core and send me 2 files:
1) retroarch.cfg
2) emulatorlauncher.log

Regarding the bug you are talking about ==> please tell me with which game this happens and send also the file (retrobat\emulationstation\.emulationstation\es_settings.cfg)

The issue happens to any game where I set the game-specific settings to use RetroArch as the emulator. Once this has been done, it will then launch in RetroArch forever, regardless of which emulator I set it to use afterwards. If I haven't done that for a particular game yet, I can launch it with other emulators, but as soon as I select RetroArch as the emulator and start it, from then on it will only run in RetroArch.

Here are the three files you requested:
https://purplemoonlight.net/upload_temp/Files.zip

Hello,

Maybe you are confusing per-game settings and per-system settings...

Can you tell me which game has this issue ?

Currently, it is happening to Super Mario 64 and the North American version of Chameleon Twist.

I first noticed it was happening to Super Mario 64 - when I went to "Game Options/Favorite" and then "Advanced Game Options" and changed the emulator for that game, the setting seemed to have no effect - it would always launch in RetroArch no matter what.

I tried the North American Chameleon Twist. I was at first able to choose whatever emulator I wanted for it. Once I had selected RetroArch however, it then became just like Super Mario 64 - no matter what emulator I choose, it will now always start in RetroArch.

The Japanese version of Chameleon Twist lets me select an emulator just fine. I believe this is because I have yet to try selecting RetroArch. I believe that if I were to do that, it would start ignoring the emulator setting and always launch in RetroArch like the other two games, based on what I experienced with the North American Chameleon Twist.

Maybe check the gamelist.xml file in roms\n64 folder to ensure you did not force the core/emulator in there

Yes, the gamelist.xml file was what I was looking for earlier. But it doesn't seem to offer much in the way of an explanation. Here's an excerpt from it showing the three games:

https://purplemoonlight.net/upload_temp/GameSettings.txt

All three games are set to use Mupen64 as the emulator, but when I start Super Mario 64 or the North American Chameleon Twist, they start in RetroArch anyway. No matter what I set them to use, they always start in RetroArch. Only the Japanese Chameleon Twist is honoring this setting, and that's only because I have yet to specifically select RetroArch like I did with the North American Chameleon Twist and Mario 64. It seems that once that's been selected, the game is permanently locked to always use RetroArch. I have no idea what is going on or even how the whole system could "remember" which games are locked like this, since there doesn't seem to be any indication of it in the config.

I think you have a broken installation and you should reinstall Retrobat.