I get the feeling most questions would be more likely to get answered if we asked them in the relevant core's forum, or emulationstation forum, etc.

To be clear: The stick IS operating as analog. But the zone of movement where it is analog is very small, kicks in at a relatively high value (presumably at least 4096,4096), and reached 100% input almost immediately with only a very small movement. There is a large area towards the outside of the movement circle, seems like more than half of it, where all movement is at 100% despite not being anywhere near the physical limit of the stick movement. black=no effect grey= effect, engages suddenly at high value, and quickly reaches 100% with very little movement. white=100% effect, reaches 100% well before stick physically reaches edge of range. ^^^ bad ^^^ Modern controller sticks self-centre, so a huge analog deadzone is redundant, and suddenly outputting 100% effect when it's nowhere near 100% of it's physical movement range.. is very tedious.

Got up this morning and turned Pi on. No bluetooth connection. Tried unplugging/replugging dongle(s). Total failure. So I set max_usb_current=0 and rebooted. Immediately it worked. Very strange, considering it worked fine the night before and now suddenly didnt work at all after a night powered down. Is it possible that the Pi is drawing current from the HDMI cable even when the Pi itself is off? The only difference between working (last night) and not working (today) was that overnight I physically remove power from my tv via a switch on a powerboard...that the Pi is also powered from. However while testing I generally only unplug the Pi, and do not kill power to the TV as well. Weird. In any case it's back to the usual: working on one dongle just fine across reboots, but not after powerdown/power disconnections. Re-plugging the dongle is still the 'easy' fix.

Like this? Yes?

Anything that uses the analog joystick. It's most annoying in flight sims like Ace Combat (PSX) There is such a huge dead spot that by the time the joystick takes effect it's already a strong response... so it almost may as well be digital on/off. It defeats the purpose of having analog.

I got the impression that mupen64 was for N64 games only....yes? In any case, the variables that I want to alter never actually stays changed after I set it, so I'm finding it difficult to even learn by trial and error. ie: input_axis_threshold in retroarch and AnalogDeadzone in mupen64 But I only made the original post in case it was a bug.

Not lag. Joystick deadzone.

I assumed it would be useful. I'm a noob with the whole emulation thing, and was attempting to come to grips with adjusting controller settings.

re: input_axis_threshold = "0.500000" Does setting this variable have any relevance if the stick is in analog mode? Is it possible to change this value and have it STAY set? Despite changing it in every config I can find, it still resets to 0.5 I am attempting to make my analog sticks more sensitive, and because there appears to be no way to reduce/remove the massive deadzone (which would be ideal) I was experimenting with input_axis_threshold. Presumably by setting it to 1.000000 I will enable the full range of the stick. Right now, between the deadzone which seems to eat the first 20% of movement, and the stick feeling like it achieves maximum signal at about 50% of it's movement... it is extremely difficult to control games like 'Ace Combat 3 - Electrosphere' with any degree of finesse. TL;DR: Reduce PS3controller analog stick deadzone, and increase range of stick movement before 100% signal.

re: CRT only. Right. So then faux-lightguns.... Is the use of mouse and wii controller likely to be included soon?