13 replies to this topic

[Grimlock Magnus]

Hi, first off, I'm very happy with the return of Fire Selected weapons group. This is also not about that, but for some reason since it returned with the latest patch, it will not map to any of my mouse buttons...? I can assign it just fine, but it just will not trigger. What does work is mapping it to a key and then mapping my mouse button to that key. However that is causing all kinds of issues (once I do that, I can no longer use LMB and as a result, it's very difficult to set it back). I have a Logitech Performance MX and it's happening in every mech on every map. Please note that all other bindings (to mouse or keyboard) seem to work just fine. Please help!Steps to reproduce: 1. Mount fire selected weapons group to Left Mouse Button (LMB) 2. Join any game. 3. The LMB will not trigger fire selected weapons group, nor will any other mouse button (keyboard buttons work just fine). w

Edited by Grimlock Magnus, 19 November 2013 - 04:18 PM.

[HUBA]

yes, on the alternate key map it won't work use the first row

--edit--
sorry for the bad explanation - use the primary key map

Lusankya, on 20 November 2013 - 08:19 AM, said:

Just tried this out and sure enough it wouldn't work if put onto the alt fire position but it does work if you put it onto the primary.

Edited by HUBA, 20 November 2013 - 10:55 AM.

[Kaosity]

I can confirm this. It works on any joystick button but fails on Mouse1, Mouse2, and Mouse3. The binding "map" shows the buttons as bound but they fail to operate in either the test maps or real game operation.

Sounds like a fix for Friday? Right PGI? Please......

[FREDtheROLF]

HI PGI

thanks for bringing it back... if it would just work.
same behavior as above ... therefore confirmed.

FtR

PS: How can this slip through your QA process? this was what everybody wanted to do with it. did you ever tested the new feature?

Was this a test to see how many of the players complaining that it was gone really use it once it is back ?

Edited by FREDtheROLF, 19 November 2013 - 11:30 PM.

[TyrEol]

It's also not working here, I can bind it to mouse 1 but it doesn't fire. Dropped twice it was the same both times.

Windows 7 64bit, USB Razor deathadder mouse, can provide full system specs if needed

[Lightfoot]

Don't know if this is related because I use a joystck, but I noticed that right when I needed it to be fireing, my AC20 would not fire on 'number one' bound to trigger (button 1). Just the AC20 though.

[Dustein]

Grimlock Magnus, on 19 November 2013 - 04:12 PM, said:

I can assign it just fine, but it just will not trigger.

+1
Can asign in options but does not respond in game.

[xhrit]

same.

[Lusankya]

Just tried this out and sure enough it wouldn't work if put onto the alt fire position but it does work if you put it onto the primary.

[Dock Steward]

Yep. Same problem.

[Dock Steward]

Just got this response from support:

"we are unable to identify from here what may cause the communication problem between your inputs and your PC."

Unhelpful f*#@^s!!! Anyone solved this problem yet?

Edited by Dock Steward, 21 November 2013 - 02:51 PM.

[MountainCopper]

Also had this issue at first, so again, if the one description maybe wasn't clear enough:

You have to set your "Mouse 1" as the primary key binding for "Fire selected weapon group". That means the first column from the left.

[Robertak]

yep.. exactly like that.. working fine when mapped to primary column (called "KEY MAP" in game) in secondary column (called "ALT KEY MAP") it doesn't work.. pretty strange, isn't it? still I'm really happy to have this option back!

[Dock Steward]

Thanks guys. Sorry, I hadn't seen that fix when I read this thread earlier. Lack of sleep=bad reading comprehension.