Blizzard PLEASE add an Motion Blur option on the engine

[NighthAwk-13514]

@Dan-110607

High precision input have NOTHING to do about the tick rate

I think you may be confused about the purpose of the feature. It has literally everything to do with tick rate. I suggest you re-read the article that describes it. What I mention it actually the first paragraph of the post:

New Feature – High Precision Mouse Input (Gameplay Option)

Hi everyone! I’m Derek, a gameplay engineer on Overwatch and wanted to run through this new feature in version 1.42, and exactly what it does and how it works. First, a quick summary on how aiming and shooting happens in Overwatch. Overwatch simulates (or ticks) every 16 milliseconds, or at 62.5Hz. Each tick, we update the players aiming direction based on whatever raw inputs we’ve received from the mouse hardware since the previous tick. If the player has pressed primary fire, we then launch t…

@DerekMulder-1909

First, a quick summary on how aiming and shooting happens in Overwatch. Overwatch simulates (or ticks) every 16 milliseconds, or at 62.5Hz. Each tick, we update the players aiming direction based on whatever raw inputs we’ve received from the mouse hardware since the previous tick. If the player has pressed primary fire, we then launch their shot in that direction (assuming they are alive, have ammo, aren’t in the middle of some other action, etc.)

The problem is that the simulation (tick) of the engine is fixed but the rendering is interpolated and variable. The location where your camera is facing and the recorded location of where you shot were seen differently between the two threads in the engine. Under normal slow-moving conditions, the difference between those two is very small, and thus you wont notice much of a difference. but during very fast flick shots, those two points can be very far apart. This gives a disconnect from where the user thought they clicked, and where they actually did.

@Dan-110607

This is EXACTLY why I died as Tracer in the video above

You died in the clip above because the replay is not accurate to what happened, and he clicked your head quickly enough that the replay was unable to record it with a high enough precision.

@Dan-110607

Still, it’s WAY off isn’t? The replay isn’t perfectly accurate exactly because what I explained above.

The replay isn’t accurate because mouse input is not recorded at the same rate as on the client, therefore some data is missing and interpolated.

@Dan-110607

You’re saying that you should have “pristine” jarring and precise frames because it would lead to more precise shoots. I think not.

No, I’m saying you should have pristine precise frames because it allows your brain to see more detail. The higher the clarity and distinction of the visual, the easier it is to keep track of.

@Dan-110607

If fine detail is so important to shoot. Then we should see the EXACT hitboxes of the players and not an silhoutte that are extremely mismatched from the actual hitboxes.

There is a pretty important distinction here. Visual representations of the meshes are always confined to the hitboxes. They are designed such that if you shoot at the visual, you achieve a hit, but then also give some leeway. Yes the interpolation and rollback does provide some inaccuracy here, but using per-object motion blur degrades the detail of the information, which in turns degrades the precision of your shot. By adding motion blur to the mix, you are effectively losing visual information that can help determine the current precision of the hitbox. The tradeoff is that the animation and movement will appear smoother, but smoother in this case reduces the accuracy of the data. Any rendered information that is post processed is, by definition, not accurate to the original mesh data.