Apex Legends Dev Tracker

I'm passing this thread to the audio team as this has been a really big issue. But the info here is really great! Thank you all for your due diligence on trying to fix it on your end and reporting your finding. This really does help to nail this issue down.

Also for anyone else who sees this, please let us know as all the additional steps you've taken on your end to fix this as this is our next big issue to tackle. Also the situation in game you were in that it occurred (ie. Reviving someone, initial drop, characters in party, and console ( PS4 vs PS4 pro, etc)). Every single piece of info, no matter how small does go a long way. Videos also help.

Cheers and thanks you!

If the community finds it I usually personally see them here. We also have devs looking at our forums and others places too, so I'll get bugs that way. If you can, dm me a screenshot and I'll take a look. Thanks!

It true 8)

When I opened this sight line up for season 2 I had been waiting to see someone to nail this shot. Nice one!

No, the guns have different muzzle velocities.

Not ruling out that you haven't encountered a bug, but in local testing I cannot reproduce this at all. You can see results for a 500m test here. I also tried both the 4x and 6x at 200 and 300 meters with accurate results.

https://imgur.com/a/PzfH732

For the optics that do that, that should be fine, as long as you're adjusting your aim to the mildot after range finding but before firing.

If the 200 isn't lining up that's a bug. You can verify if it's working or not by pinging a location, checking the reported distance, lining up the mildot, firing, and checking the impact point vs. where you pinged.

That's a good point. The 50m had to do with the ranges that engagements actually tend to take place in Apex, and the exaggerated velocity and drag of the projectiles (there are reasons for that too, but they're outside the scope of this discussion). The combination created instances where targeted headshots at average engagement ranges (generally far less than 100m) would pass over the head of the target, due to the upward trajectory required to zero at 100m.

That said, I believe at some point we increased the sniper class weapon projectile velocities, so it seems worth revisiting the zero distance. I realize that user adjustable zero distances could also help resolve this, but it's a pretty meaty feature to add for a type of gameplay (long range sniping) that isn't really how Apex tends to be played. (that doesn't mean it's completely off the table)

Projectile has a velocity, the velocity is modified by gravity and drag. I think the calculations are done using Runge Kutta 4, which is pretty standard in games.

> ...but the bullet velocity is always constant

For the record, this is completely untrue. Where did you get such an idea?

Edited for clarity; quote shortened to relevant portion