Tutorial Added: Install Mupen64Plus 1.99.3
We’ve added a new tutorial on how to install and use the latest version of Mupen64Plus (1.99.3), which was released this past week.
Because MP64+ runs from the command line (Terminal), it’s a little tricky to get working–but don’t worry: we’ve made it really easy for you to start playing games. All you have to do is drag a rom file onto our Mupen64Plus Game Launcher, and you’re good to go!
If you’d like to learn how to install Mupen64Plus 1.99.3 (the best N64 emulator for your Mac), set up our game launcher, and more, check out our Mupen64Plus page!
If you have trouble with installation or set-up, or if you have any questions or comments at all, leave a comment below and we’ll get back to you as soon as we can.
I am having trouble with the game launcher app part of the tutorial; whenever I attempt to click on the launcher, an error message comes up that says “The action “Watch Me Do” encountered an error. Check the action’s properties and try running the workflow again.” Any idea how to correct this? Thanks
Hi Nick,
Thanks for letting me know about that error. I’ve fixed up the launcher and replaced all of the “Watch Me Do” bits with AppleScript, and I’ve uploaded the newer version at the launching games page. Would you be able to try out this version to see if it works? Thank-you again for your feedback; it was very helpful.
John
Yeah, I think that fixed it up, I’m now able to just drag and drop ROM files onto the launcher with no issue. However, I have another question – is it possible to edit keyboard configuration, and if so, how would I go about doing so? Thanks again
That’s good news! I heard from a few other people that the launcher wasn’t working properly, but I wasn’t sure why it wasn’t. I’m pleased to hear that it’s working as I planned it would.
You can change the default keyboard configuration. Open Terminal and type “open -a TextEdit /Applications/Mupen64Plus/mupen64plus.app/Contents/Resources/InputAutoCfg.ini”, then press Return. This will open up the configuration file if your Mupen64Plus files are in a folder called Mupen64Plus in your Applications folder.
If you don’t want to use the terminal, go to Applications/Mupen64Plus, right-click on mupen64plus.app (the .app part might might not be visible) and choose Show Package Contents, then go Contents/Resources, right-click on InputAutoCfg.ini and select Open With -> TextEdit.
The first group of lines in that file are the default keyboard bindings. The N64 controller key is listed on the left, and then a JavaScript keycode is listed as key(xx). You can check out this site for a list of JavaScript key codes, and the page has a handy feature that shows you a key’s code when you press that key.
Now, all you need to do is change the key codes to your desired keys. Let me know if this makes sense and if it works for you.
The Mupen64Plus page on keyboard shortcuts and default mappings is worth checking out if you’d like to see what the default configuration looks like on a keyboard.
Following your directions, I was easily able to go in and change my keyboard configuration to what I wanted. However, after saving my changes and whatnot, when I booted up a ROM, my controls schemes were not applied. Did I skip a step?
Thanks for the speedy responses by the way, very helpful
Hmm, so close. II thought that I had it figured out, but it seems as though Mupen64Plus overwrites the changes once the rom is closed. I changed a key and it worked, but then it reverted once I opened a rom another time. I’ll see if I can figure something out.
You caught me on a good day for replies, that’s for sure! Can you tell that I’m putting off an essay?
Haha yeah man I feel you, I’m putting off studying for a COMM exam. But yea, thanks for your help, and if you figure anything out, get back at me.
I might’ve found something: I changed “plugin = 2” to “plugin = 1” in the InputAutoCfg.ini file. It seems to be keeping my changes, even after opening and closing multiple roms. Let me know if that works for you (if you can pry yourself from that enthralling COMM studying).
So after going in and changing the plugin to 2, the problem was still there. However, it seems that there is some other interfering factor, because I have noticed that the default controls are not functioning either. As far as I can tell, the only functioning keys upon running any given ROM are the return key, the arrow keys, and the various controls for the emulation (like pause, ff, volume control, etc). It seems that I dont even have an A or B button, definitely not corresponding to the given Mupen64+ controls. Any suggestions?
Actually, I reinstalled the program and retraced my steps in order to reset everything to default, and found that upon launching a ROM, the controls once again were able to function as stated on the program site. But then as I went in to edit the configuration, as I tried before, it didn’t work when trying to play the game. So i suspect my tinkering with the control scheme is in conflict with something else, perhaps the core parameter commands, and thus my setup just won’t function. Do you think this is probable, and how would I go about changing those core parameter commands?
Hmm. I am able to edit the InputAutoConfig.ini file, save it, and use it without a problem. Whatever was reverting before doesn’t seem to be doing it now. (I also found out that “plugin = 2″ just means that a memory pak is plugged in; 1 means that nothing is.)
I took a look around the main Mupen64Plus configuration file (mupen64plus.cfg, located in “~/.config/mupen64plus”), and I can’t see anything that would override your changes to the InputAutoConfig.ini file.
It might be the case that InputAutoConfig.ini isn’t saving properly. Could you open up InputAutoConfig.ini, change a key, close the file, then open it again to see if the change was kept?
What’s odd is that my changes do save every time I tinker with them, it’s just that they aren’t applied when opening up a ROM. But it doesn’t revert to the original default controls either, like I mentioned before the only keys that work are Return and my arrow keys, in addition to the basic emulation program functions. I have tried changing up my keyboard input, but nothing I change it to seems to work. What do you think?
If this helps at all, this is the section of the terminal reading that concerns input settings:
Input Warning: No joysticks/controllers found
Input: Forcing keyboard input for N64 controller #1
Input: Using auto-configuration for device ‘Keyboard’
Input: Mupen64Plus SDL Input Plugin version 1.99.3 initialized.
Basically I’m trying to map the directional movement keys to my left hand, by using either W,A,S,D, or Z,control,option,command, but neither seem to be working. I also aim to map the other buttons to my right hand, but that also is not working…
That terminal output is normal, so I’m not sure what the problem is. It must be a problem with how Mupen64Plus is reading the InputAutoConfig.ini. What version of OS X are you running? It’s working fine for me under Snow Leopard, but I haven’t tried it for Leopard. Some of the Mupen64Plus developers are active on a forum at EmuTalk.net, and they might have a better idea of what’s going on. They’ve helped me with a couple of things already, and they’re pretty quick. Maybe they have a COMM exam coming up, too.
Well I have the input settings back to their default settings, and it is functioning. However, comparing with that site you sent (that showed key codes for each stroke), I noticed that the settings listed in the InputAutoConfig.ini file do not correspond; i.e, the W,A,S,D (keys that work in default settings as a directional pad) keystrokes, when edited into the actual key codes of W,A,S,D (as shown on that website) do not function. Perhaps there is a different javascript code for keystrokes on OSX, but I don’t think that is the case. Hopefullly what I just said makes some sense, but let me know if it didn’t haha
This is a pickle. When I tested it I switched the Start button from Return to Space, and it might’ve worked because that key code is a common one. I didn’t think of trying out the W, A, S, D keys. The d-pad keys are by default number pad keys (Mac keyboards haven’t had one in years), even though they were showing as W, A, S, and D on the Mupen64Plus page, so you’re right-on there.
Something’s definitely strange with those keys. I mapped the A button onto the “a” key, and when I pressed “a”, it acted like I pressed Left.
It does seem as though something is overriding those keys being remapped. Looks like we’d better let the folks at Mupen64Plus know!
Alright, yeah I saw the comment you left on their board, thanks. I’ll check back there every once in a while to see if anyone responded. I’ve been tinkering with it a bit more, but still no progress. But I have one other question – Is it possible to run Mupen64Plus at fullscreen? I found the code.google.com site that the keycode for this is alt-enter, but that didn’t work for me.
I’ll keep an eye on things, too. It is possible to get Mupen64Plus running fullscreen. Go to the terminal and type in
open -a TextEdit ~/.config/mupen64plus/mupen64plus.cfgand press “Return”. That should open up a text file. Scroll down until you see “[Video-General]“, then you can change the default resolution and whether you want to run fullscreen or windowed. I haven’t tried it at fullscreen, but I assume it works. Changing the resolution works properly for me.Well good sir, I finally was able to map the keys the way I wanted them. Turns out the mac osx char keycodes are indeed different, so I had to use a program I found online to spit back the codes for my keystrokes. It is called “Full Key Codes”, and I found it here: http://www.versiontracker.com/dyn/moreinfo/macosx/21215. Using that, I was able to first edit the InputAutoCfg.ini file to my desired setup. However, it then conflicted with the core emulation settings, so I went into that file that you showed me in your last post (using the terminal command) and edited those as well, so now everything is set. Finally. Thanks much for your help, couldn’t have done it without you. Also, hopefully this could help future versions of Mupen64Plus for OSX. Let me know if this helps
Thanks for letting me know; that’s very good news! Would you be interested in checking out a basic GUI for Mupen64Plus I put together today? It’s an application that lets you choose window resolution, whether to run fullscreen, and a button to open a rom file:
http://speedofmac.com/blog/wp-content/uploads/2010/02/som_mp64+_gui.png
Let me know!
Yeah dude I’m down to check it out. But I downloaded it from that email you sent me, and every time I try to open it, the application quits unexpectedly, and I can’t get it to relaunch. Is there a special way I’m supposed to open it?
Hmm, that’s very strange. What operating system are you using? I build it for Snow Leopard, I think, which may’ve been a little presumptuous on my part. Check out http://speedofmac.com/speedofmac_mp64+_gui_test.html and see if that one works for you.
I tried that one out too, same result. And you’re right, it likely is an OS issue, I’m currently running on 10.5.8. Can anything be done to make the GUI more accessible?
The GUI launcher quits unexpectedly as soon as I attempt to run it. I’m on 10.5.8. I put the launcher in the Mupen64Plus folder. Is there a fix for this?
Thanks.
Also: Is it somehow possible to use a joystick with this? I have a ps2-controller adaptor that I use with other emulators – it would be great to be able to use that with the n64.
Mupen64Plus does work for Leopard, but unfortunately, the SpeedofMac MP64+ Launcher only works for Snow Leopard. If you’re looking for something for Leopard, check out Mike’s code above. If you aren’t sure what to do with it, take a look at http://macscene.net/component/kunena/75-emulation/506-mupen64plus-n64-emulator.html?limit=20&start=20#592.
All that you need to do to use a joystick is plug it in and cross your fingers. Mupen64Plus 1.99.3 comes with automatic gamepad configuration, so if it recognises your game pad, it will work automatically. If it doesn’t, take a look at http://code.google.com/p/mupen64plus/wiki/ControllerSetup.
Thanks for the speedy reply, man! I’ll report back if I need any more help with this. :]
I have followed all the proper instructors and everytime I attempt to load speedofmac or mupen64plus it says that the application has quit unexpectedly and I have no idea why. I am on a not very old macbook pro so I have no idea what could be the issue. My friend uses Mupen64 on his same macbook pro and has no problems.
I’m not sure exactly the problem is. Are you running Snow Leopard?
I followed your instructions to change controls for Mupen64Plus in the Terminal, and I downloaded the program with the Mac OSX key codes. I was wondering if it’s possible to change the keys that control the analog stick? I’m looking at the list of controller buttons and can’t figure out what the analog stick is…I’m a total noob sorry. This is the list of buttons, which one is the analog stick? The x axis/y axis?
[Keyboard]
plugged = True
plugin = 2
mouse = False
DPad R = key(100)
DPad L = key(97)
DPad D = key(115)
DPad U = key(119)
Start = key(13)
Z Trig = key(122)
B Button = key(306)
A Button = key(304)
C Button R = key(108)
C Button L = key(106)
C Button D = key(107)
C Button U = key(105)
R Trig = key(99)
L Trig = key(120)
Mempak switch = key(44)
Rumblepak switch = key(46)
X Axis = key(276,275)
Y Axis = key(273,274)
thanks!
No need to apologise! The X- and Y-axes together make the analog stick. The two keys for X are probably left then right, and the two keys for Y are probably up then down. Let us know if you need anything else!
I made the changes and saved the InputAutoCfg.ini file, but nothing changed when I opened the emulator again. I’m using the mac key codes, and I’m running OSX 10.6.4.
I saw in your old posts that one person mentioned having to change another file Mupen64Plus.cfg (opened by entering “open -a TextEdit ~/.config/mupen64plus/mupen64plus.cfg” into the terminal?) before the keyboard configurations went into effect? I opened this file also but i’m not sure what to change in the core settings. Is there another step I’m missing? thanks!
Never mind, figured it out myself, thanks anyway for the emualator and launcher program!
You’re very welcome for the launcher, but I can’t take any credit for the emulator! The good folks at Mupen64Plus are doing all the hard work; I’m just helping to spread the good word!
After a little bit of trial and error (and reading stuff online), I got my 360 controller working, but I would like to have the keyboard work as controller 2. I can’t figure out a way to do this. is it even possible to do?
Good question! I’ll take a look tomorrow when I have some time.