Manual

From DeSmuME
(Difference between revisions)
Jump to: navigation, search
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
= DeSmuME Platform Specific Manual's =
+
== DeSmuME Documentation Bonus YOU MUST READ ME ==
 +
You may oftentimes find more up to date information in the [[faq]]. Better check there also.
 +
 
 +
== DeSmuME Platform Specific Manuals ==
 
DeSmuME places responsibility on the developers of each port to expose emulation features in a way that is tuned to the needs of that platform. As a consequence, some ports are able to move well ahead of the others. Conversely, some ports are far behind some others. As a consequence, some behaviours and menu structures are different in each port.  Therefore, the decision was made to create separate manuals for each port as well: when a specific port is changed, only the manual for that specific port needs to be altered.
 
DeSmuME places responsibility on the developers of each port to expose emulation features in a way that is tuned to the needs of that platform. As a consequence, some ports are able to move well ahead of the others. Conversely, some ports are far behind some others. As a consequence, some behaviours and menu structures are different in each port.  Therefore, the decision was made to create separate manuals for each port as well: when a specific port is changed, only the manual for that specific port needs to be altered.
  
Line 14: Line 17:
 
[[DeSmuME Manual for the Macintosh port]]
 
[[DeSmuME Manual for the Macintosh port]]
  
= DeSmuME Common command line arguments =
+
== DeSmuME Common command line arguments ==
 
The GTK+ and windows ports share common command line arguments. We are trying slowly to move over to a common command line handling engine. The commandline arguments for these platforms are described here:
 
The GTK+ and windows ports share common command line arguments. We are trying slowly to move over to a common command line handling engine. The commandline arguments for these platforms are described here:
  
Line 35: Line 38:
 
Requests cflash in gbaslot with filesystem rooted at this path
 
Requests cflash in gbaslot with filesystem rooted at this path
  
=== --single-core [win] ===
+
=== --bios-arm9=BIOS_ARM9_PATH [gtk,win] ===  
Requests that the emulator be run in single-core mode, with somewhat degraded usability in the area of OSD. This will automatically be the case on systems with only one CPU core, but this option will be useful for testing it.
+
Specifies a path to an arm9 bios which will be used
 +
 
 +
=== --bios-arm7=BIOS_ARM9_PATH [gtk,win] ===
 +
Specifies a path to an arm7 bios which will be used
 +
 
 +
=== --bios-swi=BIOS_SWI [gtk,win] ===
 +
Set to 1 to enable the emulation of SWI via the provided bios files, which I hope you have provided with the above options. (default 0)
 +
 
 +
=== --num-cores=NUM [win] ===
 +
Overrides the emulator's autodetection for number of processors. Presently, any system with more than one core (this may inadvertantly include singlecore systems with hyperthreading, but I can't test it) will operate with somewhat reduced OSD functionality, with lower quality and no asynchronous composition. In the future, other optimizations will require higher numbers of cores (optimizations for quad-core are planned, but it won't be too impressive)
  
 
=== --scanline-filter-a=NUM [win] ===
 
=== --scanline-filter-a=NUM [win] ===
Line 98: Line 110:
 
=== -v, --version [gtk] ===  
 
=== -v, --version [gtk] ===  
 
Show version of program.
 
Show version of program.
 +
 +
=== --nojoy=1 [gtk] ===
 +
Skips joystick initialization (for folks with laptops that have accelerometers for joysticks)

Latest revision as of 04:39, 20 December 2010

Contents

DeSmuME Documentation Bonus YOU MUST READ ME

You may oftentimes find more up to date information in the faq. Better check there also.

DeSmuME Platform Specific Manuals

DeSmuME places responsibility on the developers of each port to expose emulation features in a way that is tuned to the needs of that platform. As a consequence, some ports are able to move well ahead of the others. Conversely, some ports are far behind some others. As a consequence, some behaviours and menu structures are different in each port. Therefore, the decision was made to create separate manuals for each port as well: when a specific port is changed, only the manual for that specific port needs to be altered.

 

DeSmuME Manual for the Windows port

DeSmuME Manual for the Linux GTK+ port

DeSmuME Manual for the Linux Glade port

DeSmuME Manual for the Linux command line port

DeSmuME Manual for the Macintosh port

DeSmuME Common command line arguments

The GTK+ and windows ports share common command line arguments. We are trying slowly to move over to a common command line handling engine. The commandline arguments for these platforms are described here:

--load-slot=NUM [gtk,win]

Loads savegame from slot NUM

--play-movie=PATH_TO_PLAY_MOVIE [gtk,win]

Specifies a dsm format movie to play

--record-movie=PATH_TO_RECORD_MOVIE [gtk,win]

Specifies a path to a new dsm format movie

--start-paused=START_PAUSED [gtk,win]

Indicates that emulation should start paused

--cflash-image=PATH_TO_DISK_IMAGE [gtk,win]

Requests cflash in gbaslot with fat image at this path

--cflash-path=PATH_TO_DISK_DIRECTORY [gtk,win]

Requests cflash in gbaslot with filesystem rooted at this path

--bios-arm9=BIOS_ARM9_PATH [gtk,win]

Specifies a path to an arm9 bios which will be used

--bios-arm7=BIOS_ARM9_PATH [gtk,win]

Specifies a path to an arm7 bios which will be used

--bios-swi=BIOS_SWI [gtk,win]

Set to 1 to enable the emulation of SWI via the provided bios files, which I hope you have provided with the above options. (default 0)

--num-cores=NUM [win]

Overrides the emulator's autodetection for number of processors. Presently, any system with more than one core (this may inadvertantly include singlecore systems with hyperthreading, but I can't test it) will operate with somewhat reduced OSD functionality, with lower quality and no asynchronous composition. In the future, other optimizations will require higher numbers of cores (optimizations for quad-core are planned, but it won't be too impressive)

--scanline-filter-a=NUM [win]

Intensity of fadeout for scanlines filter (edge) (default 2)

--scanline-filter-b=NUM [win]

Intensity of fadeout for scanlines filter (corner) (default 4)

--arm9gdb=PORT_NUM [gtk,win]

Enable the ARM9 GDB stub on the given port

--arm7gdb=PORT_NUM [gtk,win]

Enable the ARM7 GDB stub on the given port

-h, --help [gtk,win]

Show summary of options.

--opengl-2d [gtk]

Enables using OpenGL for screen rendering

--soft-convert [gtk]

Use software colour conversion during OpenGL screen rendering. May produce better or worse frame rates depending on hardware.

--3d-engine=ENGINE [gtk]

Select available 3d emulation:

0 = 3d disabled
1 = internal desmume software rasterizer (default)
2 = osmesa or gtkglext opengl (if available, depending on compilation options, see desmume --help)

--disable-sound [gtk]

Disables the sound emulation

--disable-limiter [gtk]

Disables the 60 fps limiter

--save-type=TYPE [gtk]

Select savetype from the following:

0 = Autodetect
1 = EEPROM 4kbit
2 = EEPROM 64kbit
3 = EEPROM 512kbit
4 = FRAM 256kbit
5 = FLASH 2mbit
6 = FLASH 4mbit

--fwlang=LANG [gtk]

Set the language in the firmware, LANG as follows:

0 = Japanese
1 = English
2 = French
3 = German
4 = Italian
5 = Spanish

--timeout=SECONDS [gtk]

Quit desmume after the specified seconds for testing purpose.

--display=DISPLAY [gtk]

X display to use.

-v, --version [gtk]

Show version of program.

--nojoy=1 [gtk]

Skips joystick initialization (for folks with laptops that have accelerometers for joysticks)

Personal tools