CONSTANT Battleeye Query Timeout PLUM issues
Constantly getting booted from matches with PLUM issues and a Battleeye popup box saying "Query Timeout"
Yes I've followed all the 'useful' information in your support page for Plum. I've sent a request for assistance from Battleeye support as well.
Doing my own investigation I've found that during matches it's constantly trying to reach battleeye servers all the way over in Germany. The problem with that is that Germany most of the time is giving over 300ms of latency from here in Australia. Here's a prime culprit who doesn't like to respond: 57.129.90.115 (master1.battleye.com), located in Germany.
Please make it so Australian players aren't using battleeye services hosted across the other side of the planet. Most of these anticheat systems don't work well when the packet takes too long to get there.
I'm happy to hear and try other solutions, but i've tested my own network top to bottom and there isn't anything blocking connectivity to any battleeye services that I can identify, the packets are leaving my network, going across the planet and they aren't being returned (happy to provide a wireshark capture, tracert's, whatever you need). Either they're being blocked because german battleeye services aren't expecting to respond to packets across the other side of the world, or it just doesn't care about them because they came 'too late'.
Appreciate any help.
Ulgrim
*edited to correct a sentence
Comments
Hi there,
Thanks for reaching out,
PLUM with a BattleEye “Query Timeout” usually means BattleEye isn’t getting timely responses from your client, which long round‑trip times and packet loss can definitely worsen.
A few things to try while we continue working with our partners on this:
If you’re on Wi‑Fi, please test on a fully wired connection from PC to router/modem.
Fully power cycle your PC and networking gear (unplug modem/router ~30 seconds, then restart everything).
Temporarily disable VPNs, traffic‑shaping tools, or overlays/security software that might delay or filter traffic.
Go through the general connection steps in our Network Troubleshooting and Optimizing Connections (latency/packet loss) guides here:
https://help.bungie.net/hc/en-us/articles/360049496531-Network-Troubleshooting-Guide
https://help.bungie.net/hc/en-us/articles/360049024092-Optimizing-Connections-Improving-Latency-and-Packet-Loss
Thanks for the response.
It’s a wired connection with <1ms to the router.
No vpn.
Fresh vanilla windows install with no special security software to intercept or slow things.
All network hardware has been power cycled. It's all recently upgraded ubiquiti hardware.
I've checked your connectivity optimisation page but there's nothing there I can see that will make the installation of battleeye connect closer to this country. There are definite instances where we're seeing packets not come back, but that's isolated to the IP's far overseas used for battleeye.
Update:
Played a bunch today, no errors so far. I have change one single thing, I've change my DNS from Superloop (my local ISP) to Cloudflare (1.1.1.1).
It could be that, or it could be battleeye or bungie fixed something, i don't know. If anyone else reads this, try a different DNS provider.
If the trouble comes up again i'll update this.
Issue still happening, but maybe less? Anyway, not solved at this point.
I am getting the same issue on a wired, high-end gaming PC.
Only game where I get this battleeye error even though I have other games that uses the same service, like Battlefield 6 for example.
Marathon boots me out of a match and gives me query timeout error every 15 minutes, Battlefield 6 has never given me this error.
It is extremely annoying as I can't even finish a game.
It started happening since the last patch as of writing this.
Yea exactly, i play bf6 and it has no issues like this.
Any further updates or leads on this Support team? Being booted 3 times a match and going through the reconnect process each time isn't a great way to play this sort of game.
Hey, if you are on Steam follow my previous comment. It has fixed the issue and I played all weekend without any issues
I finally fixed the issue after days of trying...
I was able to play 2 hours uninterrupted.
I followed this reddit comment: https://www.reddit.com/r/destiny2/comments/pel18x/comment/hlgzpq7/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Solution on Steam: If you're having this problem try launching Steam in Big Picture mode -> settings -> controller settings -> uncheck every controller support option.
i had to go find struggi’s solution comment on another issue (struggi it’s not on this one :D), but i’ll give it a shot.
Apparently battleye is detecting some of the controller features and that’s triggering this problem.
Solution on Steam: If you're having this problem try launching Steam in Big Picture mode -> settings -> controller settings -> uncheck every controller support option.
I’ll report back on how this goes. If it works, thanks Struggi for bringing it to my attention.
Also if it works, BUNGIE, what the heck 😂
I clocked in about 10 hours of gameplay this weekend without any problems, so this was the solution for me. I hope it helpe you as well and I hope Bungie/BattleEye patches it quick.
Ok, i’ve looked at the thread you got the info from: https://www.reddit.com/r/destiny2/s/nKT5NJzO78
I uninstalled the Xbox Extended Feature Support Driver in steam.
No further issues the last few hours….
I’ll keep testing tomorrow, but.
That’s a very old thread for destiny that mentioned this, how is this still a thing?!?
Bungie
I have found that by closing my epic and riot clients which open on launch I am able to play for hours uninterrupted. I have fooled with this a lot and discovered my discord is not having any effect. However if my riot or epic launcher is open I get battleye timeouts. Hope this helps
Yeah, none of those open on my system, but it may help others for sure.
Played again last night with no issues, seems the xbox extended drivers being uninstalled solved it for me.
Please sign in to leave a comment.