PatchHeader

Update 3.4

11/07/2016 10:00 AM

Pulse

Patch 3.4 will be deployed on July 13th for all platforms.

Translated versions of these patch notes will be published as quickly as possible.

General Tweaks and Improvements

Operator Balancing

Pulse has better visibility, more reliable information, and easier to read feedback.

For the update to Pulse in Patch 3.4, we wanted to give him a better awareness by increasing the visibility he gets of his gadget. A lot of times players would get caught off-guard while using Pulse's gadget, and we intend for this new update to improve situations like that. Pulse’s gadget detection marks were static on the screen and this was sometimes difficult to interpret. We have changed these marks to provide a better representation of the enemy’s world position.


After Update 3.4, if you detect an enemy and look away, the “ring” will stay at the enemy’s position, and not remain on the screen at the same position it was when the enemy was detected. We felt that we weren’t fully delivering the experience and the fantasy of the heartbeat scanner with the previous design. We hope you will enjoy the new graphic, audio and visual update we are applying to the gadget as well!


PulseGIF

Full patch notes here.

After reviewing the rest of the patch notes, we recommend you join the discussion on the subreddit or forums!

Recommended Articles

[2018-09-17]Y3S3

Y3S3.1 Patch Notes

The first patch after the season launches is generally a much lighter patch. As such, you will not see the same level of fixes as a Season launch. Patch Y3S3.1 deploys on PC on Tuesday, September 18th, and console to follow later in the week.

17/09/201812:00 PM

Read more

[2018-09-14] MM Degradation Blog Header

Matchmaking degradation following Operation Grim Sky

The Grim Sky update was deployed with improvements to the overall matchmaking flow aimed at making the initial game server selection process much smoother. Upon deployment, we noticed an increase in the number of matchmaking errors generated when compared to the Test Server phase. This is a summary of what happened, and the steps we took to fix it.

14/09/201812:00 PM

Read more