1-Works perfectly fine.
2-Slower I guess? Not that noticeable but I have high mouse sensitivity.
3-Performance is excellent sir.
4-I didn't use another joystick, but keep reading for what happened to my first one...
5-<33
About the joysticks: First off, it's absolutely beautiful that movement with the joystick is now analog and not digital, it's a COMPLETE game changer for me and feels excellent. However, now the issue is that it handles EVERYTHING but the left thumb stick wrong.
I'm using a 360 controller, so I guess you could say this has two joysticks on it, or really 3? 2.5? (I say this because when you think about it, the triggers are another axis.) On the one hand setting strafing to the Y axis instead of -Y axis works so it's not asinine, but everything else is just incorrect. The right thumbstick's X-Axis is read as the controller's Z-Axis, its Y-Axis as the Z-Rudder, and worst of all, the triggers are now read as two separate axis, the left and right triggers as the Y and Z rudders respectively. Also, when either of these are set to turning, the camera perpetually turns left and holding the trigger down has it turn right (the camera stops if you hold the trigger halfway).
Along with that, the buttons are oddly remapped, with what is read in srb2sdl as pressing down on the bumpers is read in srb2win as clicking down on the thumbsticks, obviously the most useful buttons in the world :P
But yeah this is what happens to the joysticks now. Everything else about srb2sdl so far is excellent, so if this issue can be addressed, then all will be right with the world.
EDIT: Also, it's worth noting that controller input no longer works with menus since it's not emulating a keyboard :/
EDIT 2: Lemme rephrase: JOYSTICK input specifically, as in axis controls, don't work for menus. Pressing up or left on the D pad acts as enter/select/the 360's "A" button.
THIS MAPPING THO.