|
UIConsoleUsage
Instructions for using the Mupen64Plus-UI-Console front-end application.
Console OptionsAt startup, the mupen64plus program will look for a user configuration file called 'mupen64plus.cfg' (see FileLocations for more informations). If this file does not exist, it will be created and default settings will be written. If desired, an alternate config directory can be specified using the --configdir commandline option. Run 'mupen64plus --help' for a complete list of commandline options: $ mupen64plus --help
Usage: mupen64plus [parameter(s)] rom
Parameters:
--noosd : disable onscreen display
--osd : enable onscreen display
--fullscreen : use fullscreen display mode
--windowed : use windowed display mode
--resolution (res) : display resolution (640x480, 800x600, 1024x768, etc)
--nospeedlimit : disable core speed limiter (should be used with dummy audio plugin)
--cheats (cheat-spec) : enable or list cheat codes for the given rom file
--corelib (filepath) : use core library (filepath) (can be only filename or full path)
--configdir (dir) : force configation directory to (dir); should contain mupen64plus.conf
--datadir (dir) : search for shared data files (.ini files, languages, etc) in (dir)
--plugindir (dir) : search for plugins in (dir)
--sshotdir (dir) : set screenshot directory to (dir)
--gfx (plugin-spec) : use gfx plugin given by (plugin-spec)
--audio (plugin-spec) : use audio plugin given by (plugin-spec)
--input (plugin-spec) : use input plugin given by (plugin-spec)
--rsp (plugin-spec) : use rsp plugin given by (plugin-spec)
--emumode (mode) : set emu mode to: 0=Pure Interpreter 1=Interpreter 2=DynaRec
--testshots (list) : take screenshots at frames given in comma-separated (list), then quit
--set (param-spec) : set a configuration variable, format: ParamSection[ParamName]=Value
--core-compare-send : use the Core Comparison debugging feature, in data sending mode
--core-compare-recv : use the Core Comparison debugging feature, in data receiving mode
--nosaveoptions : do not save the given command-line options in configuration file
--verbose : print lots of information
--help : see this help message
(plugin-spec):
(pluginname) : filename (without path) of plugin to find in plugin directory
(pluginpath) : full path and filename of plugin
'dummy' : use dummy plugin
(cheat-spec):
'list' : show all of the available cheat codes
'all' : enable all of the available cheat codes
(codelist) : a comma-separated list of cheat code numbers to enable,
with dashes to use code variables (ex 1-2 to use cheat 1 option 2)ExemplesCheatsTo list the available cheats in the rom: mupen64plus --cheats list "/path/to/my/rom.v64" If there are cheats in the rom, you will get (in the output console): UI-Console: 3 cheat code(s) found for ROM 'MY ROM' 0: [Enable All Levels] (This is needed to be able to Play all Levels of the Game) 1: [Enable All Weapons] (This is needed to be able to Play with all Weapons of the Game) 2: etc... All you have to do to use this cheats is: mupen64plus --cheats 0,1,2 "/path/to/my/rom.v64" |
► Sign in to add a comment
I'm sorry but I literally have no clue how to access the gameshark codes and put them into games. I don't even know how to type any of these commands, I know there is the mupen64plus.cht file and I just know how to access the config file for mupen64plus. Someone please help I'm suprised no one else has mentioned this on the web yet lol I'm completely clueless, thanks all
Just run it from the command line with option '--cheats list my-rom-name.v64' to get a list of valid cheat codes for a particular ROM. Then start the game with the cheats you want by running '--cheats 1,3,6 my-rom-name.v64' for example for cheats numbered 1, 3, and 6.
Hey its jmwakashrek again, thanks for your answer Richard. But... lol I still don't get it. I can't type mupen64plus because it is not a known command. Do I write something before that, or should the terminal know this command? I tried typing mupen64plus --cheats list romname.z64 (I was already in the path). I also just tried ./run_rice.sh --cheats list romname.z64 . Sorry for being dumb but I just don't get it.
If you open the run_rice.sh file with a text editor, you'll see it's nothing more than a script that has the most important commands typed out already. The purpose is so that you don't have to type all that stuff manually in the shell. Without that script, you'd have to fully type out something like this...
./mupen64Plus.app/Contents/MacOS/mupen64plus --corelib ./mupen64Plus.app/Contents/MacOS/libmupen64plus.dylib --plugindir ./mupen64Plus.app/Contents/MacOS --gfx mupen64plus-video-rice romname.z64
...every time you want to run the emulator (in my case, I have OS X). That's a bit much, isn't it? The script types all that out for you. Try copying and entering those lines without the script (after changing directory to the Mupen64Plus folder), but before the rom name type "--cheats list" (without quotes).
If you see a symbol like $1 at the end of the script, change the 1 to an asterisk and that should allow it to accept more than one extra command, like both cheats and the rom instead of just one of them. That will allow you to type something like...
./run_rice.sh --cheats list romname.z64
...without having to manually input all the nonsense above. Alternatively, you could add the cheats part to the script.
There should really be an option to edit posts...
I learned that if you type "$@" at the end of each script (with quotes included) it will let you enter as many parameters as you want in conjunction with the script, before typing the rom name (the script normally won't let you). For example, you could type something like this:
./run_rice.sh --cheats 1,2,3 --resolution 800x600 "/path/to/my/rom with spaces everywhere.z64"
And it should work without a hitch.
How do you do this in Windows?
In response to my previous comment, in order to use these parameters, you create a shortcut to mupen64plus-ui-console.exe and then add the parameters you want to use in the target dialog box.
For example, if you want to enable cheats, you simply add --cheats <cheat number> and then drag your ROM to the shortcut. No need to add the path to your ROM (hooray for Windows!)