Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If you are already using that then try the opposite by disabling Steam API in game and using Xinput Gamepad.
The trigger is an analog axis and unfortunately it sounds like your trigger's sending a non-zero value at rest. The game's threshold for triggers is low, so it's picking it up.
(moved thread to Tech Support since this is unfortunate, but not really a bug)
Do you have any other controllers plugged in? If you look in the Windows control panel game controller list, is anything listed?
It sounds like the game is reading something as a controller for that to happen.
Just to be sure - If you unplug the controller, verify that no controllers are listed in the control panel, and then start the game (with the trigger still mapped), this still happens?
Tried hitting a few buttons on my mouse to see if it was working in the game but the only thing was the middle mouse button on the plunger a bit. I disabled the X & Y Axis & both tilt right & lleft in the mouse buttons to see if that was doing it or if I had a stuck mouse button. There was nothing listed with the Xinput assigned though I could read it in the avaliable options. I also looked to see if there was a mouse buttom assigned to the left shift key but there was not.
The wierd thing is that everything was fine, I was playing the game for weeks, no hardware changes but as soon as I bought the bronze pack and the spooky table deal is when the issue occured.
Sorry, I'm not familiar with that mouse, but if it's emulating a controller, that would do it.