(note: I might be imagining things on this one, so read this with a little bit of skepticism)
This isn't really a bug as much as the way the game is programmed... I'm sure other people have had the same problem I have, when you encounter two arrows quickly in a row and for some reason there is the tendency for it to give you a miss for the first one and eliminate your combo. These types of arrows are much tougher to hit than others... in that you'll hit twice, and be reasonably sure you are on beat, but your combo will simply die and you get a miss, usually with an almost in there as well.
Consider a situation where you have two right arrow taps, right in a row. I think that what happens is, when you get those arrows, the second one takes priority in determining which one gets assigned your arrow input; here's what I mean. Divide it up into "moments" (32nd beats would be appropriate, I guess, but I'm probably wrong).
Moment: Score you get on which arrow
1: Average on the first arrow (early)
2: Good on the first arrow (early)
3: Perfect on the first arrow (right on time)
4: Average or Good on the second arrow (early) and a miss on the first arrow (because, since it's taking input for the second arrow right here, it believes that you have missed the first one, even though you are only hitting it a little late.
5: Perfect on second... so on...
So, assuming I'm right about this, the second arrow will dominate the first if you hit even JUST a little bit too late, even in the window for still getting a perfect, because you are in the window for determining the type of hit for the second arrow and the game just registers the first as a miss.
I'm sure I'm not just coming up with stupid rationalizations for sucky play, because on SM I can manage double taps very easily, whereas here I have to press extremely early to handle them without losing my combo.
Well, maybe this is all a crock. Sorry for wasting your time then... if I am right and can make a suggestion, arrange it so that the first arrow's window will outprioritize the second, so the window for the first arrow ends (either through being hit or just passing by) in the middle of the second one, rather than the second one starting in the middle of the first.
This isn't really a bug as much as the way the game is programmed... I'm sure other people have had the same problem I have, when you encounter two arrows quickly in a row and for some reason there is the tendency for it to give you a miss for the first one and eliminate your combo. These types of arrows are much tougher to hit than others... in that you'll hit twice, and be reasonably sure you are on beat, but your combo will simply die and you get a miss, usually with an almost in there as well.
Consider a situation where you have two right arrow taps, right in a row. I think that what happens is, when you get those arrows, the second one takes priority in determining which one gets assigned your arrow input; here's what I mean. Divide it up into "moments" (32nd beats would be appropriate, I guess, but I'm probably wrong).
Moment: Score you get on which arrow
1: Average on the first arrow (early)
2: Good on the first arrow (early)
3: Perfect on the first arrow (right on time)
4: Average or Good on the second arrow (early) and a miss on the first arrow (because, since it's taking input for the second arrow right here, it believes that you have missed the first one, even though you are only hitting it a little late.
5: Perfect on second... so on...
So, assuming I'm right about this, the second arrow will dominate the first if you hit even JUST a little bit too late, even in the window for still getting a perfect, because you are in the window for determining the type of hit for the second arrow and the game just registers the first as a miss.
I'm sure I'm not just coming up with stupid rationalizations for sucky play, because on SM I can manage double taps very easily, whereas here I have to press extremely early to handle them without losing my combo.
Well, maybe this is all a crock. Sorry for wasting your time then... if I am right and can make a suggestion, arrange it so that the first arrow's window will outprioritize the second, so the window for the first arrow ends (either through being hit or just passing by) in the middle of the second one, rather than the second one starting in the middle of the first.
Comment