ShuriZma
/
fceux
mirror of https://github.com/TASEmulators/fceux.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

docs: updated sdl-faq (can someone pull this pls? thx :D )

This commit is contained in:
punkrockguy318 2012-02-10 05:50:19 +00:00
parent 144228c191
commit f4d4486e9e
1 changed files with 22 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

49
fceux-sdl-faq.html
View File

@ -23,7 +23,7 @@
<div id="page_content"> <div id="page_content">
<center><h1>FCEUX SDL FAQ</h1></center> <center><h1>FCEUX SDL FAQ</h1></center>
<center><i>Last updated March 3, 2010<br />Valid as of FCEUX 2.2.0</i> by punkrockguy318<br> <center><i>Last updated February 10, 2012<br /></i> by punkrockguy318<br />
</center> </center>
<p><b>Table of Contents:</b></p> <p><b>Table of Contents:</b></p>
<ul> <ul>
@ -34,46 +34,41 @@
<li><a href="#hotkeys2">Can I map hotkeys to my gamepad?</a></li> <li><a href="#hotkeys2">Can I map hotkeys to my gamepad?</a></li>
</ul> </ul>
<a name="subversion"><h3>What is the subversion build and how can I get it?</h3></a> <a name="subversion"><h3>What is the subversion build and how can I get it?</h3></a>
<p>The latest and greatest changes to fceuX are reflected immediately on our <p>The most recent changes to fceuX are reflected immediately in the fceux
sourceforge subversion server. You can checkout our source code and build sourceforge subversion server. You can checkout the source code to build
fceuX with the latest changes that have been made. Use this command:</p> fceuX with the most recent sources by running the following command:</p>
<p><b>svn co https://fceultra.svn.sourceforge.net/svnroot/fceultra fceultra</b></p> <p><b>svn co https://fceultra.svn.sourceforge.net/svnroot/fceultra/fceu fceux</b></p>
<p>Instructions for compiling and installing fceuX can be found in the "README-SDL" file.</p>
<a name="config"><h3>How do I configure a gamepad?</h3></a> <a name="config"><h3>How do I configure a gamepad?</h3></a>
<p> <p>
<p>If you have the GTK GUI compiled in, you can configure the gamepad by <p>If you have the GTK GUI compiled into fceuX, you can configure the gamepad by
selecting Options...Gamepad in the menu.</p> selecting "Options...Gamepad" in the menubar.</p>
You can allso configure the first gamepad by running <b>fceux --inputcfg gamepad1</b> </p> <p>You can allso configure the first gamepad by running <b>fceux --inputcfg gamepad1</b> </p>
<p>When you configure a button you will be presented with a black window with a titlebar <p>When you configure a button you will be presented with a black window with a titlebar
indicating what button to map. FceuX will look for two indicating what button to map. FceuX will look for two
of the same keypress/joystick event in a row. If it doesn't find two of the same of the same keypress/joystick event in a row. If it doesn't find two of the same
keypresses in a row, it will allow you to map the button to two seperate keys.</p> keypresses in a row, it will allow you to map the button to two separate keys.</p>
</p> </p>
<a name="sound"><h3>My sound is stuttery/laggy. How can I fix this?</h3></a> <a name="sound"><h3>My sound is stuttery/laggy. How can I fix this?</h3></a>
<p>Try using different SDL audio drivers. You can set the SDL audio driver with <p>Try using different SDL audio drivers. You can set the SDL audio driver with
the following command</p> the following command:</p>
<p><b>export SDL_AUDIODRIVER=driver</b></p> <p><b>export SDL_AUDIODRIVER=driver</b></p>
<p>where driver is: esd,oss,alsa,pulse,nas,arts . You should probably <p>where driver is: esd,oss,alsa,pulse,nas,arts.</p>
try them in that order. esd is the best choice if you are using pulseaudio <p>There have been a lot of sound related bug fixes for the SDL port in recent releases, so
or the esound daemon. OSS (with ALSA being seond here)is best if you have you may want to try the latest version of fceuX to see if you are still having issues. FceuX
no sound daemon running. I can't confirm if nas or arts work at all (but 2.1.4 fixed the majority of the reported sound issues.
I'd definately avoid arts altogether). SDL's pulse driver has a lot of issues if you are using
older versions of SDL or pulseaudio. If you are having problems and you use
pulseaudio try the esd SDL driver.
</p> </p>
<a name="hotkeys1"><h3>How can I change my hotkey bindings?</h3></a> <a name="hotkeys1"><h3>How can I change my emulator hotkey bindings?</h3></a>
<p>You need to edit your ~/.fceux/fceux.cfg file. The SDL.Hotkeys.* values <p>You need to edit your ~/.fceux/fceux.cfg file. The SDL.Hotkeys.* values
are SDL keysyms, which can be found in SDL_keysym.h (probably are SDL keysyms, which can be found in SDL_keysym.h (probably
/usr/include/SDL/SDL_keysym.h on your system). At the time of writing, /usr/include/SDL/SDL_keysym.h on your system). At the time of writing,
hotkeys are not mappable from the GUI in sdl. hotkeys are not mappable from the GUI in sdl (although it is planned for the future).
</p> </p>
<a name="hotkeys2"><h3>Can I map hotkeys to my gamepad?</h3></a> <a name="hotkeys2"><h3>Can I map emulator hotkeys to my gamepad?</h3></a>
<p>No, not from within fceuX. However, there is a great script available <p>If you want to map particular hotkeys (pause, save state, load state, etc) to buttons on
called jkeys that will convert joystick button presses and axis movements to keyboard your gamepad, you can use software that allows you to map joystick events to key presses.
keypresses. You can map your joystick buttons to whatever hotkey you'd like. <a href="http://qjoypad.sourceforge.net/">qjoypad</a> is the recomended solution for this. You
<a href="http://code.google.com/p/jkeys/">Jkeys</a> works great with fceuX. can also use <a href="http://code.google.com/p/jkeys/">Jkeys</a> to do this.
There aren't any releases on the website, but don't let that scare you.
You can easily obtain the script via subversion:</p>
<p><b>svn checkout http://jkeys.googlecode.com/svn/trunk/ jkeys-read-only</b></p>
<a name="credits"><h2>Credits</h2></a> <a name="credits"><h2>Credits</h2></a>