So, here's a bug that's been plaguing me on and off since near the end of Chapter 1. During intense combat, sometimes the controls will bug out horribly (playing with a wired Xbox 360 controller, Windows 7 64bit, default drivers - nothing special here) and while movement and camera control is possible, it will literally have a full second of delay between me pressing a direction and Geralt moving.

Last time this happened, I managed to escape from the fight I was in and saved game. Upon loading the save, the game appears to be working fine, and I can access menus and turn the camera, but no other inputs provide any response. Geralt just won't move, attack, use items, cast signs, etc. Completely unplayable.

I included this save so that hopefully someone at CDP can figure out what's breaking and (with a little luck) fix it by V1.3. I've seen this same bug reported by others, so it's at least a known or semi-common issue. I've lost a lot of progress to this bug, as once the controls start freaking out, there's nothing I can do but stop and load my previous game. It never fixes itself or returns to normal.

Here's the save file:
http://www.multiupload.com/N78448A1BC

Wow.... just, wow. I had no idea this bug would actually record into the save game. Well done supplying a save file demonstrating this. I loaded your game up, and indeed, no keyboard input is registered (I couldn't access the menu or anything), and the mouse only allowed for camera movement, no button clicks. I don't know if the fact that you were using a controller when making this save makes any difference (since I'm using keyboard/mouse) - it shouldn't, I guess. Anyway, perfect example of how this bug may manifest itself. I hope CDPR will take a look and try out your save, themselves.

The fact that it's recorded in saves would suggest that it's some deep scripting error of some sort. The weirdest thing is that during the initial phases of when the bug hits, movement still works, but happens after a very long, noticable delay. You push the analogue stick, and half a second later Geralt starts moving. Try to change direction and there's another pause, then he turns.

It's a pretty horrible game-breaking bug though, and the only solution is rolling back to your last non-corrupted save. Hopefully CDPR will fix it soon.

Interesting indeed. You can also send the save file and a dxdiag report to tw2support@thewitcher.com.

A DXDiag report probably wouldn't help. The bug almost certainly isn't caused by hardware, as the save itself carries the problem, and other people can observe it by loading it.

Aye, but send the link and your post to tw2support@thewitcher.com anyway - they're very friendly and helpful over there. :)

I really don't know. I play KBM and I experienced only some lags but the controls never stopped working. So I think it's possible that it might be related to hardware.

And tech support will ask for it anyway. :)

DXDiag might not help, but it doesn't hurt to send it to them either. Who knows, it might turn out to be a combination of software and hardware that caused the problem.

Some other possible causes to be considered are corrupted files during installation, corrupted patching (not use if the mod plays a part), etc.

The OP issue sounds similar to the issue when Geralt is interrupted while throwing bombs and the input controls except movement become unresponsive (including the camera angle lock on Geralt; in 3D space of the game).

Getting hit by creeps/monsters brought the controls back.

grats on getting a saved version of this bug.

Hardware issue could exist...I'd expect to see it related to the joystick*...but I'd ask the OP are you using a program such as wingman controller software that allows you to map keystrokes to your joystick...I use the term joystick because controller and such can be misinterpreted, plus its a funny word. I keep coming back to the idea that somehow programs like iType, wingman controller, etc somehow aren't communicating properly with the game causing the key input delay, but I've no experience programming games so I may be way off base.

I doubt it's a corrupted file on the user end, the number of people saying they are experiencing similar issues are too widespread. I've done a clean install from a fresh download and seen this bug show up as early as the second ballista part of the prologue.

I have theories on why the controls lock up, from a glitch with how the game sees what ranged weapons you have and what happens when you try used the bomb/trap/dagger when you actually have none, to a command dropping into an eternal loop so the game sits waiting for the result of the keyed input, an input that has an interruption clause associated with it, and this is why getting hit breaks the loop resetting the ability that cause the lock-up.

I'd rather wait longer than their current goal (end of july afaik) and have this input bug fixed.

Considering the bug can get saved it should be at least easy to track down the issue.

Completely standard USB-cabled Xbox 360 controller, running with the default drivers that Windows 7 grabbed automatically when I plugged it in. Absolutely no strangeness in hardware here. Only input devices plugged in are my mouse and keyboard (USB and wireless).

Not only that, but I installed Windows 7 Ultimate completely fresh last week. There's pretty much no room for error on this end. Hardware is rock solid, and I've not observed strange behavior in any other games.

i have a razer diamondback mouse that had the same issue ,i did rebind aard to mouse buttonn five ,i'm also using a zboard fang gamepad , i fixed the ultra freeze problem by using an older mouse , i had to unplug the razer from the system to cure the problem ,the razer driver i'm using is the latest i think its 6.02 us , i thought my mouse just went south , now i think some hardware needs to be updated

Hate to be a dick, but now is the time. A member of the team, Andrej? Has claimed this issue is subjective. No way. I'm sorry, but if they meant for this to happen then they misjudged, with all due respect.

All that is left to say is the combat system is broken, and they need to fix it. Thank god they had the much smaller PC test-base here before things took center stage on consoles.

i have no problems since i switched out my mouse . i even lost a lot of my stutter ,now it only hitches when i go through doors or when the game loads assets (the spinning snake bottom rt hand corner)