{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
1/11/2019 4:53:25 AM
4
What they also do need - is to correct "auto-aim" that still exists even when playing at PC using keyboard and mouse. I don't mean general "lock on before launch" kind of aim that is most obvious on bows fired at distant target - should it be moving, your arrow will trail and hit.
What I mean, they should make point of aim being point of impact. Currently there is apparently some sort of "homing beacon" at all mobs, where all projectiles are guided to. It's fine on open terrain, but should target be partially obscured by an obstacle, then your projectile will hit said obstacle, and not target's visible part of body. It is again, most obvious with bows fired at relatively long distances (target can fit into bow's sight "box"). I'm not sure what is causing this, but it is nearly impossible to actually hit target's limb, when limb is the only thing that is protruding from behind said obstacle.
English
-
It’s annoying but the higher aim assist weapons tend to due that and no surprise to anyone but it’s more for pvp so once again we pve players get screwed by pvp heck I’ve had my weapon track an enemy and all I was doing was jumping over them
-
But I play PC version with keyboard and mouse and turned off all auto-aim settings that I was able to find! Autorifles, to some extent (I simply don't have as much experience with them) handguns, and Fighting Lion are, apparently, not susceptible to this, as I was able to fire at limbs or partially visible targets (or completely miss tightly packed group of targets with Lion), without hitting an obstacle they were hiding behind. Actually I was surprised you can shoot Cabal Phalanx's hand! Sadly, not the Taken Phalanx - if there is shield up front, it seems all bullets will hit shield, even if visually there is enough "meat" to inflict damage. Unfortunately neither of those weapons has sufficiently tight spread and punch at range to make them useful for long range shooting. It took me 3 magazines from Hazard of the Cast in semi-auto to kill a distant dreg. But at least I could kill him, as arrows were "gliding" towards the obstructed body. *shrugs* Oh well. :)
-
I can’t speak much for pc I don’t play it on it but on console majority of the player base uses high aim assist weapons I know I did for sniping til I got good at it on d1 and started using lower aim assist ones
-
My experience with consoles is limited, to be honest, due to my "physical" incompatibility between me and gamepads. So I do not really remember my impressions well. I do recall regular "insult sword fighting":) between PC and console gamers regarding accuracy and aim assist, but as not being able to access both sides of the story, I preferred to chuckle on the inside, so to speak:). I understand company's desire to save money on using as unified system as possible across all platforms, but all my previous experience combined... "rebels" (due to lack of better words) against what I see in Destiny 2. I don't mind "lock on before launch" feature present in bows, it is indeed fun to use them even at long ranges with this feature, but I want consistency both in terms of "point of aim=point of impact" and "if I see it - I can hit it". As I don't have access to game's "internals", as more PC/modding-friendly games allow us, I can't explain what's exactly wrong (such as "hitbox is incorrect", but at times not being able to hit what I am aiming it is quite irritating.
