- Joined
- Jun 15, 2014
Looking back at the comparison gifs here, it appears to be a timing issue inherent to the keyboard input sequence alone - the QTE sequences are similar but NOT identical, as the keyboard sequence starts with word typing, whereas the mouse just has one additional slider instead.
But when it gets to that first circle, the 'timer' display which I believe is that red 'pulse' is giving the player less than a second to complete it - less time than possible to even complete it between holding the spacebar down and letting the circle go around because by the time the program recognizes input, the QTE has already triggered a fail state flag and resets. The speed of the pulse also is easily twice as fast as the same circles in the mouse sequence.
However, that is only half the issue when the sequences are compared. In addition to twice the speed in the pulse, it looks like the keyboard sequence puts the start flag for the QTE timers BEFORE the instructions to actually fade-in the graphics AND to receive input. As I would expect this to be a blocked out repeating loop in sequence, each fail-reset cycle merely generates the circle running the clock before it should each time. Compared to how the mouse sequence circles fully fade into view slightly slower than the keyboard sequence circles, and BEFORE starting a much slower timer. In the time it takes for one failed mouse circle QTE to even START fading out, the keyboard circle QTE has already fully reset two times.
