Well yeah, but those games are incredibly less demanding of your computer.

I've heard rumors that decreasing the game resolution can help with the QTEs. You might try that before giving up on it, especially since you got a second opinion and it sounds like it's not a problem of you being unable to click fast enough. It seems as though playing at a higher resolution than your computer can really handle leads to only a certain number of mouse clicks being registered, which would then make filling up the QTE bar nigh impossible.

It wouldn't be as pretty, but you could always save after the QTE and revert back to your previous resolution.

Funny you should say that - my son said exactly the same thing a short while back: I set the game res right down to near rock bottom - and changed the screen res to match. Bingo - I sailed through it like - what's the problem! It took less than three minutes, the hardest part being getting up the slope at the end! (which I obviously hadn't done before) - but suddenly it was all over. Then, I switched back to the 'normal resolution again. I hoipe there are no more of this type of qte to contend with in this game.

So, anyone else having the same problems, it definitely (to me) looks like an issue (dare I say bug?) regarding the mouse clicks not being recognised by the system. I haven't checked but it may be possible to re-assign a keyboard key to he lmb temporarily as another way to get round the problem.

The really annoying thing is the game, if left to auto detect the settings, has almost everything enabled at the highest settings - and it then jerks so badly it is totally unwatchable, let alone playable.

What are your PC specs anyway?

Glad you got through it. There might be one more time where you have to clicky-clicky, but not on a boss. (There will be a QTE on a boss, just to be clear, but it is not a bar filler-up.)

You could call it a bug, since it is a "common" problem. However, getting video settings right fixes it; and, the better the video card, the less trouble, it seems. (There are also the miriad other PC configurations that can mess it up, as usual.) So, maybe more along the lines of not optimized for a range of systems very well.

Regarding your overall video performance, perhaps if you post your specs (maybe in another thread or new one) somebody with similar rig can point you in the right direction.

I'll post them here, then elsewhere if it is thought pertinent.

Intel 4 core i5, 650 @ 3.2 GHz
RAM 6GB
OS Win7 64Bit
HD 1TB
Graphics ATI Radeon 5450 with 1GB RAM
Monitor 23"

I suspect the graphic card isn't man enough to handle the 23" monitor for games (though it handled FallOut3 etc smooth as silk), as looking at the cost it is a real cheapo. Lets the side down a bit on an otherwise mid range machine I reckon.

The 1GB VRAM is a little better for gaming but the 5450 is not optimal for gaming as you suspected. It does everything including blu-ray decoding well save gaming, unfortunately. Fallout 3 is a much more dated game. I almost maxed that out with an 8800 GTX/T9300 which is about a year or two older than yours.

You run to the left, where you can run on the pieces of broken bridge to the kayrans head.
I couldn't find it myself to, but I found a video walkthrough on youtube.

I can now confirm categorically that, in my case at least, the graphics card was the problem. I took the machine back to a computer shop an they confirmed that the Witcher 2 is one of the most demanding games. Anyway, they installed a frame speed checker (FRAPS I believe), and tested it while Witcher 2 was running ... a miserable 10, and even less! The chap then did lots of exploring and tests to come up with a graphics card which didn't cost an arm and a leg, and finally settled on an nvidia GTx460 SE - not the top of the range by any means, but he felt it would be OK. It needed a new power supply fitted as well (old one was just 300Watts). Anyway its a couple of hours later - I'm home again and now the game runs with most of the options enabled (I don't like the blur anyway) - and it plays smooth as silk. No more jerkiness whatsoever on anything. So I tried the Kayran again ... absolute doddle. No problems whatsoever. Now I can see why some say it is easy - and others find it absolutely impossible...

So, anyone having a problem with getting the QTE bar up to full in the Kayran challenge, I really do suggest you have a good look at the graphics card - as others here have suggested - and make sure your power supply is up to any card that gets fitted.

I cannot believe just how much better the game looks, and how smoothly it plays now with practically all the options 'ticked' - and this is by no means a top gaming card.

Thanks to all here for the help and patience.

I started this on an ati HD5770 and was having no real problems, but have moved to an Nvidia GTX560ti . I believe some of that trouble filling the bar could be mouse related as well. I have been using a wireless mouse and had the batteries die while playing with Kayran. : )

GTX 460 is still quite good though. Glad you're enjoying.

Keys B, G, H and others are not used. Go to your user.ini file in Documents\Witcher 2\Config folder and add this line: IK_B=(Gamekey=GI_AttackFast,Value=1.000000) This will allow you to use either the mouse button or the B key. I tried it and it worked.

I really need help with this. I have tried many times, and been unable to get the Kayran to collapse the bridge on itself. If anyone could help me, I would really appreciate it.

This is my save - (I think...)
http://hotfile.com/dl/120937210/5927eae/save.rar.html


Thanks.

Before someone plays through this for you - have you tried the suggestions above? And there is a number of other posts about this that you could find with a search for "Kayran"

If you still can't get through after lowering your resolution/video settings - then I'm sure someone will help out.

Weight: 554/300

Oh, hell no. Are you using an unlimited carry weight mod?

Yeah. Someone else can handle this one.

LOL...

OK, I got it. Here - https://www.sendthisfile.com/qZA1lzOjqvU3kWKPVES8b5HX

Ya, it would be nice to know you're overweight to begin with...