The Battlefield 4 Thread 2015

randal said:
It's the taking the final bullet once you're safely in cover that drives me nuts, happened easily 5 times last night whilst playing. Seeing yourself safely behind cover and your attacker's angle way off for a clean shot in the killcam equals insta-rage for me at the moment.
Click to expand...

The one that really grinds me is coming around a corner and finding yourself like 1 on 5 - the enemy you concentrate your fire almost always lives - some random player in the crowd dies to your shots - usually one blocked by 2 other players and then you die to one of the players who was in the least likely position to shoot you. (Coming from COD4 where I'd usually take most if not all of them out in that situation makes me rage that I can't do the same in BF4 lol).

They really need to tighten up the way the game works when there are a lot of players with varying latency in the equation and I think the server boxes are becoming a bit "over-subscribed" - seeing a lot more tradekills and dying long after going into cover - this one the other day had me laughing though there are a couple of ways its explainable - especially with a mix of latency/slower server update in the equation.

https://www.youtube.com/watch?v=UMn6N2ew-rM

Tracert I did to the server I play on mostly - I know it doesn't show stuff like packetloss and jitter but my connection is pretty decent and I'm used to a much more responsive environment on a low latency connection coming from other FPS games :S

Tracing route to server23383.i3d.net [151.236.46.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 9 ms 9 ms 9 ms 31.55.187.160
5 9 ms 9 ms 9 ms 195.99.127.172
6 9 ms 9 ms 9 ms 195.99.127.13
7 9 ms 9 ms 9 ms ld5-linx.as29550.net [195.66.236.223]
8 9 ms 9 ms 9 ms ae1-cr1.rdg.as29550.net [91.186.5.241]
9 9 ms 9 ms 9 ms port49-a.19.magic.as29550.net [94.76.244.22]
10 9 ms 11 ms 9 ms server23383.i3d.net [151.236.46.161]

Trace complete.
 
Rroff said:
The one that really grinds me is coming around a corner and finding yourself like 1 on 5 - the enemy you concentrate your fire almost always lives - some random player in the crowd dies to your shots - usually one blocked by 2 other players and then you die to one of the players who was in the least likely position to shoot you. (Coming from COD4 where I'd usually take most if not all of them out in that situation makes me rage that I can't do the same in BF4 lol).

They really need to tighten up the way the game works when there are a lot of players with varying latency in the equation and I think the server boxes are becoming a bit "over-subscribed" - seeing a lot more tradekills and dying long after going into cover - this one the other day had me laughing though there are a couple of ways its explainable - especially with a mix of latency/slower server update in the equation.

https://www.youtube.com/watch?v=UMn6N2ew-rM

Tracert I did to the server I play on mostly - I know it doesn't show stuff like packetloss and jitter but my connection is pretty decent and I'm used to a much more responsive environment on a low latency connection coming from other FPS games :S

Tracing route to server23383.i3d.net [151.236.46.161]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 * * * Request timed out.
4 9 ms 9 ms 9 ms 31.55.187.160
5 9 ms 9 ms 9 ms 195.99.127.172
6 9 ms 9 ms 9 ms 195.99.127.13
7 9 ms 9 ms 9 ms ld5-linx.as29550.net [195.66.236.223]
8 9 ms 9 ms 9 ms ae1-cr1.rdg.as29550.net [91.186.5.241]
9 9 ms 9 ms 9 ms port49-a.19.magic.as29550.net [94.76.244.22]
10 9 ms 11 ms 9 ms server23383.i3d.net [151.236.46.161]

Trace complete.
Click to expand...

Noob error. Video is private.
 
CrispyOtter said:
Rroff... nothing suspicious at all with that death... just USAS explosive rounds.
Click to expand...

Its not about suspicious - just the "netcode" makes me laugh - with the relative positioning even with frag rounds he must have been shooting at me quite a bit before I saw the damage on my end (if you extrapolate it back from the start of the death cam he should have been visible standing there).

As I said though couple of ways its explainable i.e. corner peeking and shot, etc.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom