Yeah, it would explain as to why sometimes it feels like I'm getting kills where I know it should have taken longer and when sometimes I just drop dead for no reason.
Also kind of explains Onboards video where a soldier just shot him dead within seconds and all you heard was one or two shots being fired (I figured it was just a sound-bug or something at first but it might have been this bug).
This game is really broken and it's been almost a month since release where things kind of have been fixed.
I'm strongly thinking of not buying premium, even from the mexico store.
Biggest joke, that it was happening in the beta, and dice said that hit indication on user's end was messed up. So up to now, that is what I believed in. But in actuality, most of those OHKs were in fact OHKs.
I wonder if it's the same with other body parts, and at different distances.
Sig too big. -Nothing is too big for Fedor. Expect a nasty armbar.
Since I bought this shit, day one purchase, I only had like 2 crashes in the first days.
Since then, no problems whatsoever. Usually i'm playing for like 2 hours.
/bragging mode off
>>>> >>>>>>> >>>>>>>>> ♪ Viva La Vida ♪ <<<<<< <<<<< <<<<<< <<<
I don't wish to be argumentative.. But wouldn't a headshot kinda kill you? I mean, sure, it's a game, and dying isn't exactly fun... but most games reward a clean headshot with a one-shot kill... is this really a bug, or is it a random instadeath reward for scoring the headshot?
Playing Valheim every weekday at 10pm GMT - twitch.tv/kaltern
Follow me on Twitter if you feel like it... @kaltern
Well, there's 2xmultiplier to headshots.
The problem isn't that "it's not real to be shot in da headz lots" but more that it's inconsistent and broken.
Either make headshots one hit kills (would ruin the game) or fix it.
Well that video does explain some of the cases where my target dies...but still gets me too.
I still don't get shit like Krest does though, the only times where I try to hit someone and get 0 hit markers is when he's lagging like shit and he's warping around. You can easily tell if someone's got a lot of packet loss (sup Germany, a decade and a half of that shit now), because their animations will all be out of sync. And that's just the BF netcode for you. Always has been.
To draw a comparison, in CS a high ping only affects the person with that ping, they'll see shit desyncing. High packet loss will make them warp on other people's screens. A higher interpolation value will reduce that effect.
In BF movement is very tightly tied to the data stream; so missing packets will make movement seem weird. Because of the game's inherent interpolation, that means that someone with tiny bits of packet loss and a decent ping will be fine, but with a lot of packet loss half of their movement (which is a lot more subtle in BF than in a lot of other games) is lost. Latency (ping) on the other hand will delay movement because of that and results in the CS: S syndrome, where what you see on screen is actually old stuff. If you go up against someone with ping 100-120 and he's running from right to left, be prepared to shoot way ahead of the model on your screen, because what you see happened in the past
Yeah, it would explain as to why sometimes it feels like I'm getting kills where I know it should have taken longer and when sometimes I just drop dead for no reason.
Also kind of explains Onboards video where a soldier just shot him dead within seconds and all you heard was one or two shots being fired (I figured it was just a sound-bug or something at first but it might have been this bug).
Ah it's nice that they but the effort in making these tests. And yes that explains that my instant death or one-hit-kill-bug as they named it in the video. He was using shitty engineer starter gun hit RDS and I know you can't kill with 2 bullets full auto with that on that distance, hence the video.
Well turns out you can with this bug. I'm just not convinced it's contained just for headshots, but anywhere on body, sure hope they would have tested that too.
But just yesterday I was in operation locked inside A flag, just shooting randomly on triangles outside, couldn't even see the enemies in the sunlight, just wanted suppression points as there where snipers around. And what do you know I got a kill with M416 with RDS. Felt so bad for the one who died. No way should any non sniper rifle have the accuracy for a headshot or the damage at that (I'd say about 300m) range for a kill, but had to be this bug.
Now if they can fix this it's half the battle won. Don't fix network sync issue yet, where enemy and you are on different spacetime (behind wall dying is the usual cry but when there is no obstacle it comes down to time and my talk of future enemies). At least I'll be able to start shooting back 1s later with 50% health instead of just being dead, so all good
@OnBoard Any way to reliably identify which one of those 2 you have installed?
My Computer / Uninstall or change a program and you see Microsoft .NET Framework 4 or 4.5 or 4.5.1 there (as only one of them is needed).
edit: oh and 4.5 comes with Win8 and 4.5.1 with Win8.1.
Well, I play BF4 on 8.1, would I still be able to replace .NET 4.5.1 with 4.5 if needed?
Test if you get CPU lag spikes to begin with. "perfoverlay.drawgraph 1"
Might work just fine with win8.1 and if needed would think 4.5 goes over 4.5.1 too.
Here's my test with 4.5, forgot to make video with 4.5.1 but it was constant spikes within that boxed are and half screen spiked would cause the dude and world to lag.
The next PC update is in the works, and we are tracking to fix a few items you have given us feedback on.
Specifically, we are looking at the Commander EMP blur effect that you have noticed, as well as the intermittent sound bug that happens most frequently on the Golmud Railway map.
While we don’t have a solid date for this patch just yet, we just wanted to let you know some of the things we’re looking at right now (besides increasing stability overall.)
Finally, Youtuber jackfrags sent us a great video where he demonstrates the so-called ”1 shot kill bug” [youtube.com], where it looks like weapons sometimes deal too much damage (although the real issue might be more complex.) We are reproducing this bug and working to fix it as soon as possible.
Stay tuned to the Battlefield 4 Control Room for more updates as they happen.
Yeah, that video definitely explains some of my weird kills and some of my weird deaths too. Good thing DICE just aknowledged the problem. Now we'll see if they manage to fix it or make it worse
4th crash in 15mins i'm out fuck this cocksucking piece of shit..
And every single time it happens when you click deploy and screen goes black. Fucking idiot cockmunchers.
the ammount of crashes you have is insane...
for me its very rare that my game crashes, my problem is that i get killed instantly (about 80% of the game - when i die... its instant).
Or enemys are porting around the corner there is no point in playing this game right now, and there is no patch comming out, because xbox one > everyone... just a stupid bunch of devs out there
4th crash in 15mins i'm out fuck this cocksucking piece of shit..
And every single time it happens when you click deploy and screen goes black. Fucking idiot cockmunchers.
the ammount of crashes you have is insane...
for me its very rare that my game crashes, my problem is that i get killed instantly (about 80% of the game - when i die... its instant).
Or enemys are porting around the corner there is no point in playing this game right now, and there is no patch comming out, because xbox one > everyone... just a stupid bunch of devs out there
Well, I'm stll having fun as long as I don't get one of those nasty looping sound freezes I don't care about KDR and that crap, as long as I can have a full match with my squad.
Don't get me wrong though, I still want f...ing DICE to fix all the problems, the loss of audio in a couple of maps, the instakills, etc.
Well, I'm stll having fun as long as I don't get one of those nasty looping sound freezes I don't care about KDR and that crap, as long as I can have a full match with my squad.
Don't get me wrong though, I still want f...ing DICE to fix all the problems, the loss of audio in a couple of maps, the instakills, etc.
Problem is i'd like to unlock stuff...
Which i can't because i keep crashing all the time = no progress saved.
Yeah, if I was in the same situation as you I would've certainly stopped playing till they fix it, I can't tolerate that kind of stuff. I'd be playing something else instead.
EDIT: Oh! BTW, the game is running now much more stable with the 64-bit exe. I would even go as far as saying, after my 2-3 hour session last night that it's now more stable than 32-bit for me.
Last edited by 4treyu on Fri, 22nd Nov 2013 19:44; edited 2 times in total
Yeah, if I was in the same situation as you I would've certainly stopped playing till they fix it, I can't tolerate that kind of stuff. I'd be playing something else instead.
I am playing something else instead.... now....
But i actually felt like playing bf4 since i haven't touched it in 2 weeks. Impossibru..... so yeah.
Signature/Avatar nuking: none (can be changed in your profile)
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
