Aim assist is broken. Only works sometimes.
CM EDIT:
Please see the current version of this thread here.
Product: Apex Legends
Platform:Xbox Series X
Please specify your platform model. Microsoft Xbox Series X
What is your gamertag/PSN ID/EA Account name? ExTiNkT 91
Please provide your squad mates' gamertag/PSN ID/EA Account name if possible.
Are you using any software with an overlay? No
Which Legend were you playing (if applicable)? Happens with all legends.
Which Legends were your squad mates using (if applicable)?
Where did the issue occur? In a match
Which part of the map or menu were you in? If you don't remember the exact name, please describe the area or what you were trying to do in the menu. Happens everywhere on all maps.
What were you doing when the issue occurred? E.g. respawning a squad mate at a beacon, using an ability, a squad mate left the game. Aiming/shooting at enemies
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? Happened in the very first match, and all matches afterwards.
When did this happen? (dd.mm.yy hh:mm)
How often does the bug occur? Often (50% - 99%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? No aim assist AT ALL when shooting at enemies.
What should be happening instead? Aim assist should be kicking in when aiming at enemies.
Steps: How can we find the bug ourselves? Easiest way would be to go into Firing Range and aim/ADS side to side over the dummies/bots. You'll notice that some of the bots have aim assist, but some of the other bots will have NO aim assist at all. This happens in all game modes against real players as well.
Aim assist only works maybe 30-40% of the time. Some enemies have aim assist, some don't. Very intermittent. You never really know
UPDATE- 22/01:
Message from the dev team:
“Hey everyone.
Thanks a lot for your videos and your posts.While I keep investigating, here are a few things that we can test meanwhile.
But first, something to keep in mind:
- if your target is moving in the same direction than you, then the AA is weaker, because there is less work to do to aim at your target (directional and rotational).
- If you're not moving (left stick), you don't have rotational AA
- So for @skykll21 (post #511), that's why stick drift was a thing.
- I agree that "Look Deadzone" to "none" tend to drift, even on new controllers. I'll see what I can do for that.Now, to speak about the videos everyone sent:
When the AA kicks-in, it's basically slowing down your acceleration while you are in a zone around the target and try to pull towards your target (there is more, but I keep it short for the sake of explanation):
- But it's not On/Off, the values (acceleration, direction, etc.) are doing a transition.
- To give you a fake example, we are not going from 1 to 0 instantly, but instead doing 1 / 0.9 / 0.8 / 0.7 / …
- And if you're going fast or have a High Look Sensitivity, then your acceleration might re-start before the AA finish slowing down, because you left the zone around the target, and we are transitioning back towards the acceleration wanted.
- You can see that especially on https://photos.onedrive.com/share/27FAF063FDEDDFDB!753?cid=27FAF063FDEDDFDB&resId=27FAF063FDEDDFDB!753&authkey=!ADCOXHplfKbogsU&ithint=video&e=xOYrYF
- The AA doesn't really have time to slow down since your acceleration is strong.
So can you try with a lower Look Sensitivity please? (and ALC Off, because otherwise, ALC override the params).
Like Look Sensitivity 3 or even 2. Just for a few tests.
To see if the AA really has time to slow down before your acceleration restart.
If you do, then great! And it might be a matter of tweaking that transition speed on our side, so you could go back to a higher sensitivity.But I do agree that it looked weird when you were doing a 360 slow rotation (https://photos.onedrive.com/share/27FAF063FDEDDFDB!754?cid=27FAF063FDEDDFDB&resId=27FAF063FDEDDFDB!754&authkey=!ALAqKaGjjsqTWiQ&ithint=video&e=oAjOKF), that's why I would like to see what is happening with low Sensitivity.
For the rotational AA, it looks legit.
Regarding this video: https://photos.onedrive.com/share/27FAF063FDEDDFDB!757?cid=27FAF063FDEDDFDB&resId=27FAF063FDEDDFDB!757&authkey=!ADlSkGpxn-VIDSc&ithint=video&e=adoCsx
If you're moving in the same direction than your target, the rotational is obviously less strong (what you called weak).
When the target was close to you (at 10 seconds), the AA was deactivated because of that (there is no AA on close targets).I'm still investigating, and I'll find what's going on.
Thanks a lot already for all those videos, that's really helping.If you are on PC and think you have the same issue, that's also extremely valuable because the debugging is faster, so if you can, please record a video showing the situation, and your settings (so I can try to repro with the same values).
Same thing if you're on console, please keep sharing your settings.
So:
- Controller settings.
- Being sure that you don't have any "Per Optic Settings" overriding your default settings.
- No ALC (or if it's On, please show me what are your settings here too).
Thanks again everyone.”The Dev Team
UPDATE: I've added some extra questions in light of what we are looking for to better investigate this, please check below:
To the ones that have already replied, my apologies and thanks for adding it up if possible.
Once again, folks, we do appreciate your patience and help so far. 🤗
Hello folks,
Our team is investigating it further, however, we are going to need a few details from everyone experiencing this:
- Do you play console or PC?
- Any controller used? Which one?
- Do you have Advanced Look Controls (ALC) enabled?
- What is your screen refresh rate?
- Does it happen in-game or in the firing range as well?
- Whats your aim assist setting?
- Please add a clip/video showing the issue, if possible.
-
Could you please test the firing range: do you have AA at the firing range?
Thank yall for gathering this extra info, we appreciate the patience and for sticking with us!
Accepted as solution for viewing purposes only. This issue is still under investigation.
