Bug #18769

Battleye initialisation failed is not shown to the player himself - player gets booted from servers without getting told why.

Added by kju about 4 years ago. Updated almost 3 years ago.

Status:Assigned Start date:04/07/2011
Priority:Normal Due date:
Assignee:Dwarden % Done:

0%

Category:Multiplayer
Target version:NextGen
Affected ArmA II version:1.59.79384 First affected build:
Reproduced by another DH user:Yes First affected ArmA II version:
I am using some Mods:No Single / Multi Player?:
I am using: BIForumURL:
Reproducible for you:Yes NGUrl:
Related to content of DLC: WIKIurl:

Description

rundll.exe said:

Tonight (after patching the game to 1.59) I had some time and try to catch a public MP game (I never do). But right after loading the mission, the gamespy list comes up again, without any message. I thought: might be the server or mission. I tried maybe 10 other servers, with the same result. Booted to the gamespy list without any message. I had no clue what could be happening. Even the RPT didnt state anyting fatal. Then, when one server was setting up a new game I asked the players to watch for a message when the game starts. When re-joining they tell me it says "battleye initialisation failed".

Reference: http://forums.bistudio.com/showpost.php?p=1893047&postcount=177


Related issues

related to ARMA2 Community Issue Tracker - Feature #16257: Optional server.cfg entry: Show custom text message, if p... Assigned 12/27/2010
related to ARMA2 Community Issue Tracker - Feature #22759: Improve or hide "PlayerX uses modified file - MODLIST" in... Assigned 07/25/2011

History

Updated by kju about 4 years ago

  • Subject changed from Battleye initialisation failed not always shown - player gets booted from servers without getting told why. to Battleye initialisation failed is not shown to the player himself - player gets booted from servers without getting told why.

Updated by Dwarden almost 4 years ago

  • Status changed from Assigned to Expired

Updated by kju almost 4 years ago

This ticket is NOT about BE updating.
This ticket is about missing error to the player.

Updated by Fireball almost 4 years ago

  • Status changed from Expired to Assigned
  • Assignee deleted (Dwarden)

I see, BE still kicks without showing an error message. Maybe this should be brought to attention of $able directly too.

Updated by Dwarden almost 4 years ago

  • Assignee set to Dwarden
  • Target version set to NextGen

highly unlikely to become resolved in actual engine builds ...

Updated by Hanzu almost 3 years ago

  • Due date deleted (07/01/2011)
  • Category set to Multiplayer

Also available in: Atom PDF