 |
 |
 |
 |
 |
F.A.Q.
Q: Which emus are compatible with padJoy?A: PCSX and ePSXe are known to work with padJoy (the later has some limitations, see below). Any other emu that supports the PSEmu interface should do as well.
Q: Why does the second pad not work with ePSXe?
A: Unfortunately, ePSXe's pad plugin interface supports only one pad. You can use xjoypad to or a similar program to work around this problem.
A: Unconfirmed: Piotr Szymaniak told me that he is able to use two pads with ePSXe 1.5.2 on Gentoo Linux with kernel 2.6.14-gentoo-r5.
Q: Why does an analog pad not work with ePSXe?
A: Confirmed by Jo Christian Bergsk`s: Yoshinobu IGARI told me that ePSXe 1.6.0 has a "-analog" command line option; if you run it with that option, analog works, but you have to use the "PCSX-Style" option in padJoy.
Q: How can I use the macro feature to program a rapid fire button?
A: You need to make a macro that calls it's own invocation event in the end. For optimal performance, edit the padJoy.cfg file to adjust the intervals. Interval times are given in 1/10000 sec. See this example:
[macro 2]
event_launch = B0P2
events = B0P3 B0R3 B0P2
interval = 0 500 500
event_launch = B0P2
events = B0P3 B0R3 B0P2
interval = 0 500 500
Q: Does padJoy run on Windows?
A: No, and chances are very little it ever will. Anyway, it's open source, so feel free to make a pad plugin for Windows based on padJoy.
Q: The plugin does not work at all, how can I test if my system is well configured?
A: Check that the joydev module is loaded ( lsmod; if necessary, run modprobe joydev as root )
A: Check your permissions on the device file ( ls -l /dev/input/js0; if necessary, run chmod a+r /dev/input/js0 as root )
A: See readme.txt for more instructions how to check your joy device driver.
Q: ePSXe coredumps when I use padJoy, what can I do?
A: This happens on some systems, e.g. on my Mandrake 9.1. Here is my workaround (ePSXe is installed in ~/epsxe/):
cd ~/epsxe/
mkdir lib
cd lib
ln -s /lib/libc.so.6 .
ln -s /lib/libm.so.6 .
ln -s /lib/libpthread.so.0 .
ln -s /lib/librt.so.1 .
ln -s /lib/libthread_db.so.1 .
cd ..
env LD_LIBRARY_PATH=./lib ./epsxe
mkdir lib
cd lib
ln -s /lib/libc.so.6 .
ln -s /lib/libm.so.6 .
ln -s /lib/libpthread.so.0 .
ln -s /lib/librt.so.1 .
ln -s /lib/libthread_db.so.1 .
cd ..
env LD_LIBRARY_PATH=./lib ./epsxe
Obviously, only the last line is required after the first time.
Q: padJoy is way too sensitive, it interprets tiny movements of the stick as an actual movement.
A: place the following lines in your padJoy.cfg file:
minzero = -2500
maxzero = 2500
maxzero = 2500
Example:
[general]
pcsx_style = 0
use_threads = 1
use_analog = 1
[pad 1]
devicefilename = /dev/input/js0
minzero = -2500
maxzero = 2500
event_l2 = B0P
pcsx_style = 0
use_threads = 1
use_analog = 1
[pad 1]
devicefilename = /dev/input/js0
minzero = -2500
maxzero = 2500
event_l2 = B0P
You might have to try some other values in place of 2500... The higher the value, the greater the dead range (so the pad is "less sensitive")
Q: I want to edit the config file by hand, what do those codes mean?
A: "event_triangle", "event_down" etc. obviously correspond to the buttons and controls on the joypad. For the right side, there are: Keyboard events (starting with the letter "K"), button events (starting with "B"), axis events (starting with "A") and analog axis events (starting with "X").
- Keyboard event descriptions continue with "P" for press (or "R" for release), followed by the Key code in double quotes.
For example, KP"x" means that this event is mapped to the x key on the keyboard. - Button event descriptions continue with the pad number (0 or 1), then "P" (for "press"; within macros, there can be "R" for release); finaly the number of the button.
B0P2 means: Button 2 of joypad 0 pressed. - Axis event descriptions continue with the pad number, "P" for press (or "R" for release), the axis number and finally + for the positive side or - for the negative side of the axis.
A1P2+ means: Axis 2 of joypad 1 pressed on the positive side (usually right or down). - Analogue axis event descriptions continue with the pad number, "P" for press, the axis number, v (for "value") and finaly a value between 0 and 255. For event mapping, the value is always zero; within macros, different values make sense.
X0P3v127 means: Third analogue axis of pad 0 in center position.
Q: How can I support the development of padJoy?
A: Currently, padJoy is considered "complete". If you want new features, email me. You can indirectly help padJoy by persuading the ePSXe team to improve the pad plugin interface.
