Jump to content

$able

Member
  • Content Count

    706
  • Joined

  • Last visited

  • Medals

Everything posted by $able

  1. This is unrelated to the RCon change. BE's netcode changed, i.e. BE packets are now sent/received via the game's network protocol. This might cause problems for BE's ping calculation if the packet exchange is not fast enough (due to other traffic, etc.). As a result, unfortunately BE might no longer be able to provide such a feature in the future.
  2. Before people start complaining, I want to quickly explain why I decided to take this step. Without the requirement for administrator privileges prior to this update it was easily possible to hide cheats/hacks by simply running them under a different user account or as administrator. Therefore it is necessary to give BattlEye full access, otherwise it can be prevented from functioning correctly by anyone. So this is an important step that I postponed as long as I could. Keep in mind that the statements in the BE EULA are unaffected by this. Your privacy still is and will always be protected. On a side note, to permanently run the game as administrator on systems with UAC enabled, so that you don't have to right-click on the shortcut/executable each time, simply right-click on it and choose Properties. Then go to the Compatibility tab, check the "Run this program as an administrator" option and click OK to apply your changes. Steam users should do the same with their Steam shortcut/executable.
  3. You can now download a new beserver.so with this dependency removed here: http://www.battleye.com/downloads/arma3/beserver.so.
  4. The 0-bytes overwrite is caused by a bug in the Arma 3 server following "BattlEye initialization failed". The devs are aware of it. The problem here is missing dependencies. If you check your GLIBC version using "ldd --version" it will probably show 2.13. The new beserver.so needs at least 2.15. Please upgrade GLIBC on your server by following instructions such as these: http://stackoverflow.com/questions/10863613/how-to-upgrade-glibc-from-version-2-13-to-2-15-on-debian.
  5. Could you guys please make sure you use the latest version of TrackIR? If so please send the blocked file to support@battleye.com, thank you!
  6. Could you confirm that this is fixed now?
  7. No file updates. Could you confirm that the issue is fixed now?
  8. This issue should be fixed now, please confirm. I'm sorry for any inconvenience caused.
  9. Just ignore such messages if you don't notice any issues with the game.
  10. Yes, this boot option does the same and hence you can't use it anymore.
  11. Well, maybe your claims would be more believable if you didn't use the same nickname on a hacking forum. ;)
  12. Please try to disable test-signing mode again and reboot your system: https://msdn.microsoft.com/en-us/library/windows/hardware/ff553484%28v=vs.85%29.aspx.
  13. I'm sincerely sorry for that, but this is one of the measures taken to make the game more resistant against hacks, even if a handful of users are negatively affected by it. Using test-signing mode is never a good solution anyway (in terms of security as well). Maybe you can find a signed version of this particular driver or ask its creator to sign it?
  14. The problem with Windows 10 should be fixed now. Please restart Steam to force the update.
  15. It will be fixed if you do it correctly, unless you are using a 64-bit OS.
  16. For those using a 32-bit OS, please delete the BE Service folder ("C:\Program Files\Common Files\BattlEye") and then manually update your BEService.exe from here: http://www.battleye.com/download.html. This should resolve your issue. A fix for Windows 10 will follow later.
  17. Something seems to be seriously wrong with your system as the BE Launcher fails to run an .exe. In this case I can only suggest a complete reinstallation of Windows, I'm sorry.
  18. Sorry, the above only possibly helps if your game doesn't launch. Could you follow the steps listed in the Steam thread again and post afterwards? It seems nothing was logged for you yesterday.
  19. Could you check if you have a Windows update with the name "KB3004394" installed on your system (check in control panel)? If so please try to uninstall it. Others reported this as a solution before.
  20. Do you use a legitimate version of Windows?
  21. Please do the following so I can see what's wrong for you: http://steamcommunity.com/app/33930/discussions/0/617328415066127195/.
  22. $able

    yyL9RIeMArma " OA problem

    Please do the following so I can see what's wrong for you: http://steamcommunity.com/app/33930/discussions/0/617328415066127195/.
  23. Let's kick off March with two new features added in BE Server v1.131 and BE Client v1.151: 1. New script detection/logging that is fully customizable by server admins You can now easily set up your BE Server to scan clients for certain strings that are used in script attacks on your server, for example "createVehicle", "serverCommand", "setVehicleInit" or anything else that could potentially be exploited on your server. All you need to do to enable this is create a file called "scripts.txt" in your BE working directory (in the game's application data / profiles / BEpath folder, not the install folder - where bans.txt is placed as well) with per-line entries formatted as follows: [type] [string to search for] The following types exist: 1 - Log detections to "scripts.log" 2 - Log detections to server console 4 - Kick for detections ("Script Restriction #X") When logging detections, the BE Server logs an extract of 100 characters of the script being executed showing the detected string. You can combine types by adding them, so e.g. 3 causes positive detections to be logged both to scripts.log and server console, 5 causes detections to be logged to scripts.log and kicked for at the same time, 7 combines all methods, etc.. See the following random scripts.txt example (please do not use the list below unless You know what's command for/why): 1 createVehicle 1 setVehicleInit 3 serverCommand 4 godmode 3 Bo_Mk82 3 #shutdown 7 disableUserInput true Important update: http://forums.bistudio.com/showthread.php?131759-New-BattlEye-features-for-server-admins&p=2192402&viewfull=1#post2192402 2. Messaging players via RCon RCon admins can now directly send in-game messages to players using the new "say" command: say [player #] [message] If player # is -1, the message is sent to all players. Otherwise the message is sent privately to the specific player. Note that player # is the one shown when entering "players", not the one used by the game itself. Also, keep in mind that only in-game players can be messaged, not those that are still in the lobby. Example: say 11 hey mate, how are you doing today? I hope you like these new features. Feedback of any sort, as always, is welcome. :)
×