Plenty of people in denial of this hit reg problem.
Yes i was not accurate but i was lying hits on enemy before he did same to me he was using standard ammo i was on high power i had body armour not sure about him.
He should have been dead before me.
He is either cheating or its hit reg ps my ping was 5ms
I think the hitbox is out of whack. That's why the TTK is slow. If you compare similar cases with different guns, the difference will be apparent. It means that the bullet is "penetrating" (not hitting).
also, there is something big time broken in BF hit registration; it varies between rounds. Sometimes the difference is significant. I play a lot close quarters -mode. There are few names, who play from day to day; they kill multiple enemies before even coming visible. They have been reported a lot. Without actions: Dice / EA does not care about gaming community.
i am not sure if you guys are involved in IT or any technical field. I am.
Yes, it is possible to create engine, that is taking latency into account. We do it industrial world all the time. Latency is not the only issue here. Latency can also vary a lot. I guess that is beeing exploited in BF case a lot.
They should detect this and not it happen. Connection needs to stable in order to play.
Ping and tickrate are not the same thing. the ping is how much delay you have to the server,
The tickrate is how the server sees you and the other players and dictates how the players interact, the lower the tickrate the higher the desync gets, and with that comes the bad hit registration and getting killed after turning corners.
Thats why competitive games runs at higher tickrates, and low tickrate games get these kind of problems, just look out at warzone, call of duty has 30hz tickrate servers, and that feels horrible.
ping is indeed very important, but there is so little you can do with 0 ping and 30hz or 45hz servers.
Imagine you're calling a friend to ask where the ball is in a game, but it takes 200ms for your question and their answer to go back and forth. Even if your friend updates the game state 128 times per second, you're still getting old information. The faster updates don’t help much if the communication itself is delayed — just like in an FPS game with high ping.
low tick servers, current hz is 45, way low than the acceptable level, dice just dont give a damm, we already pay for the game so it wouldnt be a surprise if they never upgrade it
If you stop and think a little, how is a netcode supposed to fix physical time differences and make it feel fair for all parties in a game. There is always someone who is unfairly affected when there are large latency differences, and here we are talking about latency differences from all over the world combined.
Anyone who was involved in the past when there was no code that smoothed out or should we say shifted what was happening on the screen, knows what it was like when someone jumped in with a high ping, then the latency was really noticeable and made it unplayable.
This is exactly what you are asking for, for the netcode to conjure up these physical time differences, and there is no code in the world that can fix this.
And with all these VPNs, it is not surprising that you get a constant latency of a few hundred milliseconds, which also makes the experience accordingly.
Low tic servers are never going to be very good. Hopefully the next Battlefield will learn and have high tic servers.
Hit registration is still on poor level. Its abit shame, since this game is abiut shooting. We can say that the most important feature is not working well. Some players who score triple or so say that they use vpn to get high ping. Those player move different. They are not getting hit before 5 or so bullets hit them. Game engine just sux big time.
😅 I prefer to think its a lottery
