It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
The Witcher 2why QTE is ruining this game(111 posts)(111 posts)
(111 posts)
Pages:
1
2
3
4
5
6
7
8
This is my favourite topic
Posted June 12, 2011
avatar
zerebrush: Hi,

first off: this is a fantastic game with everything the fantasy genre needs. From grafix to plot and everything in between >> there is nothing like it, honestly!

But: I tried but still can not fathom why ever those QTE's found their way into the game.
Just want to say I agree. Ok for boxing arm wrestling etc - really terrible otherwise. I can't look forward to playing the game anymore.
Posted June 12, 2011
avatar
zerebrush: I suppose there will be a lot more of these QTE-sequences, once Flotsam is history, but I am sure I will never see any of them, simply because because of the uninstall function.

Thank you for reading...
Thank you for playing. Since you uninstall over a minor annoyance which I say is nothing more then a distraction that does not add much but not a negative as you put it, you already made your point. Goodbye.
Posted June 12, 2011
Instead of QTEs, they should have given a choice. A few choices. Like the timed dialogue events.
Posted June 12, 2011
avatar
zerebrush: Hi,

first off: this is a fantastic game with everything the fantasy genre needs. From grafix to plot and everything in between >> there is nothing like it, honestly!

But: I tried but still can not fathom why ever those QTE's found their way into the game.
I mean, it might be alright (and even funny) during armwrestling, boxing or loading up a ballista, but to put QTE into key elements of the game is worse then announcing "Gothic 4" only to hand out "Arcania" - maybe some folks will know what I mean.

Actually I died enough times for three games by trying to outlive the QTE in Flotsam (freeing the elven women).
First it had been the dragon (during the prolog). While this only had been a mild spoiler this is followed up by the Kayran >> just hammering any key/mouse button in a mindless way to kill an endmonster? Not quite the cream of game making.

I suppose there will be a lot more of these QTE-sequences, once Flotsam is history, but I am sure I will never see any of them, simply because because of the uninstall function.

It is not because of having spent money for something that I can not use, it is a lot more about being disappointed in perhaps the most talented game makers all around today.

Thank you for reading...
QTE's were the culprit for you? Trust me, there's more to complain about than QTE's. Heavy Rain for the PS3 must be your personal hell.
Posted June 12, 2011
They claimed the QTE's offered alternative ways to kill bosses. Not really the case though, not in my play throughs. They just need to get rid of QTE's altogether, they were a bad idea and I can't imagine why such an intelligent team came to a different conclusion.
Posted June 12, 2011
While I have no problems with the QTEs themselves, I would prefer something better than what is essentially a minigame for these things. QTEs, in my personal experience, is simply a quick method for making the player think they are doing something important and still in control during a cutscene, and is a problem with the industry as a whole in my opinion.
Posted June 12, 2011
avatar
hanns.g: One could say this has been debated to death; but since it hasn't been "solved" I will comment in hopes of least getting devs' attention.

First of all, I don't mind them at all, personally.

Some people REALLY dislike them or have major impediments with reflexes. You may wonder how such poor reflexes can play the game at all, but on Easy the rest of the game is doable for bad "clickers."

So, I think a patch that makes ENTIRELY SKIPPING them an option is called for. (Disabling Difficulte QTEs does not equal skipping them.) For example, it would be as simple as making the Kayran fight go to cut scene and end when the 3rd or 4th tentacle is destroyed. Kinda changes the original design vision, but doesn't break the fight at all.

Even though I kinda like the QTEs, even do them on Hard, I would offer one more suggestion. The prompt symbols could be larger. Even when I know what is coming, I find myself staring at a small, fixed point on the screen awaiting the que. If you are gonna add an orange icon flashing on my screen, might as well make it visible. :)
avatar
zerebrush: I suppose there will be a lot more of these QTE-sequences, once Flotsam is history, but I am sure I will never see any of them, simply because because of the uninstall function.

It is not because of having spent money for something that I can not use, it is a lot more about being disappointed in perhaps the most talented game makers all around today.

Thank you for reading...
avatar
hanns.g: The vast majority of them are in the Prologue and Act I. I understand your frustration, but press on! You will love it.
"... getting dev's attention" - well: exactly my hope (and it really seems I am not alone in this - thank you all!).

About the visibility of some prompts - it is right, they are small, and I am sure I missed a lot of them running from A to B to do C and back again, but I will not try to make my list of "minor annoyances" larger then needed :).

If I would dislike this game, I certainly would not post here...
Posted June 12, 2011
avatar
FlintlockJazz: While I have no problems with the QTEs themselves, I would prefer something better than what is essentially a minigame for these things. QTEs, in my personal experience, is simply a quick method for making the player think they are doing something important and still in control during a cutscene, and is a problem with the industry as a whole in my opinion.
Completely concur. If they want a show-offy cinematic scene to end a fight, I can dig it. Just do it without the QTE. It adds very little and annoys too many people.
avatar
scampywiak: They claimed the QTE's offered alternative ways to kill bosses. Not really the case though, not in my play throughs. They just need to get rid of QTE's altogether, they were a bad idea and I can't imagine why such an intelligent team came to a different conclusion.
They outsmarted themselves! I do that all the time...
Post edited June 12, 2011 by hanns.g
Posted June 12, 2011
Edit: The script doesn't work while TW2 is running. I'll see if I can figure out why.

Ok, here's what I came up with (autohotkey script)

First, you gotta download and install Autohotkey from
http://www.autohotkey.com/download/

Put this code in a script file.
I just use Notepad and save the file as "F1rapidfire.ahk"


F1::
Loop
{
SetMouseDelay 30
Click
If (GetKeyState("F1","P")=0)
Break
}


Then run the script before launching your game.
You probably should close the script (it should be in your system tray) if you want F1 functionality back, though.
I don't actually have a save near any button mashy bits, so I haven't tested the script ... but it should work.

EDIT:
Crap. It doesn't work .. seems to be working outside of TW2, but not while the game is running.
Post edited June 12, 2011 by Danceofmasks
Posted June 12, 2011
avatar
zerebrush: Actually I died enough times for three games by trying to outlive the QTE in Flotsam (freeing the elven women).
Yeah, that was the part that bugged me. I died I think five times just because of the qte bars popping up every time I went to unbind somebody. Once you get the third woman free it's Witcher flambé!

It'd occurred to me that maybe my mistake was casting Quen just when I got to the top of the tower, but on second thought: the spreading flames were timed with each release (or failure to release, I suppose, but having never failed one of those I can't say).
Posted June 12, 2011
I absolutely hate the boxing QTE. And it's not because I have bad reflexes and keep failing them, in fact I can win any boxing fight without getting hit at all. But those QTEs remove every bit of tactic from boxing, it's simply pushing the button that is shown on the screen. Consolification ahhh :(
Posted June 12, 2011
avatar
zerebrush: Actually I died enough times for three games by trying to outlive the QTE in Flotsam (freeing the elven women).
avatar
Eoghain: Yeah, that was the part that bugged me. I died I think five times just because of the qte bars popping up every time I went to unbind somebody. Once you get the third woman free it's Witcher flambé!

It'd occurred to me that maybe my mistake was casting Quen just when I got to the top of the tower, but on second thought: the spreading flames were timed with each release (or failure to release, I suppose, but having never failed one of those I can't say).
From looking at reasons why autohotkey doesn't work, it's possible that the red engine is grabbing low level inputs from the devices.
While that's nice in theory, it can also cause inputs to be missed if the engine is overworked.

Is your game's framerate dropping during that section (due to excessive flames)?
If that's what happening, you may be doing everything right, but it's just poor engine performance that's causing you to fail.
Perhaps try lowering the graphics settings (or resolution) to see if it helps?
Posted June 12, 2011
avatar
Eoghain: Yeah, that was the part that bugged me. I died I think five times just because of the qte bars popping up every time I went to unbind somebody. Once you get the third woman free it's Witcher flambé!

It'd occurred to me that maybe my mistake was casting Quen just when I got to the top of the tower, but on second thought: the spreading flames were timed with each release (or failure to release, I suppose, but having never failed one of those I can't say).
avatar
Danceofmasks: From looking at reasons why autohotkey doesn't work, it's possible that the red engine is grabbing low level inputs from the devices.
While that's nice in theory, it can also cause inputs to be missed if the engine is overworked.

Is your game's framerate dropping during that section (due to excessive flames)?
If that's what happening, you may be doing everything right, but it's just poor engine performance that's causing you to fail.
Perhaps try lowering the graphics settings (or resolution) to see if it helps?
No, I have a decent system so my framerate is perfect at Ultra. I'd have to go back and try again to figure out what the problem was... after five tries I was finally able to get out onto the porch and jump... I think the final time I was just very slightly quicker in moving from person to person . . . but it wasn't framerate corruption, so far as I could tell. The only problem I've noticed moving from High to Ultra is a little more blur in moving the camera (and while others have said it: my game, too, tells me I have low system requirements and automatically resets every time I patch the game... as well as reconfiguring my keyboard settings, which is much much more of a hemorrhoid) -- don't remember offhand what I did to fix that, but probably it was the framerate I lowered again after all, while leaving nearly everything else at a maximum. ...Which would mean my first sentence is wrong: my framerate is perfect at High.

...But... it's an interesting idea. The framerate could be dropping without my even noticing.
Posted June 12, 2011
avatar
Eoghain: ...But... it's an interesting idea. The framerate could be dropping without my even noticing.
It's one reason I always keep FRAPS running.
Even when I'm not recording, it tells me what kind of framerates I'm getting,

I remember playing TW1 on a mediocre PC, and while it ran everything else great, the framerate tanked during times where there are a lot of flames.
I suspect a lot of people had more trouble with the beast due to that than the actual fight being cheap.
Posted June 13, 2011
avatar
Eoghain: Yeah, that was the part that bugged me. I died I think five times just because of the qte bars popping up every time I went to unbind somebody. Once you get the third woman free it's Witcher flambé!

It'd occurred to me that maybe my mistake was casting Quen just when I got to the top of the tower, but on second thought: the spreading flames were timed with each release (or failure to release, I suppose, but having never failed one of those I can't say).
avatar
Danceofmasks: From looking at reasons why autohotkey doesn't work, it's possible that the red engine is grabbing low level inputs from the devices.
While that's nice in theory, it can also cause inputs to be missed if the engine is overworked.

Is your game's framerate dropping during that section (due to excessive flames)?
If that's what happening, you may be doing everything right, but it's just poor engine performance that's causing you to fail.
Perhaps try lowering the graphics settings (or resolution) to see if it helps?
Danceofmasks -

even playing the game on minimum specs should not lead to parts of the game being "impossible" to get around.
I find it interesting that I can play in windowed mode (any screen res), while full screen gives me the blue screen. Not every time, and not in a predictable way.
I'm running a GeForce with one gig, CPU and machine specs a tad better then minimal.

So - just so that I can continue to play - I tried one of them trainers yesterday. Works pretty good (using the health feature only), but while freeing the last of the three elven woman >>> dropping dead, nice and crisp, AGAIN.
While I do not recommend the use of trainers, I found this behaviour interesting, just the same.
Post edited June 13, 2011 by zerebrush
Pages:
1
2
3
4
5
6
7
8
This is my favourite topic
Community
The Witcher 2why QTE is ruining this game(111 posts)(111 posts)
(111 posts)