MAMEWorld Forums - EmuChat - Linux problems (Mame 0.162)

I am having several problems under Linux (Mageia 4, Mame 0.162):

I cannot map joysticks. Something is causing my joystick to be seen as two joysticks, which does happen outside Mame, but when I actually use the joystick, Mame thinks it's #2. A joystick test program shows my joystick as joystick 0 as I expected (which should be 1 in Mame, not 2). The obvious solution is to try remapping the joysticks. However, that doesn't work.

I originally get:


Joystick: Start initialization
Input: Adding Joy #0: Twin USB Joystick
Joystick: Twin USB Joystick
Joystick:   ...  4 axes, 12 buttons 1 hats 0 balls
Joystick:   ...  Physical id 0 mapped to logical id 1
Input: Adding Joy #1: Twin USB Joystick
Joystick: Twin USB Joystick
Joystick:   ...  4 axes, 12 buttons 1 hats 0 balls
Joystick:   ...  Physical id 1 mapped to logical id 2
Joystick: End initialization

Trying to map the joysticks causes them all to be remapped at -1 no matter what I do.


joy_idx1                  0
joy_idx2                  1
joy_idx3                  2

gives me


Joystick: Start initialization
Input: Adding Joy #0: 0
Joystick: 0
Joystick:   ...  -1 axes, -1 buttons -1 hats -1 balls
Joystick:   ...  Physical id -1 mapped to logical id 1
Input: Adding Joy #1: 1
Joystick: 1
Joystick:   ...  -1 axes, -1 buttons -1 hats -1 balls
Joystick:   ...  Physical id -1 mapped to logical id 2
Input: Adding Joy #2: 2
Joystick: 2
Joystick:   ...  -1 axes, -1 buttons -1 hats -1 balls
Joystick:   ...  Physical id -1 mapped to logical id 3
Input: Adding Joy #3: Twin USB Joystick
Joystick: Twin USB Joystick
Joystick:   ...  4 axes, 12 buttons 1 hats 0 balls
Joystick:   ...  Physical id 0 mapped to logical id 4
Input: Adding Joy #4: Twin USB Joystick
Joystick: Twin USB Joystick
Joystick:   ...  4 axes, 12 buttons 1 hats 0 balls
Joystick:   ...  Physical id 1 mapped to logical id 5

and the actual joystick (which my system thinks is physical ID 1) is now treated as joystick 5.

I cannot configure video. The main complication is that most documentation is written for Windows. For instance, there is a file docs/newvideo that comes with mame. It helpfully describes that depending on what I want to do, I might use d3d or ddraw, I'm on Linux; I don't have these. It also mentions hwstretch. There is no hwstretch option. (I need to use the ancient video card option. My card is not technically ancient, but it's a builtin Radeon HD 3000; already bad, and my drivers are terrible. The driver is "ati" (the free driver). With vsync off, glxgears gives me around 1100 in software mode and 2000 accelerated.)

Attempting to use switchres with window=0, leads me to a weird situation where the screen switches to the new resolution, but the game doesn't fit inside the screen and acts as though it's being fit into a larger screen, making it go off the edge. soft or opengl makes no difference to this, and smaller prescale values actually make it worse.

I have no idea what values are acceptable for the "scalemode" option. The SDL.txt sort of documents it but it lists an "async" option that doesn't actually work under Linux. Furthermore, it just lists the options without descriptions. What are they and why would I want them? Googling tells me that async is "async overlay", which is also unhelpful.

window=0 always maximizes even with maximize=0. (maximize works correctly with window=1.)

prescale seems to do nothing in windowed mode. I have no way to tell if it is working in fullscreen mode.

Also, is there any way to say "scale by the largest integer factor that fits in the current screen resolution"? For that matter, is there any way at all to specify what factor to scale by, given that I do not have d3d or ddraw?

The documentation claims that prescale takes a parameter from 1 to 8. It only accepts 1-3.

Running a game and going into the options gives me an option for "pixel aspect". Is there a way to say "apply pixel aspect to every game that has it"?