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

×
I am in a pickle, here, and any of you more experienced players may be able to help.
Here's the thing...I am stuck in prologue because I cannot aim the Ballista. The only command available to me is to cock the thing...it immedietley fires and I am attacked by soldiers...there is nothing that allows me to aim the thing to the required 1.5 degrees...is this a glitch or am I missing something?

Thanks!
SPOILERS SPOILER ALERT:










the one in the courtyard area that is under the pathway that Foltest is standing on?

when my game plays, there is one action to pull back the bolt> kill three guys;
one action to aim or whatever> kill two or three guys (varies);
then one more action to fire the thing> run to the stairs far across the thing >kill more guys and climb back to Foltest



Is that what you are getting?
avatar
marcvin1: I am in a pickle, here, and any of you more experienced players may be able to help.
Here's the thing...I am stuck in prologue because I cannot aim the Ballista. The only command available to me is to cock the thing...it immedietley fires and I am attacked by soldiers...there is nothing that allows me to aim the thing to the required 1.5 degrees...is this a glitch or am I missing something?

Thanks!
there is a QTE even where you have to press your LMB until the bar on the screen fill up. Look carefully, you may not see the bar on the middle, lower part of the screen.

If you do it right, you will have to do it 3 times: 1 to cock the ballista, 1 to aim it, 1 to fire it.

Or you can let it fail several times and get some XP killing guards.
avatar
Freewind: there is a QTE even where you have to press your LMB until the bar on the screen fill up. Look carefully, you may not see the bar on the middle, lower part of the screen.

If you do it right, you will have to do it 3 times: 1 to cock the ballista, 1 to aim it, 1 to fire it.

Or you can let it fail several times and get some XP killing guards.
You don't need to do the QTE to fire the ballista. Just to cock and aim it. The firing sequence just needs a single click.

The aiming QTE is the more difficult; this is the one that builds your XP and frustration level.
avatar
Freewind: there is a QTE even where you have to press your LMB until the bar on the screen fill up. Look carefully, you may not see the bar on the middle, lower part of the screen.

If you do it right, you will have to do it 3 times: 1 to cock the ballista, 1 to aim it, 1 to fire it.

Or you can let it fail several times and get some XP killing guards.
avatar
cjrgreen: You don't need to do the QTE to fire the ballista. Just to cock and aim it. The firing sequence just needs a single click.

The aiming QTE is the more difficult; this is the one that builds your XP and frustration level.
o O: somehow in my game, I feels that the game aims the ballista for me. Never have the problem where I fire a miss.
avatar
cjrgreen: You don't need to do the QTE to fire the ballista. Just to cock and aim it. The firing sequence just needs a single click.

The aiming QTE is the more difficult; this is the one that builds your XP and frustration level.
avatar
Freewind: o O: somehow in my game, I feels that the game aims the ballista for me. Never have the problem where I fire a miss.
It never misfires, but you have to crank like mad to aim it. If your setup has any problem with mouse responsiveness, you'll find it out here.
..... you all are wrong hes talking about a different ballista.

to OP, you cant use your mouse you must use the keyboard to aim + fire (spacebar)
avatar
cloud8521: ..... you all are wrong hes talking about a different ballista.

to OP, you cant use your mouse you must use the keyboard to aim + fire (spacebar)
No. He's talking about the ballista in the courtyard that you must cock, then fend off an attack (then aim and fend off another attack, then fire).

You're talking about the ballista that Foltest asks you to aim. You cannot cock that ballista, and you do not get attacked afterward. So it can't possibly be the one you claim it is.
Post edited June 07, 2011 by cjrgreen
avatar
cloud8521: ..... you all are wrong hes talking about a different ballista.

to OP, you cant use your mouse you must use the keyboard to aim + fire (spacebar)
avatar
cjrgreen: No. He's talking about the ballista in the courtyard that you must cock, then fend off an attack (then aim and fend off another attack, then fire).

You're talking about the ballista that Foltest asks you to aim. You cannot cock that ballista, and you do not get attacked afterward. So it can't possibly be the one you claim it is.
he cannot get stuck if he miss fire that ballista. The game still goes on regardless he scores a hit or not
avatar
cjrgreen: No. He's talking about the ballista in the courtyard that you must cock, then fend off an attack (then aim and fend off another attack, then fire).

You're talking about the ballista that Foltest asks you to aim. You cannot cock that ballista, and you do not get attacked afterward. So it can't possibly be the one you claim it is.
avatar
Freewind: he cannot get stuck if he miss fire that ballista. The game still goes on regardless he scores a hit or not
No, he said he cocked it and got attacked.

The only place that happens is with the ballista in the courtyard.

You are correct in that you cannot miss when you finally get to fire the ballista in the courtyard. But that is not what he said was happening. He's not even getting that far.
Post edited June 08, 2011 by cjrgreen
avatar
Freewind: he cannot get stuck if he miss fire that ballista. The game still goes on regardless he scores a hit or not
avatar
cjrgreen: No, he said he cocked it and got attacked.

The only place that happens is with the ballista in the courtyard.

You are correct in that you cannot miss when you finally get to fire the ballista in the courtyard. But that is not what he said was happening. He's not even getting that far.
I got through this by getting my wife to hold the mouse while I hit the left mouse button rapidly with both index fingers.
She wasn't pleased that she had to stand there while I did it two more times.
Can someone tell me if the game involves more of this button mashing.
I won't bother playing it if it does.
Certainly not my idea of a RPG.
avatar
cjrgreen: No, he said he cocked it and got attacked.

The only place that happens is with the ballista in the courtyard.

You are correct in that you cannot miss when you finally get to fire the ballista in the courtyard. But that is not what he said was happening. He's not even getting that far.
avatar
olnorton: I got through this by getting my wife to hold the mouse while I hit the left mouse button rapidly with both index fingers.
She wasn't pleased that she had to stand there while I did it two more times.
Can someone tell me if the game involves more of this button mashing.
I won't bother playing it if it does.
Certainly not my idea of a RPG.
Depending on choices you make, there may be up to ~ 5 more times you have to execute a similar mechanic. That sounds like a lot, if you have difficulty with it, but it doesn't feel like many really.

Quite a few people have trouble with them. Some just don't have the reflexes for it, and I empathize with that.

I think the main problem is that these QTEs (quick time events), as they are called, are not optimized well for the wide variety of PC configurations and specs.

If you come across another one you have trouble with try this:

1. Turn off "Difficult QTEs" in Gameplay options.

2. Lower your resolution for that moment. (Yeah, on first play, you don't know when they are coming. Just have to reload, change it, save, change back and reload.) This one seems to be the best trick for the most people.

3. Remap your Quick Attack button. The QTEs that require filling a bar are completed using the LMB, or quick attack by default. Change the binding and you can tap the keyboard instead. It seems like that could get confusing in one instance in particular, but it may work for you.
Post edited June 08, 2011 by hanns.g
Thanks for the quick reply hanns.
I wondered what that Difficult QTES was.
I got killed in the fistfight a little after that & now have to sit though a 10 minute cut scene to have another go. Is there anyway to skip the cut scenes?
avatar
olnorton: Thanks for the quick reply hanns.
I wondered what that Difficult QTES was.
I got killed in the fistfight a little after that & now have to sit though a 10 minute cut scene to have another go. Is there anyway to skip the cut scenes?
Cutscenes, yes. Right click or space bar, then right click.

There is no way to skip the QTEs, though, darn it.

I hope they eventually patch the option to take out QTE or allow for modding it out with a Software Developer Kit. It would not detract from the game at all. I don't mind them. I think most people are o.k. with them, but a few really hate them or can't do them. So why not make them optional?

Side note: I don't think that toggling Difficult QTEs changes the events that require filling a bar, or fistfights. There are a couple others you haven't encountered which that toggle applies to, which is why I suggest turning them off.

Regarding fistfights: I got caught off guard the first time I encountered that. If the "filler-up" ones gave you trouble, you can still get the hang of fistfights after a couple. You don't have to repetitively hit anything. Just watch for what section of the screen the letter pops up on. High=W, Low=S, Left=A and Right=D. Just tap the key once. You don't have to be super quick. It gives you a beat or two to respond.
Post edited June 08, 2011 by hanns.g
Everyone says theres enough time for the QTE's i barely get a blink im talking quarter of a second to see and react. I dont belive it relates to the game itself on the hard or unchecking, but when i run the game in SLI mode it just blinks or dont show up period. I think its a driver related issue if you run sli. but i could be wrong. But i have lost alot so called easy fist fights becuse this QTE's. Has anyone else noticed this and is running SLI by chance?