@sleve_mcdichael having had a cursory look I can confirm and I lean towards "won't fix".

Rationale: As long as there are SDL events they get pumped into the Window.cpp/GuiComponent::input() call chain an consumed from there. Every downwards component "sees" one event at a time. Processing of the event is stopped either at the last GuiComponent in the chain or if a input() call returns true.

This also happens with Use LR/LB for full page navigation set to false. It just does not occur as easily as the cursor most of the time is always placed middle.

One option to remediate may be to measure the time between the events and if they are too close (i.e. less time than between update()/render() calls) drop the second, and ofc only if the events are LR/LB.

I don't have any other idea at the moment.

@prukogui from what I can tell, SWA on lr-2015 has permanent, broken controls. lr-2016 can be properly configured, but will run slower. lr-mame will run even slower, requires a different ROMset, but has more accurate emulation.

2016 seems to run "okay-ish" up until the trench on the second scene, then there are a bunch of graphic anomalies.

Wish I had better news, but there aren't many good solutions for SWA -- at least none that I could find.

@mitu
Sure! I will post all my findings to help others as well.
Thanks for your time.

@mitu

ah ok - should be fine now.

For what it's worth, I got a 5.2v 2.5a power supply. I had no reason to believe it would make a difference; but I've seen much stupider things fix dumb things.

Of course, the cursor still pops.

Dosbox definitely has a rotation, I can move with the mouse but only within a circle that snaps back to center that's def analog stick mapping. Where do I change that setting I have not come across any for mouse.

I solved my concern.

In fact it is necessary to modify in the file advmame-1.4.rc the following line:

input_map [p2_lightgunx] mouse [2, x]
input_map [p2_lightguny] mouse [2, y]

Thank you in any case, I could not double cursor on any game.

@pickles I strongly suspect a faulty SD card. It's known that they get into a read-only state when they're approaching their end.

@jonnykesh No problem. It's just on a Rapsberry Pi 3b with Retropie 4.3. Had the same issue on 4.2.