It seems that the level of maturity in this board has gone down the drain. You be basically flamed and insulted for being disagreed and term as a moron.

I wonder if i can hall him a moron too when i disagree with him. Seriously IF the game is working as INTENDED that there should be a delay of 1-2 seconds AFTER an action, player shall be INFORMED that it was intended. Otherwise a casual gamer would think that it IS a bug due to irresponsiveness.

I have no freaking idea if requesting that to be informed in the manual will be called moron? I have nothing much to response with this kind of behaviour.

I can't believe some people are in denial about the lag issues. If it were the same amount of lag under the same circumstances, they might have a point. But that's not the case.

This isn't the recovery frames of Street Fighter at work, trust me. Street Fighter works because those recovery frames are consistent and crafted with precision.

I use bombs frequently and the behavior of this "recovery time" some people are talking about is very erratic witch leads me to believe it's and input issue, not an intended delay. I have had instances where I toss a bomb at a group of enemies rushing down on me and I am able to roll backwards while Geralts arm is still extended from the throw, i.e. instantaneously. Other times he will stand there an do nothing from 2-3 seconds while he gets surrounded.

Shhh... you be called a moron for stating the obvious..

I'm not too worried about it ;)

There is definitely a real issue with input lag. This is not about performing action chains. I have experienced many occasions when I am simply standing in town, and I press the key to run forward, and the response is delayed.

This may simply be a system issue, my computer struggling at times to keep up with the game (the game is not freezing though, action around me continues as normal). Or it may be a fixable bug with how the game handles inputs, I have no idea.

There's recovery time between moves that's natural, and I think people are confusing it and unresponsive controls. Some people experience sluggish combat and others don't. It's not a part of the game, because the short time I can't do anything between moves (recovery frames) is fair and consistent (clearly I have none of this lag), so adding a cooldown timer like archaven suggested or anything like that is unnecessary since two-second delays aren't a part of the game.

I do wish we could figure out what causes it. People with better systems than mine have experienced it, so I don't think it's a hardware thing. Maybe something OS-related? I'm running XP on the machine with Witcher 2 installed, if anyone's interested.

Nope, exactly the same issues on Win7/amd quad@3,2GHz/GTX460OC and XP/intel 2core@2,4GHz/same gpu.

I mean that I don't experience any problems on XP. All of the lag I've heard of up to this point (which, to be fair, is only 3 or 4 people) is from people running Windows 7. It's starting to get a bit suspicious.

I have only had NOTICEABLE lag exactly once in a complete play through. Not saying that it doesn't exist, but obviously it is worse for some folks and not for others.

My version of "input lag" is of a different nature. Instead of Geralt not responding to key presses, I found that between 2 performed actions there are inconsistent pause. Here is my thread with a few videos.

A few things I find suspect:
a) Compared to the others actions, the pause before running (WASD) takes effect after casting signs / hitting an enemy / blocking / getting blocked / getting hit is noticeably longer (well, at least to me). The thing is, this only happens if you are standing still previously, but if you were running while doing the first action, such longer delay is not present.
- This is esp. obvious to me when I reach the part of game where I am not allowed to roll. It's not 2-5 seconds, mind you, but it's more than enough time for the enemies to get in a few hits, causing a... chain of reaction.

b) Blocking after getting hit by enemy also exhibits the lengthier delay shown in running.

c) Something about unable to cast sign for a while after rolling
- Felt this deeply with my Sign heavy character, maybe I should record a video for this.

Edit: Aha, after reviewing the video "Get hit" again, I noticed one thing. If you were standing still before, and pressing run (WASD) after performing any action, you get the complete recovery frame (knees bent lower, return to default/neutral posture, 0.5 s pause - ok I'm making this number up). Contrary to this, if you choose to dodge, attack or cast signs after getting hit, your action is executed after "knees bent lower" part instead of getting full deal.

Note: Maybe it's OS problem, I can't say it's not because I'm using Windows 7 after all.

This recovery time issue seems to demonstrate the unpredictability of the Witcher 2 under different system configurations. Some may have two very different setups and still get the same problem while others ask what on earth that person is talking about.

For instance, with the Kayran quick time event issue that some (like myself) have complained about there seems to be no consensus over exactly what causes it. I suspect that this supposed recovery time issue shares the same problem with being unable to determine the exact cause.

It's a bit different, Kayran issue seems to exhibit on some lower end computers, where it doesn't register clicks fast enough. Which admittedly is weird, since on my computer, about 4 clicks is enough to seal the deal.

For the recovery frame issue, it's not a hardware issue
1. I have a mid-end hardware (is there even such a word ? :)
2. It is inconsistent with the other actions (attacking / dodging / casting signs)

Ah, I missed the part about XP in your post. Sorry about that.

But yeah, I'm kind of using "lag" and "non-execution of key presses" interchangeably.

Maybe it has something to do with the way the game was coded, like the same reason it's impossible to change the volume with your keyboard or take screenshots with the print screen key? Just a random thought based on the fact that clicks get thrown out altogether rather than just delayed.