The server browser of the x64 client doesn't show any servers regardless of filter settings. The "play" function doesn't put me into the queue even though the server is running and puts me into the empty server browser instead.
x86 server browser working fine (except for crashes explained in another post).
Description
Description
Details
Details
- Severity
- Major
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 7
- Category
- Menu UI
Additional Information
BattleEye Launcher window is open and says:
20:06:41: Starting BattlEye Service...
20:06:43: Launching game...
20:07:40: Note: File blocks can be ignored if they don't cause problems with the game.
20:07:40: [INFO] Blocked loading of file: "E:\Windows\System32\BfLLR.dll".
Event Timeline
Comment Actions
Hello Gekker and thank you for the report.
Does the BattlEye error appear only when launching the 64bit client or does it also appear when launching the 32bit client?
Regards,
Geez
Comment Actions
Only when I launch the 64bit client. I notice it when I close the game.
Aparrently the BfLLR.dll has something to do with my Bigfoot Networks Killer Network Manager. But I was unable to solve the problem so far.
Comment Actions
Hello Gekker.
We believe that it is possible that the BattlEye error is not related to the server browser not showing up servers correctly. Please contact BattlEye support about the error message - https://www.battleye.com/support/. Meanwhile we will look into the issue with the server browser not working correctly. Also, have you tried to disable the Bigfoot Networks Killer Network Manager to see if it has any effect on the behaviour of the issue?
Regards,
Geez
Comment Actions
I contacted battleeye support.
And I have tried disabling the Bigfoot Networks Killer Network Manager service and process which didn't seem to have any impact on the issue. Even The BattleEye message is still popping up.
The 64bit server browser is still not showing any servers.
Comment Actions
Hello,
updating my Bigfoot Networks Killer Network Manager to the newest version seem to have solved the issue with 0.61.136541.
Comment Actions
Hello Gekker.
Glad to hear that the issue has been resolved. In that case I am going to close the ticket, but feel free to submit another ticket in case you encounter any issues.
Regards,
Geez