BattlEye problems

[$able]

Regarding "Client not responding": It is known to happen when a player is in "Receiving..." state (black screen) for a long time after joining the game - depending on his connection. This is related to the BE integration code and will be fixed in the next version.
You shouldn't be kicked for that while playing though - except if a client loses connection due to a game crash of course.

Please also try the new BE Server version (you get it via auto-update). Some improvements have been made regarding this and other matters.

[brit~XR]

Yep i did say that in my 2nd post above. i used all 3 settings. battleye=0; then battleye=1; then removed battleye= from server.cfg and did the same.

I just tested again with battleye=0; to make sure. Server ram was 370mb and when server started it went to 904mb and in processes it shows 20,120k memory used.

[$able]

Is that immediately after the .exe started? As the memory usage in task manager goes up to more than 100 MB when a mission is loaded.

[brit~XR]

Yeah thats immediately after the exe is run

[$able]

Ok, I get the same for the "Commit Charge" value - "Physical Memory" remains normal though.

I get the feeling that this might be related to ArmA's new memory management.

[Cross]

Regarding "Client not responding": It is known to happen when a player is in "Receiving..." state (black screen) for a long time after joining the game - depending on his connection. This is related to the BE integration code and will be fixed in the next version.
You shouldn't be kicked for that while playing though - except if a client loses connection due to a game crash of course.

Please also try the new BE Server version (you get it via auto-update). Some improvements have been made regarding this and other matters.

I received "Client not responding" error couple of times just after i started playing (ie after lobby and receiving). It kicked me off the game. I reconnected and it was OK.

[NightShade]

Today i had reports it kicked off half the players on my server but wasnt there to comfirm that

(Enverex here)

What happened was that for about 20 minutes it seemed fine, but then it started seeming to lag heavily, as in very badly. People then started being kicked off by battleeye almost randomly (you'd get the "Losing Connection" message from them first) then they'd rejoin a little later after having been kicked off by BattleEye.

About 20 minutes after that started I noticed no-one was joining the server anymore and then slowly one by one BattleEye was kicking off everyone from the server, the amount of players dropping from 15 slowly down to nothing. If you try and rejoin the server while it is in this stage you will just end up the the ArmA logo and freeze in the "Connecting" stage, you'll never reach the lobby.

I don't understand what may be causing this though, 1.11 and BattleEye were fine the other day...

[brit~XR]

Enverex = niteshade from devgru? lol.

Anyway back to topic. The day i put 1.11 on server with battleye i noticed problems with high desync when players would join and yellow boxes which wasnt a problem on 108. And because its a beta patch then we can exspect some problems.

[$able]

@crawler75: Yes, I posted this as a temporary workaround on the first page.

@NightShade & brit~XR, I am sorry, but I doubt any of this lagging is actually related to BattlEye. Maybe the server was just generally lagging at that time? Regarding "Client not responding", as I said above, please try the new BE Server version - except for immediate kicks after joining. And when a player loses connection it is most likely due to a game crash, so obviously he will be kicked.

[MessiahUA]

I don't know if it is actually a problem, also there is no thread for 1.11 beta with battleye, so I decided to write here just a note about:

Quote[/b] ]BattlEye Server: Update successfully completed. Restarting...
BattlEye Server: Initialized

I'm using dedicated windows server (1.11). I don't know why, but sometimes this message above repeats a lot of times for no reason. Interval is around 1.5 minute.