Worgen said:
Atmos Duality said:
I have no idea why some of these companies leave aim assist in multiplayer.
because the only reason fps games work on consoles is because of aim assist, without it on multi then they would be vastly inferior to pc multi, instead of just inferior
A bit of a loaded response.
I don't think aim-assist is absolutely necessary for all console shooters.
As much as it pains me to admit it, I have to cite Halo Reach as evidence.
I just finished watching my two friends kick all manner of ass in Reach, and they didn't have Auto-Aim on. The bullets went where they were aimed.
Now, I will admit freely that by technical standards, a keyboard and mouse are superior.
However, you can adjust your game's relative motion/gameplay speed for the type of system you are making your game for (Console or PC).
Halo is really really slow; and so are a number of current gen FPS titles.
Compare this to say, Quake 2/3 or even Tribes multiplayer, and the difference is perfectly clear; the latter games are far more difficult to learn simply because they are faster, and it is far more difficult to aim (or in Tribes case, move).
(Before some troll jumps down my throat, these comparisons are strictly by *TECHNICAL STANDARDS*. These things are measurable differences, and have absolutely nothing to do with personal taste or opinion.)
So, the point here is that Console Shooters use Auto-Aim/Assist, but unless the developers made the game "too fast" for the controls, there is no NECESSITY for auto-aim.
I think many of these alleged 'AAA' game devs know this by now.
When you add auto-aim to a competitive game, it had better be your absolute last resort and absolutely necessary (Armored Core does this, and Armored Core had a fairly tough learning curve for the average gamer regardless), but most console shooters do not fall into this category.