Battleye initialisation failed is not shown to the player himself - player gets booted from servers without getting told why.
|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:|
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".
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 kju over 3 years ago
This ticket is NOT about BE updating.
This ticket is about missing error to the player.
Updated by Fireball over 3 years ago
- Status changed from Expired to Assigned
- Assignee deleted (
I see, BE still kicks without showing an error message. Maybe this should be brought to attention of $able directly too.
Updated by Dwarden over 3 years ago
- Assignee set to Dwarden
- Target version set to NextGen
highly unlikely to become resolved in actual engine builds ...