Jump to content
Sign in to follow this  
KField86

New battleeye issue..

Recommended Posts

Was just playing in my server when I noticed battleeye was starting to spam something along the lines...

"Battleye: Exception Detected" and it repeated that line multiple times. Now, before you call hacker, I fraps all my games I play for youtube purposes, but I didn't quite turn it on yet since I was just in the server near lopatino getting some water.

Then, "You were kicked. Battleeye: Client Not Responding" and EVERYONE in my server was kicked as well.

21:58:54 Player ********* kicked off by BattlEye: Client not responding

21:58:54 Player ******** disconnected.

21:58:58 Player ****** kicked off by BattlEye: Client not responding

21:58:58 Player ****** disconnected.

21:58:59 Player ** kicked off by BattlEye: Client not responding

21:58:59 Player ***** disconnected.

Just to show an example, here's an excerpt from my server log. Names removed, but that was 3 of the 14 other players who were removed. It's clearly not a cheating issue. Is battle-eye out of date again with 1.7.2.4 and the latest arma beta? (I'm running 95389 along with most others until we see another stable beta come out that fixes some of the graphical issues we're seeing. So far 1.7.2.4 has been a pretty stable patch so I'm happy with that at least.

Anyone have a solution for this though? It usually happens after 10 minutes of play-time. It's almost like BE is timing out.

Share this post


Link to post
Share on other sites

Yea just got it on my server. I updated the server to the newest beta ( 95417) and so far no problem but not for sure.

Share this post


Link to post
Share on other sites

All hackers. Battle Eye is a well oiled machine. No false positives, nothing gets past it. It is the alpha and omega of cheat prevention.

  • Like 1

Share this post


Link to post
Share on other sites

All hackers. Battle Eye is a well oiled machine. No false positives, nothing gets past it. It is the alpha and omega of cheat prevention.

Usually sarcasm doesn't get me laughing but ok, you win this time.

  • Like 2

Share this post


Link to post
Share on other sites

Yea just got it on my server. I updated the server to the newest beta ( 95417) and so far no problem but not for sure.

Well, I'm pretty much stuck with 95389 since Vilayer has to put up the new beta for me to install and add to my server. I mean, I love the guys at vilayer but still... I should be able to host whatever god damn beta I want on the fly the second it's released if I want to. It's my $48US a month for 40 slots, which is already more expensive than most other providers. I will say though my server has not crashed one time, and it's already very smooth. (90 FPS, 60 FPS with fraps running. I used to never get those numbers, but I know the patches did help things) and the only desync I ever see is red(hive) desync.

Share this post


Link to post
Share on other sites

???

Has nothing to do with the server provider or the host. Its battleeye that had done this.

Share this post


Link to post
Share on other sites

Has nothing to do with the server provider or the host. Its battleeye that had done this.

Yes, but there is a new arma beta out that supposedly people aren't experiencing this particular BE problem with.but I can't update my server to it yet to test it myself since vilayer isn't hosting the files on the ACP. That was my point. Not everyone on this forum is an idiot.

Share this post


Link to post
Share on other sites

It appears it was only for one moment, I have yet to see the error come up.

Several people, including myself, are assuming it was battleeye hiccup. As it happened to everyone at the same time and wasn't isolated to a single instance.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×