@mitu That's how I originally started out and it didn't work. I have weeks of work into this image now and don't want to wipe it out on a whim until I know that every avenue has been explored. And as I said earlier, it's happening on multiple different images.

Thanks, I'll try that. It sounds like it is basically a bug since it should automatically invert an axis if I map the controls reversed. Some people want to flip joysticks around and use them left-handed, so the software shouldn't really assume a "correct" orientation.

@RetroNerdman Nope, you go there : https://www.bountysource.com/issues/69769485-feature-request-input-mapper-macros . Also having a github account to reply "i opened a bounty" to this issue is a good idea though.

@Erdrick said in Unable to Configure Controller: My hunch is since I configured it for a keyboard and nothing else, he needs a keyboard to select input configuration and it should work from there. If you configured a keyboard as controller in ES, I think the initial controller configuration screen would not show If that's the case - and he gets the normal ES system carousel - then he'll not be able to configure the controller on 1st boot. He would, indeed, need a keyboard.

ok i tried it. This is my config. But it didnt work. my idea for the select Button is to push the eft and right shoulder button at the same time DPad U = hat(0 Up) DPad D = hat(0 Down) DPad L = hat(0 Left) DPad R = hat(0 Right) Start = button(9) Z Trig = button(7) A Button = button(6) B Button = button(8) C Button U = button(0) C Button D = button(2) C Button L = button(3) C Button R = button(1) Y Axis = axis(1-,1+) X Axis = axis(0-,0+) R Trig = button(5) L Trig = button(4) Select = button(4) button(5)

Thank you for all the guidance. It appears all is working well.

So I got it to work. (In ES input) After I choose X as left shoulder and Z and right shoulder, I then had to assign the left and right bumpers on the controller as left trigger and right trigger. Before I was skipping these on the controller due to them being assigned to X and Z. All working fine now :)

I found the problem. Mame seems to define a controller + a keyboard as possible inputs. Since my controller is a device that is mapped through RetroPad the event gets fired twice: once through the keyboard emulation and once through RetroPad. If the mapping is even different in the retroarch.cfg in can cause some strange events overlapping each other. Solution: I changed the MAME input configuration to only receive one input (RetroPad). That solved it :)

Thanks for you answer! I didn't know about the different emulators but I was using Mupen64plus which has his own config... I tried lr-mupen64plus but the cinematics appears black sometimes and the game crashed a few times... So a (re)switch on Mupen64plus. Just in case someone has the same issue I drop here the configuration issue I had: In the config file (/opt/retropie/configs/from_retropie/configs/n64/mupen64plus.cfg) I had this line: # Joystick event string for stopping the emulator Joy Mapping Stop = "J1B10/B9" The combination B10 (hotkeys) and B9 (start) seems to be ok for me BUT my controller was J0 not J1. It fix the "stop emulator" command. Now I have to check for the load/save state commands. Thanks again for you answer. It really helped me :-)

Thanks for this info, glad you brought this up, got it running thanks. I can use my virtual keyboard to type on my desktop now :)

@coloq said in N64 button mapping woes: So... ... still having the issue despite what documentation says I should do... As I mentioned before, if you map the physical “a” button to the virtual “b” button and the physical “b” button to the virtual “y” button it will work as you want.

@thejester Don't enable config save on exit' in RetroArch, it usually messes up your controls. Instead, configure the gamepad in Emulationstation and if you want to fine tune your controls, then use the RGUI to re-map the controller and choose Core Remapping menu to save it per core or game/rom. Also, when you have a problem unrelated to the topic at hand, don't just hijack it with your questions/problems, just open a new topic instead.

@johnny5126 I don't think so, how would the system choose which action you intend to perform when you press the key ? If the key acts as a toggle (run/stop), then it might work, but otherwise I don't think it's possible.

@johnny5126 I am new to Vice having only installed it over the weekend. The video tutorial above that I used to map my joystick encouraged me to Save current settings, Save hotkeys and Save joystick map each time I made a new mapping. I followed this advice and when I looked at the Vice config files in /opt/retropie/configs/c64, I noticed that changes were only being made to sdl-joymap-C64.vjm and not sdl-hotkey-C64.vkm which was the same as when first created. For your maps to the virtual keyboard, for example, you should choose Save joystick map for them to persist. You can check this by looking at sdl-joymap-C64.vjm and you should see a line like 0 1 0 5 Virtual keyboard.

@johnny5126 Both have their advantages and disadvantages. If I were faced with only having one, I'd probably choose a USB HID-compliant controller interface, as it could still be key-mapped later if need be.

Doesnt look like atari800 emulation has robust input mapping. But read more here? https://retropie.org.uk/docs/Atari-800-and-5200