And I have verified that the process doesn't crash. Unfortunately the BattlEye client isn't logging data to the App or System log. Error on game client is BattlEye client not responding, this is backed up by both the pcap file, and the ProcEx (again a tool from /sysinternals). I have pcap files that shot that the disconnect, a TCP (ACK, RST) packet is generated from the server side. NVMes, don't respond to SMART calls the same way SATA SSD or SAS do. I think this has something to do with the fact that my C drive is an NVMe. Because BattlEye is unresponsive the game client disconnects. Because the service stops talking the game calls the battle eye client unresponsive, in fact this is the every error message that is given. ProcMon (/sysinternals) indicates that the network traffic stops on the client side immediately after it tries, and fails to do a SMART call to the C:\ drive (OS install location). It doesn't sent anything, and it doesn't receive anything. The BEService.exe, which is the BattlEye exe attempts to establish a TCP connection, but then all network activity dies. This issue started when I upgraded in October. If you are using Windows 11, don't bother. I'll be posting this text everywhere I can in hopes of finally sparking a response. Still no acknowlagement from Bungie or BattlEye. The update as of 9th, November 2021 has not resolved the issue. This game is not playable due to the behavior of the BattlEye service on windows 11. I've kept my diagnostic data in case I do hear from someone, but as of yet, not a peep. I've made forum posts, and waited weeks, I've opened tickets, no response. Neither has responded to requests for assistance. The BEService for BattlEye just does not transmit UDP packets. I've done packet caps, ProcMon traces, looked at TCP and UDP activity in process explorer. You can't do a stack trace of the BEservice.exe. This makes the game currently unplayable on windows 11. The BattlEye client does not respond on windows 11.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |