FCEUX SDL FAQ

Table of Contents:

• What's the difference between the windows and sdl ports?
• How do I configure a gamepad?
• Why do I need lua5.1 to compile/run FCEUX?

A lot of work that has been done on the FCE code base was been windows only, so some features have not been implemented into the more portable SDL version.

Here is a list of planned features that are currently in the Win32 build but are missing from the SDL build:

• Autosaving
• Hotkey mapping
• More graphical ways of configuring FCEUX

I'm going to reiterate that much of the work that has been done of the FCEUX code base has been windows only, so some features will probably never be ported to the SDL version. If you are a casual user that just wants to play old NES games, the SDL build will be sufficient for you. However, if you want to use the extensive TAS and debugging features that FCEUX has to offer, you are better of using the windows build in wine. Here is a list of features that will most likely never be ported to the SDL port.

• Memory watch
• Ram filter
• TAS edit
• Most of the debugging features

You can configure the first gamepad by running fceux --inputcfg gamepad1

When you do this, you'll be presented with a black window with a titlebar 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 keypresses in a row, it will allow you to map the button to four seperate keys.

Input configuration is planned for gfceux.

You don't! As of version 2.0.3, lua is optional. However, the lua scritping engine in fceux is very powerful, and will be used more and more by fceux in the future.