{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Valecan:
2/3/2023 5:36:39 AM
5
Update on issue:
I have since also tried a fresh install of the game. Insured that all drivers are up to date and I am still having the issue of the inconsistent game launching. I have discovered a work around that suggest that the problem is with battleye in some way. The only way I can predictability successfully launch the game is if I delete the battleye folder and let the game detect it is missing and ask for a new install which I okay. At this point it will launch no problem. I have to do this every time. I have also tried uninstalling battleye and reinstalling using the method in the destiny 2 installed folders, but that has the same inconsistency problems as a normal launch. It is acting as though battleye is not closing properly when I close the game and effecting a later launch, but the task manager does not show any process related to battleye or destiny prior to my attempts.
English
-
Update 3: Never mind, the steps I took in update 2 had seemed to be working consistently yesterday, but today I am back to the same issue as described in the original post.
-
Tried to reply to this earlier as I have been having the same / similar issue. What I have been experimenting with is disabling my antivirus at launch - I've done three tests where I've first tried to launch in steam with the outcome described by OP and the launch fails after 10 sec or so - then disabled the AV for 5 min (setting in AV tool) and launched from Steam successfully. I had been through the full delete / redownload / reinstall, update everything, check logs path. My AV is not reporting any issue BTW - so not 100% confident this is the fix but so far has been the most successful mechanism. Worth a shot.
-
Edited by Valecan: 2/5/2023 6:37:30 PMUpdate 2: Your post got me thinking and I tested another solution that right now is seeming to work every time I load up. I had in the past added Battleye to the exception list for windows defender to, but it didn't help the problem. What I did different was I selected the parent folder for battleye and the steam Destiny 2 parent folder to be the exception which should include all the files and subfolders. That has seemed to work for me. I have no idea why out of the blue that this error started up on me in the past week but this is seeming to work for now. The file location where battleye installs that you would need to add to the exception list is C:\Program Files (x86)\Common Files and it is the entire BattlEye folder to add. For me the Destiny 2 install location was found at C:\Program Files (x86)\Steam\steamapps\common\Destiny 2 and I selected the parent folder of Destiny 2. If you are on windows 10, the process for adding the exception is found here https://support.microsoft.com/en-us/windows/add-an-exclusion-to-windows-security-811816c0-4dfd-af4a-47e4-c301afe13b26 I hope that helps you and any others have this strange issue.
-
Thank you Valecan. Disabling antivirus was a false victory for me in the end - the issue returned and remains intermittent. I'd love to know what is causing it. I will try your suggestion as well and see if it changes anything. Worth a shot and appreciate the update.
-
Download avast and don't turn on your PC's windows defender.
