Jump to content

$able

BattlEye Staff
  • Content Count

    227
  • Joined

  • Last visited

Everything posted by $able

  1. This is no excuse or anything, but I noticed a massive increase in complaints right after the last major updates (mid-March) while the amount of hack users didn't really increase (rather the opposite actually, January was much worse compared to now). My theory is that there is some new desync issue that could possibly be the cause for many hack-like situations (teleporting, instant kills, etc.). Again, this is no excuse, I'm just trying to find an explanation for this change in perception since the last stable updates were released. It's a fact that these days BE is more effective than ever (anyone with access to private hacks can verify that), so this whole situation is quite weird.
  2. Since I read complaints about cheating on experimental servers all the time: I advise everyone to only play on BE-enabled experimental servers. It's a fact that most private hacks aren't detected by VAC very often, so if you want best protection you should make sure you only play on BE-enabled servers.
  3. $able

    Battleye failed to update

    Normally that's not necessary as the game automatically updates the BEClient.dll in that folder if it has an older version number.
  4. I understand, I'm quite annoyed by this issue as well. ;) At least we know the cause (for many players) now.
  5. Actually it wasn't BE's fault if the file was in use by Steam. Thanks a lot for posting those details though, I really wasn't aware of this. It would be great if others having this problem could check if their BEClient.dll (in the AppData BE folder mentioned in the first post) is in use by Steam.exe as well. If that's the case we will reach out to Valve to get this fixed ASAP.
  6. I'll just reiterate this here as well: If you come across any "undetected" hacks please send any information about them (links, etc.) to me.
  7. $able

    Battleye Client Not Responding.

    What sort of router are you using?
  8. Please send any links to me (via PM). Most likely they are already known though.
  9. $able

    Game crashing

    Yes, I know. As I said above, this was quickly fixed. Do you still have problems?
  10. $able

    Game crashing

    That was happening with BE Client v1.213 which was quickly reverted. At the moment there shouldn't be any BE-related crashes. If you still experience one please let me know.
  11. $able

    Game crashing

    I'm not sure why you think so, he didn't mention BE anywhere? I am not aware of this currently "very common" problem either. Could you please send me your crash report/log? I'm not sure why you expect issues to be magically fixed if no one (including yourself) reports them? Thanks in advance!
  12. Do you get these lags constantly or only every few seconds or so?
  13. Please let me know if you still have problems with the new update (v1.213) that was just released.
  14. What type of kick are you talking about?
  15. Please check if you have received a PM from me - I need some testers.
  16. Thanks, could you rejoin a server and test again now?
  17. I know that there is an issue, still I would like to know your client-side system specifications. Also, could you check if it's better now?
  18. Could you post your system specifications (hardware, etc.)?
  19. $able

    arma 2 has stopped responding

    Thanks, this should be fixed now. Could you please confirm?
  20. $able

    arma 2 has stopped responding

    Could you please send me the last 20 lines of your .RPT file right after the crash?
  21. FYI, I identified a BE-related issue that might have caused crashes for certain people. An attempted fix is now live. Please confirm if the crashing has stopped for you. Thanks!
  22. I know. ;) If this thread is hijacked I'm sure the offending posts can be removed?
  23. I'm not sure what you mean, I regularly post here?
  24. May I ask what version is shown for you in the "BattlEye Client: Initialized (v1.xxx)" message when joining a server?
  25. $able

    CRASHING AFTER BE UPDATE WTF

    There indeed was a temporary issue right after the update, but that was quickly resolved.
×