Product: Apex Legends
Platform:PC
Please specify your platform model. PC
AMD or Nvidia Model Number GTX 1080
Enter RAM memory size in GB 16
What is your gamertag/PSN ID/EA Account name? AUGZUGA
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)? Any legend
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. This happens regardless of location
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 down sight
Did your squad mates also experience the issue? Yes
How many matches had you played in a row before the issue occurred? This occurs every single time and is a flaw in implementation
When did this happen? (dd.mm.yy hh:mm)
How often does the bug occur? Every time (100%)
How severe is your issue? Major impacts to gameplay
What happens when the bug occurs? When ANY ADS zoom multiplier is used the sensitivity is not scaled proportional to the FOV during the zoom in animation. It appears that the multiplier is used immediately when the aim down sight key (right click) is used. This means that for a multiplier greater than 1 your sensitivity increases during the transition between FOVs causing you to overshoot the expected target if moving the mouse at the same time as zooming in.
What should be happening instead? The sensitivity should change proportional to the FOV change. It should not be possible, for a constant mouse distance movement,to rotate MORE when performing a ADS transition than simply staying on hipfire.
Steps: How can we find the bug ourselves? 1- Change the ADS sensitivity value to a value greater than 1 (works for every single scope and magnification level. higher values accentuate the problem). 2- Use a script (kovaak sensitivity matcher works great) to move the mouse a constant distance. This works best if set to perform an exact 360 degree rotation when hip firing 3- run the script while hip firing notice the exact full rotation 4- run the script while ADS, notice how the angular change is less than 360 degrees, which is as expected. 5- run the script again while taping the aim down sight button at least once to engage the aim down sight animation. Notice how the angular change is now GREATER than the rotation achieved during hipfire. Notice also how the velocity of rotation immediately increases when the aim down sight key is pressed.
The moment you press your aim down sight key, apex multiplies your base sensitivity by the ADS multiplier you have set for the final zoom level you are zooming into, without performing a smooth transition. This means that for the entire period of time between when you right click and when you are fully zoomed in, you have a sensitivity that is higher than your hipfire sensitivity. This is a completely non physical result and something that is practically impossible to adapt to.
How does this affect players?
1- Quick scope type shots become wildly unpredictable, since each scope has a different ADS time you cannot easily adapt to the way sensitivity is being changed
2- Lots of people like to quick scope with shotguns (PK) before firing each round, this is probably effecting those players heavily.
3- Whenever you transition between hipfire and ADS or vise versa. (enemy slides into you and you zoom out). Sensitivity does not scale properly causing you to lose tracking of the target.
4- Preventing you from improving: because this is such a counter intuitive and subtle mechanic, most people will never notice it and it will be very hard to adapt to and work at improving. Shots will be missed by a few pixels without really understanding why
This is unacceptable aim mechanic behavior for a game trying to make a name for itself as a competitive Esport shooter. Clearly the code already exists to smoothly transition sensitivity between zoom levels since everything works as expected for Zoom sensitivity multiplier values of 1. It should be possible to to implement the same function for other values than 1
