Destiny 2

Destiny 2

Voir les stats:
Ce sujet a été verrouillé
*Solved for now* Error code: plum
I've been getting this error yesterday, and I haven't been able to find a solution that works for me on the internet. I'll be playing strike with random players or missions with my fireteam, and about 5 - 7 minutes into the game, I get a window saying "BattlEye. Query Timeout" and an error message in Destiny saying: "BattlEye error. Battleye has detected a problem. For more information, visit help.bungie.net and search for error code: plum". My internet connection is fine, and I have no files or other anti-cheats that could be interfering BattlEye like Riot Vanguard. I've reset my router, validated my game on Steam, and added BattlEye to my Firewall. No luck. I'm out of ideas what I could do to solve this issue.
Dernière modification de AdvanceLAMP; 28 févr. 2022 à 17h53
< >
Affichage des commentaires 1 à 10 sur 10
Man bro I had to do a ton of things for me to finally get through this error. Add the destiny launcher to the firewall as well. Disable the Xbox Game Bar overlay, Delete the battle eye folder in the Destiny folder and delete the second battle eye folder if one exist. Verify game files, and Steam will automatically reinstall BattleEye during the process. I repeat this is purely a battle eye issue. Here's a screenshot of the things I have added to my firewall. https://siasky.net/AAAo1Ofw_eA6CG2WfSdumUvvF2W20-S-NEl7goU53pom0g. Do not resort to Reinstalling Windows.
https://siasky.net/NAD0lkB4Qe5e7W8mJEwX5w5TbECsJxTAQCh9cn5uPoRb8g <- Add to firewall

https://siasky.net/OADfuijqEhmBdbcyyn7c0_KV_pXL2iuZqc_sMfueVzKdnQ <- Add battleye
Oh and one more thing, clear your shader cache for NVidia or AMD Radeon Center if you have AMD GPU.
So what worked for me was deleting the BattlEye folder in Destiny 2, then I verified the game so it would create a new folder. I restarted my PC and the game went back to normal. I do have BattlEye allowed on my firewall, I also included EAC. I'm not sure what changed but I hope this works for anyone else. I don't recommend uninstalling your game though, I don't think that fixed anything.
Steemp 28 févr. 2022 à 18h31 
AdvanceLAMP a écrit :
So what worked for me was deleting the BattlEye folder in Destiny 2, then I verified the game so it would create a new folder. I restarted my PC and the game went back to normal. I do have BattlEye allowed on my firewall, I also included EAC. I'm not sure what changed but I hope this works for anyone else. I don't recommend uninstalling your game though, I don't think that fixed anything.
hmm I'll try this.
AdvanceLAMP a écrit :
So what worked for me was deleting the BattlEye folder in Destiny 2, then I verified the game so it would create a new folder. I restarted my PC and the game went back to normal. I do have BattlEye allowed on my firewall, I also included EAC. I'm not sure what changed but I hope this works for anyone else. I don't recommend uninstalling your game though, I don't think that fixed anything.
I'm glad you can now play Destiny my guy.
They need to provide a definite solution to for this... Nothing has worked for me thus far...
This is dumb... I have tried multiple "fixes" nothing works. And I only wanted to play because of the new DLC haha thank the gods I've yet to purchase it.
For me, the PLUM error codes went away when I:

- unchecked the "Run as administrator" for destiny2.exe

- checked the "Run as administrator" for destiny2launcher.exe (NOT destiny2.exe).

- Turned off NVIDIA in-game overlay through the GeForce app settings

- In Windows, in the bottom right-hand corner, there's an app in the background running called "NVIDIA Settings". Right click the icon and hit "Exit"

- Close ReWASD or any other intermediary software between your keyboard and the game (anything that can potentially be used to create macros).

Hope this helps
IllI 1 févr. 2023 à 21h41 
Got battle eye plum... sheesh ... no cheats installed ever
Sman644 a écrit :
For me, the PLUM error codes went away when I:

- unchecked the "Run as administrator" for destiny2.exe

- checked the "Run as administrator" for destiny2launcher.exe (NOT destiny2.exe).

- Turned off NVIDIA in-game overlay through the GeForce app settings

- In Windows, in the bottom right-hand corner, there's an app in the background running called "NVIDIA Settings". Right click the icon and hit "Exit"

- Close ReWASD or any other intermediary software between your keyboard and the game (anything that can potentially be used to create macros).

Hope this helps

Would a Xbox Elite controller set off a macro flag due to the "Shift" feature of a custom button layout?
< >
Affichage des commentaires 1 à 10 sur 10
Par page : 1530 50

Posté le 28 févr. 2022 à 6h00
Messages : 10