343i,
Aiming is broken beyond belief in Halo 3 and, though better, still wildly inconsistent in Reach due to aim acceleration. The reticle speed goes all over the place moving from slow to normal whenever any adjustment is made. Additionally, the reticle gets extremely slow (particularly in 3) when aim-assist clicks making it doubly inconsistent, slow when on a target, then less slow when off, then less slow again. Thus if you move from one target to the next, the velocity will change inconsistently. This makes these titles, which are supposed to be FPS’s, unplayable. I do not know how they got released. They play similar to when you drink alcoholic drinks in other FPS games, except worse, especially when using high sensitivity.
I will point out that this is not actually the reticle but the vision. What if your eyes or head moved initially very slowly every time you wanted to look at something? You would feel extremely dizzy and drunk and would never focus on anything correctly.
Can you imagine if Geometry Wars or any other title, even non-FPS, included a “feature” where the player starts slow and first and then moves at a normal speed every time you turned in a new direction? What would your score be? How frustrating would playing it be?
Can we get word in a bulletin whether aiming will be normal without acceleration (and, if applicable, tweaked deadzone settings, and aim-assist settings that SCALE WITH SENSITIVITY)
I should repeat that:
ACCELERATION AND AIM-ASSIST THAT SCALE WITH SENSITIVITY
ACCELERATION AND AIM-ASSIST THAT SCALE WITH SENSITIVITY
ACCELERATION AND AIM-ASSIST THAT SCALE WITH SENSITIVITY
ACCELERATION AND AIM-ASSIST THAT SCALE WITH SENSITIVITY
ACCELERATION AND AIM-ASSIST THAT SCALE WITH SENSITIVITY
or made adjustable or removed entirely, so players who are used to aiming at one speed do not get extreme slowdowns every single time they change direction, auto-aim catches, or releases, which is extremely often, so we can rely on eye-hand coordination developed on any normal 360 title. This is an essential issue for Halo 4 and I think we need to get some word on it. It would not an issue in Halo 2 (I cannot remember about the original; I will check sometime).
I would be less critical but this issue was not addressed in the Reach autoupdate and my default assumption is then that this will not be changed. It needs to be changed.