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
Discussions Rules and Guidelines
Report this post
....
Sometimes, when a controller is present, controller "drift" can cause problems, even in situations where the player is using a keyboard and especially in situations in which a game can be played with a controller.
You have an issue where your are having a control problem in your game and the game is, apparently, detecting some sort of input regarding your character's movements that is not being purposefully input by you.
So, is it your keyboard? It might be, I don't know. (I doubt it, unless it's wireless and you're having some issues, there.) But, the most common source for this problem is usually another I/O device, like a controller, causing a conflict. That is why I suggested it. (Other devices, like even a camera with drivers running and that has a thumb-controller on it so you can scroll through pictures can cause similar problems in a game.)
So, you don't have any other I/O devices that could be causing this problem, right? Great. Good for you.
Oh, and you're welcome. You're welcome to the attempt I made to try to help you. You're also welcome to go stand in a closet and yell at yourself for being a jerk and gleefully jumping on the oppotunity to demonstrate that through the misdirected and improper righteous anger you just dished out to someone that just tried to help you.
Didn't you read my post? Did you read the "If" part? That's a word, you know. My post is a conditional statement and, if you are able to comprehend a full English sentence, which may not be the case, it clearly does not suggest that you were referring to a controller in your opening post.
But, I have little hope that you'll understand this. So, there's still the closet - Go yell in there and maybe someone will come to help you.
Let's start this again:
You don't have any analog devices connected to the computer, correct? (By analog, I mean things like controllers, analog joysticks, other devices that have thumbcontrollers or joysticks on them and the like.)
Are you using a wireless keyboard?
Does your keyboard require any special drivers? Are these updated and do they have any special settings that you can control that could cause this issue?
Does your keyboard have any analog input devices on it? (Joystick-like devices, touchpad, etc..)
When you say the character walks on his own, you're saying that the character continues to walk and can not be stopped by any keyboard input?
And, though it may seem strange, your keyboard isn't really dirty, right? You haven't spilled a drink in it, it appears relatively dust-free, etc?
2. No, a laptop keyboard
3. No
4. It does have a touchpad due to the fact it's a laptop keyboard, but there's nothing interfering it.
5. Yes, he can be stopped, but only by holding S for 5 seconds instead of one, or any other key of movement
6. Nope, not dirty, i don't have this issue with other games.
Try disabling this. For me, using an HP Laptop, I can disable the touchpad by double-tapping a small, printed, square in the upper-left-hand corner of the pad area. I know it's weird to assume a touchpad might have "drift", but it could be causing issues with the game's controls. (My touchpad on my laptop doesn't, but that doesn't mean that some others might not.)
Just a edited-in note: Games that are designed to accept analog inputs often monitor for those, even though you're not using such. Older games, especially, have the tendency to accept just about any anolog noise if it remotely resembles input they're coded for. That's why it's usually the first place to check when you're having controller related issues that appear to act like analog "drift."