provide default mouse button mapping to lightgun API triggers

[markwkidd]

RA support for the lightgun API is a useful addition to the input system.

At the present, when the user has a mouse connected and has selected lightgun as their input device, they do have an automatic mapping of the mouse movement to crosshair movement.

There is not at present a default mapping between mouse buttons and the lightgun API triggers. This is a request to add a default mapping.

[OctopusButtons]

I may be mis-reading your description, but I think the problem is larger than described: as of RetroArch 1.9.0 there is no support at all for custom binding lightgun button to anything other than default Mouse1 if you're using mouse to control crosshair. If you try to change the binding in a config like any other binding, it won't work. The line in the config file is right there (apparently), but, if you change it has no effect and it doesn't change.

In other words, it's impossible to bind Lightgun Trigger/Fire to a controller button or keyboard button. I mean specifically if (I think?) you're using a Mouse to control lightgun crosshair. It's like it's hard-wired into the RetroArch code somewhere, and it automatically over-rides any attempt to config or bind it to something else. Basically, Lightgun Mouse doesn't function like any other control.

I thought that there WAS a "default", the problem I saw was that it's impossible to change that default to anything else.

[markwkidd]

@OctopusButtons in the current version of RA, there is no default binding for the lightgun trigger (or other lightgun controls). What you are describing sounds like a separate, although equally frustrating, issue. In fact, I think someone else has just logged it in detail here: #12417

Does that issue sound the same as yours?

[markwkidd]

Closed via #12423

[OctopusButtons]

Sorry, I’ve been busy and never replied. I’ll reply in the other thread. It does seem similar, in that in that case and my case the accepted binds in the RA menu (or also using manual config entries) have no effect in game. It’s like the Mouse button 1 is hard coded to lightgun trigger, I can disable that by binding it stop something else, but the something else doesn’t work, the only thing that works when bound to lightgun trigger is Mouse button 1.

By “no default binding” maybe I should have said “a rogue invisible binding.” It seems like a default somewhere in the code, invisible to the front end and unaffected by manual CFG changes.