I did try installing mupen64plus-ui-python (which worked just fine after removing the specific version for pyqt from requirements.txt) but I could see no option to change key mappings. To put start on the "x-box button" and to put Z on RT (somehow after all these years it just feels "right" to put Z on that button). Left of the topright of the left joystickīutton(7) = the three-line settings button to the upper left of X and Yįor Mario64 I ended up changing: Z trig = axis(5+) For completeness: for my xbox controller the mappings I figured out: Button(0) = Aīutton(6) = the small settings button (with the two rectangles) to the top So in my case I had to look for Generic X-Box pad in InputAutoCfg.ini. You can see which controller config mupen is using in the printed output when you open a ROM: Input: N64 Controller #1: Using auto-config with SDL joystick 0 ('Generic X-Box pad')
This file is read when mupen64plus starts and the config used is written to the cfg file above. The file to edit is actually /usr/share/mupen64plus/InputAutoCfg.ini There is a config file in ~/.config/mupen64plus/mupen64plus.cfgīut it gets overwritten when starting mupen64plus. Just tried this (manjaro/kde) using mupen64plus 2.5.0. Sometimes it helps to look at the N64 controller layout to help figure out the parameters you intend to map. Using jstest, you should be able to figure out how you want to configure InputAutoCfg.ini to customize your input settings using the input event words. Save/write the changes to the file and the changes should be implemented when you next run mupen64plus.Īfter some changes, mine looks like this: Mine says Input: N64 Controller #1: Using auto-config with SDL joystick 0 ('Generic X-Box pad'). You can find out which device (controller) is being used by mupen by running mupen64plus from a command line terminal and finding the name of your controller. Vim /usr/share/games/mupen64plus/InputAutoCfg.ini. Open InputAutoCfg.ini in your preferred text editor. For me this is in the directory /usr/share/games/mupen64plus/InputAutoCfg.ini. Now you can press a button on your controller to see which axis or button it corresponds with.Īpplying custom controller config to mupen You will see a gui for numbered axes and buttons. For help with that, see Ubuntu Forums - Gaming & Leisure - HOWTO : Joystick/Gamepads under UbuntuĪssuming you have that set up and your joystick is already calibrated properly, all you need to do is run jstest-gtk /dev/input/js0 &, where js0 is the calibration file for the device you are currently testing. You will need the joystick calibration tool jscal to determine which button is which. Here is a solution anybody currently running mupen64plus, with or without a gui, should be able to use. Unfortunately, m64py was not a working solution for me and "trial and error" is too cumbersome. For each axis, this must be greater than the corresponding AnalogDeadzone value # An absolute value of the SDL joystick axis >= AnalogPeak will saturate the N64 controller axis value (at 80). # The minimum absolute value of the SDL analog joystick axis to move the N64 controller axis value from 0. # SDL joystick name (name check disabled if this is empty string) # Specifies which joystick is bound to this controller: -2=Keyboard/mouse, -1=Auto config, 0 or more= SDL Joystick number # If True, then mouse buttons may be used with this controller # Specifies which type of expansion pak is in the controller: 1=None, 2=Mem pak, 5=Rumble pak # Specifies whether this controller is 'plugged in' to the simulated N64 # Mupen64Plus SDL Input Plugin config parameter version number.
#Super mario 64 emulator best keyboard trial#
There I found the area where it talked about the joysticks and figured by trial and error that if I see on my controller a number (the buttons are numbered) I type that number minus one in the config file, and for the buttons I was not using I just leave it blank, as in "". The file I used to configure the controllers is: ~/.config/mupen64plus/mupen64plus.cfg
#Super mario 64 emulator best keyboard how to#
I myself couldn't run a GUI for mupen, so I ended up figuring out how to configuire it and run it in the Terminal.
0 kommentar(er)
