27 replies to this topic

[Chernobyl]

So I'm trying to figure out why sometimes my weapon 1, which is bound to mouse button 1, fires repeatedly...it happens in every match. It makes this game not very fun to play, and it makes my mech overheat in the middle of battle.


Edit: it happens mostly when I'm about to fight or in a middle of a fight.

Edited by Chernobyl, 02 November 2013 - 08:45 PM.

[Koniving]

Mouse disconnect? Keyboard disconnect? Accidentally holding down "1" on the keyboard? Another key also assigned to fire it as well?

We could use more information.

[Wintersdark]

I experienced something similar.

I didn't report it, as while it happened repeatedly during a game session, after I rebooted my system it stopped, so I assumed it was something weird on my end and likely related to win8.1.

What happed to me was ALL my weapons would start firing out of nowhere, and continue firing until I overheated. After overheating, they'd stop, but it would start again intermittently.

I've never had issues with my keyboard or mouse before, my mouse lacks the ability to trigger an alpha strike right now (keybinds being what they are) and my keyboard is a very old but solid industrial Dell keyboard and pretty much bulletproof.

Anyways. Restarting fixed it, and it hasn't reoccurred.
It was bizzare, though... I was really lucky it never happened when I could hit friendlies.


More info: Likewise, it only happened for me near enemies. While I have a key bound to alpha strike(tab) I never use it, so it wasn't a matter of they key getting "stuck down" in software. Still, it only ever happened during or near combat.

Edited by Wintersdark, 02 November 2013 - 09:04 PM.

[StarGeezer]

Wintersdark, on 02 November 2013 - 09:03 PM, said:

It was bizzare, though... I was really lucky it never happened when I could hit friendlies.

More info: Likewise, it only happened for me near enemies. While I have a key bound to alpha strike(tab) I never use it, so it wasn't a matter of they key getting "stuck down" in software. Still, it only ever happened during or near combat.

I suspect it was those sneaky clammers and their clam tech...

[Chernobyl]

I don't have any keys bound outside of the default, other than alphastrike on my #5 button. I'm on Windows 8.1, and I use a fairly new Alienware laptop m14 (June 23rd deployed), and I don't normally use my #1 and #2 button for firing. I use the Alienware touchpad and mouse for this game.

[Johnny Marek Summers]

I have this problem as well. It's why I haven't played all that much. I'm not sure why it happens and unfortunately I have hit friendlies when the weapon goes off and I wasn't expecting it to.

And it takes a bit to actually try and fix it so I rarely have been able to appologize. Actually the temporary fix (double tap the number key associated with the bad weapons group during the cool down period) is fairly easy, manuevering your mech so that you aren't a threat to your dropmates while you are trying to fix the problem makes it hard to appologize.

Unfortunately the Repair Tool will not fix this problem.

[Chernobyl]

Johnny Marek Summers, on 02 November 2013 - 09:35 PM, said:

I have this problem as well. It's why I haven't played all that much. I'm not sure why it happens and unfortunately I have hit friendlies when the weapon goes off and I wasn't expecting it to.

And it takes a bit to actually try and fix it so I rarely have been able to appologize. Actually the temporary fix (double tap the number key associated with the bad weapons group during the cool down period) is fairly easy, manuevering your mech so that you aren't a threat to your dropmates while you are trying to fix the problem makes it hard to appologize.

Unfortunately the Repair Tool will not fix this problem.

Do you also have an Alienware? Also do you have an external mouse that you use? I'm curious if this happens on an external mouse as well.

Edited by Chernobyl, 02 November 2013 - 09:57 PM.

[XphR]

It could be a microswitch going out. Have you opened the windows onscreen keyboard and watched it awhile for phantom keystrokes?

I just rebuilt a micro switch in my mouse for a similar issue(click strobe). Sadly I dont think the micros under chiclet keys on a laptop can be rebuilt in the same way. But on a lighter note, a good cleaning may be in order. Even under the slimmest of keyboard keys a bit of paper, eraser, hair or many other types of fluffy fuzzes can get between the key and the switch and stop or cause clicking.

[Chernobyl]

Just played a match to see if double clicking the #1 would cancel out the mouse #1 button, but no luck.

[Redshift2k5]

Definitely sounds like an issue with either your hardware or your drivers/OP and not any issue with MWO itself, sorry

[Nick Makiaveli]

Random thought...make sure you don't have any of the disability settings turned on, might be something like hitting the key repeatedly in short time frame causes it to get "stuck". Don't have Win8 so can't say for sure but have seen it do weird things in XP/7.

*edited to shut up my inner Grammar National Socialist*

Edited by Nick Makiaveli, 03 November 2013 - 10:51 AM.

[Bront]

Another thought. Touchpads click when you tap them, so maybe if you're using a touch pad, it's registering a click? Try using a normal mouse (and possibly disabling the touch pad) and see if that helps.

[Nick Makiaveli]

Bront, on 03 November 2013 - 11:02 AM, said:

Another thought. Touchpads click when you tap them, so maybe if you're using a touch pad, it's registering a click? Try using a normal mouse (and possibly disabling the touch pad) and see if that helps.

Good point, one of the reasons i hate touchpads.....try to move the cursor, and launch an application.

[John MatriX82]

Hold on..

I've experienced this kind of issues, it's usually due to your controls configuration and/or your weaponsgroups.xml.

Simply get rid of your user folder (user/profiles) and restart from fresh or try to trash only the weaponsgroups.xml (that you find in user/profiles/yourname); either way you'll have to rebuild all the weapons' groups and it should solve it.

I had a similar problem with my AWS 9M that suddendly started spinning left without pause and other times I've experienced the same "non stop firing" groups. It wasn't either the keyboard nor the mouse.

It's clear that you have to make sure not to have other controllers (joysticks, gamepads) that are connected before deleting the stuff above and if this doesn't fix it, then check your mouse/keyboard on another pc to see if some keys are stuck.

Edited by John MatriX82, 03 November 2013 - 11:55 AM.

[Wintersdark]

Nick Makiaveli, on 03 November 2013 - 10:50 AM, said:

Random thought...make sure you don't have any of the disability settings turned on, might be something like hitting the key repeatedly in short time frame causes it to get "stuck". Don't have Win8 so can't say for sure but have seen it do weird things in XP/7.

*edited to shut up my inner Grammar National Socialist*

Yeah, in my case anyways this wasn't the problem.

1) I turn this off.
2) My weapons would randomly start firing when I wasn't pressing any keys at all.

[XphR]

Wintersdark, on 03 November 2013 - 12:01 PM, said:

2) My weapons would randomly start firing when I wasn't pressing any keys at all.

Have you tried the OSK yet and watched for random inputs?

[Wintersdark]

Redshift2k5, on 03 November 2013 - 03:25 AM, said:

Definitely sounds like an issue with either your hardware or your drivers/OP and not any issue with MWO itself, sorry

You'd think so, but I've seen an increasing number of people with this problem. I'm starting to suspect there is in fact a weird random problem with MWO causing it. I haven't experienced it again, but I'm very curious because I run into the odd person in game with it happening from time to time - leading me to suspect a weird interaction with how mwo/cryengine is hooking the keyboard and certain system configurations.

I kind of wish I could get it to happen again, so I could test out some theories.

[Wintersdark]

XphR, on 03 November 2013 - 12:05 PM, said:

Have you tried the OSK yet and watched for random inputs?

No - though it's an approach I'd considered (actually, I was planning on firing up Eventghost's monitor, as it tracks *every* sort of input) but I haven't been able to recreate the problem.

The thing was, and what was very, very strange, is it was firing every weapon simultaneously. The only way to do that for me via keyboard or mouse was with Tab, and switching out of MWO and into Notepad didn't show tab's being pressed.

In my case, my mech would start alpha striking, and continue until it shutdown. Once it restarted, it would not be firing any more. Hitting Tab while the mech was alpha striking did not stop it (so it wasn't a case of MWO incorrectly assuming the key was held down).

The fact that it would stop alpha striking after restarting is what most strongly suggests to me that it was an MWO bug. An input-device related issue would have resumed alpha striking when it started up again (behavior demonstrable, of course, by holding down your alpha strike key as you start up)

[kevin roshak]

this happens to me sometimes, and its usually the mouse button gets stuck down. i just press it again and it stops

[Wintersdark]

kevin roshak, on 03 November 2013 - 01:16 PM, said:

this happens to me sometimes, and its usually the mouse button gets stuck down. i just press it again and it stops

Yeah, that's not the problem we're discussing, as has been explained above. It's not a stuck button/switch.