It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
I have an NVIDIA GTX 660Ti GPU with up to date drivers. So far as I can tell all of my OS drivers are all up to date. When playing my main ( or any other char for that matter) when I press the fire key for more than a second or so and then release my weapon continues to fire. Sometimes in excess of 10 seconds. During that time I cannot move other than to spin to re-aim my weapon The more creatures in the battle, the more intense the battle, the longer before my weapon will continue to fire up to in excess of 10 seconds. Everything else seems to work fine. I have no other laggin issues that I can discern.

Anyone have a clue as to the cause of a stuck trigger? BTW this is NOT a keyboard issue so far as I can tell. The trigger key is not sticking. Thanks all!
No posts in this topic were marked as the solution yet. If you can help, add your reply
avatar
Krundar: I have an NVIDIA GTX 660Ti GPU with up to date drivers. So far as I can tell all of my OS drivers are all up to date. When playing my main ( or any other char for that matter) when I press the fire key for more than a second or so and then release my weapon continues to fire. Sometimes in excess of 10 seconds. During that time I cannot move other than to spin to re-aim my weapon The more creatures in the battle, the more intense the battle, the longer before my weapon will continue to fire up to in excess of 10 seconds. Everything else seems to work fine. I have no other laggin issues that I can discern.

Anyone have a clue as to the cause of a stuck trigger? BTW this is NOT a keyboard issue so far as I can tell. The trigger key is not sticking. Thanks all!
I've never heard of this issue on any of the game forums, and I have not experienced it.

It does sound like a hardware problem. Just because your key is not physically staying down doesn't mean the contact is not still being made underneath, perhaps.
I myself haven't any problems in GD and I haven't heard any of that kind in that particularly game.

My advice:

Eliminate out the keyboard now and you''re not only sure, but also one step closer in finding the problem. Troubleshooting is about eliminating possibilities.

Try other keyboards
Try new batteries
Try other (usb)ports
Try without usb hub directly on the mamaboard (not via internal connection)
Does it happen in other games?

I've had "lag" before, and usually it's those mentioned (unless I've forgotten something).
Post edited July 05, 2019 by sanscript
avatar
sanscript: I myself haven't any problems in GD and I haven't heard any of that kind in that particularly game.

My advice:

Eliminate out the keyboard now and you''re not only sure, but also one step closer in finding the problem. Troubleshooting is about eliminating possibilities.

Try other keyboards
Try new batteries
Try other (usb)ports
Try without usb hub directly on the mamaboard (not via internal connection)
Does it happen in other games?

I've had "lag" before, and usually it's those mentioned (unless I've forgotten something).
Here's what I have discovered with this problem. This makes no rhyme nor reason to me. I have been logging into my game via GOG Galaxy. Out of frustration I closed out Galaxy and logged back into the game without Galaxy and the trigger lag disappeared. Out of Galaxy and everything works perfectly. There it is folks. No clue what's happening however I do log into Galaxy frequently so as to avail myself of the cloud saves. That's magic I can live with. Thanks for all of you guys and your support!
avatar
Krundar: I have an NVIDIA GTX 660Ti GPU with up to date drivers. So far as I can tell all of my OS drivers are all up to date. When playing my main ( or any other char for that matter) when I press the fire key for more than a second or so and then release my weapon continues to fire. Sometimes in excess of 10 seconds. During that time I cannot move other than to spin to re-aim my weapon The more creatures in the battle, the more intense the battle, the longer before my weapon will continue to fire up to in excess of 10 seconds. Everything else seems to work fine. I have no other laggin issues that I can discern.

Anyone have a clue as to the cause of a stuck trigger? BTW this is NOT a keyboard issue so far as I can tell. The trigger key is not sticking. Thanks all!
Hi Krundar.

It might be the GOG Galaxy overlay causing the lag, if you have it enabled. Try disabling it and see if that eliminates the lag.

Cheers.
Post edited July 13, 2019 by Fate-is-one-edge
I've experienced a similar problem in effects with some games on Linux, which after a long time I discovered was caused by an accessibility feature. It's desired that if you press and hold a key, it'll start repeating (particularly useful for backpacking long stretches of text and so on). But in some games - which presumably have their own logic for handling keys that aren't released, separate from what the OS provides - it appears that so much is happening on the same 'thread', that this input from the OS gets queued, and is still being processed long after I've released the key.

Turning off that particular accessibility feature ("Repeat keys", though presumably it'll be called something else on Windows) when playing one of these games completely solved the problem for me. It might be worth seeing if the equivalent situation exists for you.

edit: looks like you can't turn the feature off in windows, but it has a "repeat delay" and a "repeat rate" under keyboard properties, which you can set to "long" and "slow" to see if that has any effect.
Post edited July 13, 2019 by gogtrial34987
avatar
Krundar: Out of Galaxy and everything works perfectly.
There you go... Galaxy seem to be a minor/major nuisance to some.

I don't use it myself, but things like this is not going to make me want to try it more. :)
Post edited July 14, 2019 by sanscript
avatar
Krundar:
I've seen a frequent bit of advice when encountering issues being turn off the Steam overlay. Same with some overclocker/fps monitoring software. Is that perhaps the issue here? Never used Galaxy so I don't know how much it has in common with Steam.