It's not that bad...

I brought up CPU because I've personally run the game on the lowest possible settings (including viewport scale) and managed to keep around 60 FPS on a shitty NVS 5400M, based on the GeForce 540M chip. However the CPU used was a mid-range mobile Ivy Bridge i5 and 8GB RAM.

Obviously you should upgrade both, but the CPU is the biggest bottleneck right now. You're going to want at least 4 threads if you want OW to start being GPU bottlenecked. For instance, a Sandy i3 handily beats the G3258 just because it has hyperthreading (dual core + HT).

http://www.mtndewkid.com/wp-content/uploads/2015/12/Mtn-Dew-Pitch-Black-16oz-Bottles.jpg

its a guilty pleasure ok

It would help but not very much.

You'll need both a new CPU and GPU for OW. You might be able to get by on the GPU front if you're okay playing at low, but you won't get respectable framerates even at low until you upgrade that CPU. Blizzard games are notoriously CPU-bound. I'd also consider going to 8GB of RAM.

it won't throttle anywhere near that

do you play borderless or full screen normally? and what OS?

also with that much CPU usage there must be something else going on in the background. what other processes are using the CPU? screenshot task manager's Processes (7) or Details (8, 10) tab, sorting by CPU usage

people that have to go on Wikipedia to figure out what dihydrogen monoxide means smh

i like how everyone has exactly two upvotes

edit: reverse psychology worked

i overdosed on water once

ill trade u my japanese text b4nny x clockwork for ur holo kaidus x sideshow

aim is independent of the actual shot, that's probably just the shit tickrate

No, TF2 only cares about the server's perspective. It does slightly adjust for really bad pings from the attacker, but never to the point that it blatantly overrides the server.

actually no. While that part sucks, blizzard actually wrote their netcode with "favor the shooter" in mind. The server will fudge hits in favor of whoever is shooting, so that if the shooters client saw the hit even when the server shows the enemy behind a wall now, it still gives them the hit. Which is even worse on the client of the enemy.

Playing back a POV demo from a different client without the right HUD won't disable the scope on that HUD. However, you can fairly easily determine that the script is trying to run by checking logs. Scripts are saved to the demo. Additionally they could just add part of the exploit to their HUD and if your script triggers it, then they'll know you're using it.

http://www.pcmag.com/media/images/447950-overwatch-logo.jpg?thumb=y&width=740&height=426