Bungie Answered
Playing certain games at any point in time before playing Marathon will cause error code Plum until a reboot takes place
So as per the title and as silly as it sounds, I have now recreated this issue specifically in Marathon multiple times and it seems if at any point past a reboot of the PC on WIndows 11, if you play the game Pacific Drive and then exit out after some time, the next time you try to play Marathon you will be plagued with Error code Plum followed by BattleEye crashing and saying "Query Time Out." A full reboot of the PC will fix this issue until you load up Pacific Drive and quit it again.
0
Comments
Hi there,
Thanks for reaching out.
If you haven't already, please try the troubleshooting steps in our Error Code: MARMOT guide as this error is also related to BattlEye services. If the error persists, BattlEye may be detecting a suspicious version.dll file in your steam folder which could be causing issues with the game. Please try deleting it and try again if so.
For more information about the PLUM error code: https://help.marathonthegame.com/hc/en-us/articles/39001779823252-Error-Code-PLUM
its none of those things actually. i previously checked for a suspicious version.dll and theres nothing there. Verifying will also achieve nothing as the issue does not present itself until you play the game Pacific Drive for a couple hours before you hop on Marathon. I have verified, reinstalled, clean install etc. Even triple checked if it was the NVIDIA App but its none of these things. The only thing reliably causing this error is to launch Pacific Drive on steam and play for a while. You can come back 12 hours or 2 days later and Marathon will throw a Plum error after roughly 10 minutes even if youre in the main menu and BattleEye will pop up and say Query Timed Out. Rebooting the PC fixes this until you once again decide to play Pacific Drive.
i am making this post in the efforts of someone at Bungie can see that there might be other games that are conflicting with both Marathon and BattleEye. I have also tested this seems to be exclusively a Marathon issue, it did not present itself when I played Gray Zone or Helldivers
Please sign in to leave a comment.