Having trouble accessing the forums? Try logging out of the forums completely - clear cache, cookies, and temp files - then restart the browser and log in. Thanks!

Rev0verDrive Member


Last Active
Member, Battlefield 3, Battlefield 4, Battlefield, Battlefield 1, CTE
Hide my latest activity
Restrict other users to write in my profile feed


  • Ethimu
    Go to youtube, watch c9mQe5nsv2Q and after that tell me dmg mods are not possible in bf 1.
    June 15
    • Rev0verDrive
      Go read a book on client-> sync and modern hit registration in AAA titles. Then go read source docs, then talk to real devs.
    • Ethimu
      Gosh, just watch it and deny that there are dmg mods in this game. I don't care how it SHOULD work, when I see how it works. Maybe there are hit confirmations in bf, but certainly no dmg confirmations.
    • Rev0verDrive
      I'm not watching the garbage. I fully understand how the hit registration and damage calculations work in this game as with many many other games. I work directly with top tier game engines. I write code, level design, 3d model etc. Have been doing so for the past 20 years.

      Stop letting BS videos manipulate your thought process. Learn about the mechanics and processing.
  • Weish
    Hi, thanks for responding to my post. And do pardon me for my ignorance, although I do follow the update notes in general, I might miss out on some of the finer details.

    'The fix is servers in your region. Devs have stated so about a gazillion times. Asia to US or EU is "Officially" off the table. Next update lowers the 150ms threshold to 130ms in these 2 regions. All other regions will be bumped up to 200ms. Until that is, when more server locations are opened up in said regions. After which the 200ms will then potentially be lowered.'

    Would you mind if I just clarify some of what you said? Would really help me to understand how to work around the issues.

    From what I understand, they don't want Asian players on US/EU servers. What I don't get, however, is what you mean by the threshold being lowered/increased. Is this threshold that beyond which there is a significant disadvantage (need to lead shots much more, etc)?

    Once again, excuse my ignorance.

    May 26
    • Rev0verDrive
      It's not about X,Y,Z ethnicity on X,Y,Z servers. It's about how Latency affects the game play. If all players could have a long pings on all servers there wouldn't be a problem. DICE has to look at the server performance, precision and accuracy of simulation calculations. And provide the majority base in each region with the highest possible precision and performance. Latency and jitter corrupt that precision.

      The "Threshold" determines whether or not your shots purely run on strict server-side hit registration versus client detection -> server registration.

      The patch on April 29th set the global (all regions) threshold to 100ms. A few days later it was raised to 150ms. On May 30th the new patch will release. This patch sets all USA and Europe server to 130ms and all other regions (Oceania, Middle East, Asia etc) to 200ms. The classified "other" regions do not have enough server locations to allow the majority is these regions to have a low latency. Thus the threshold there is being increased.

      After the next patch if you have play on a US or EU server and your latency is 130ms or higher, you will have to lead your shots on moving targets. This is regardless of your home region. US player on US server will abide by the same threshold as a Asian/Oceania player on a US server.

      Further down the road when DICE opens up more server locations in these "other" regions, the threshold in these regions will be reviewed again. Potentially lowering the 200ms to 150m or 130ms.
  • xxShiftyxxx
    I just noticed you said ping cap at 130 for EU and US so what are you saying that us in Australia have to put up with these OOR players now filling our servers with there 200ms ****.
    May 26
    • Rev0verDrive
      That's the next patch bro.
      US/EU server-side barrier 130ms
      All other regions server-side barrier 200ms

      Dice is suppose to be setting up more server locations. There's talk and testing posts all over reddit.
  • Alucardrock5000
    Hi, Good evening, I would like to know what action DICE is trying to address the question of the xiters that only add up on the BF4 servers? Without mentioning that now the game's NETCODE seems to be failing! Because at various times you shoot the enemy first and he can still kill you, as this is possible, in other cases we shoot and our shot does not count! Incredible as we paid for a complete game and we have to face these **** problems, as far as hackers my honest view is that DICE is not giving due attention to a game that is still more played than BF1. DICE wakes up the BF4 servers are still active do not abandon them like you are doing!
    May 24
    • Rev0verDrive
      Netcode isn't "failing" or "Broken". It's being fixed to where it legitimately should have been for many years. To understand the change you need to understand exactly what ping/latency and jitter are and then how lag comp hit registration is arbitrated.

      Please read the following

      Ping, Latency, Jitter

      Basic Client/Server Synchronisation walk through

      Lag compensated hit reg - hitscan vs projectile
    • Rev0verDrive
      Once you've read the following I can talk to you about the xiter (cheater) issues.
  • HillbillyJohn
    Thank you for explaining things, I really appreciate it.
    May 23
    • Rev0verDrive
      Not a problem. Have questions just ask and summon me.
  • misisipiRivrRat
    Hey man. My apologies for the quote boxes in the hit detection thread. But I was hoping you'd answer me so thank you. I've seen you answer people here and in reddit and you sound knowledgeable while I know next to nothing. Plus you don't make people feel like complete idiots when you answer them like some do in the thread. Anyway thanks.
    April 30

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!