That's something the SDL OSD already does... see src/osd/sdl/input.c, line 1260 ff!!

But it does that on specific axes only (axis 12 and axis 13). Perhaps that's what confuses you?!

That's not the behavior I'm seeing in outrun. After fixing the overflow (src/osd/sdl/input.c, line 71, change 8 to 28), OutRun is very playable on a DualShock 3 with -nosixaxis and the pedals mapped analog to pressure sensitive buttons (I recommend L2 and R2). Its input test screen gives exactly the desired values too (00 up, FF down).

-E- Crus'n World (crusnwld) and Ridge Racer (ridgerac) behave in exactly the same way. Are you sure pedals are not an exception or similar?

On a related note, I found another issue. I can't map the button axes through MAME's menus, but if I manually edit ~/.mame/cfg/*.cfg, they work fine.

I've improved the -sixaxis handling for 0.129 so now it "sanitizes" all the non-stick axes instead of just 12 and 13 (and fixed the max axes in the OSD layer to 32). The inability to map axes > 4 or so in the UI seems to be a baseline thing. Aaron?

So the outrun and crusnwld and ridgerac drivers are bugged in their pedal handling? What games aren't bugged then?

They're not bugged. You're just getting suboptimal results right now and assuming it's perfection. Happens a lot with emulation.

Here's (presumably) a way to get the sixaxis working on OSX.

Source code and binary:
http://netkas.org/?p=76

I haven't tried it myself, I don't own a sixaxis.

With the sixaxis "fix", the pedal axes start at 0, then jump to almost exactly halfway (7F in outrun) with any axis activity, then moving between halfway and max. Unless I start the game holding down each pedal button, the game calibrates for 0-max, meaning the brake is always at least halfway on, and your car doesn't go anywhere. This strongly suggests to me the "fix" is wrong and resting at -32767 is expected for pedal axes.

I probably should have mentioned all this right off the bat.

Well, I'm doing what Aaron tells me the OS Dependent layer should do. It's up to you to convince him he's wrong :-)

Or I could just not use the sixaxis option.

I could make it mandatory if the controller name matches. Anyway, the adjustment is different in my code from what's in yours, so you're not actually seeing how 0.129 will behave.