{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Beans:
4/11/2020 8:19:44 AM
4
[b]4. ATTEMPTED SOLUTIONS[/b]
So far, I've tried (to no avail; none of these helped in any way):
1) Reinstalling Destiny 2
2) Reinstalling Steam
3) Deleting the appid.txt file
4) Deleting every file except for the Packages folder, then verifying game files
5) Launching Destiny 2 as an administrator, and disabling full-screen optimisations
6) Changing the language on steam
7) Whitelisting Destiny 2 from Windows Security
8) Utilising the crash_folder's information, delete package files that were associated to the crashes and then verify on steam
[i](do note that every crash seemed to have a different package file involved, and some of them didn't even involve package files)[/i]
9) Clearing out space on my computer (60-100 GB at a time in the form of other games)
10) in light of my VRAM mentioned above, I attempted to use the Registry Editor to increase my allocated VRAM to 1024 MB, to at least have enough allocated for Destiny 2. That went about as well as you'd expect.
11) Update drivers
12) Roll back drivers
13) Using Task Manager, set the process priority of destiny2.exe to above normal, high, or realtime
14) ensure that I have the MS C++ redistributables and .NET frameworks required
15) Since I'm using Bootcamp, reinstall the entirety of Bootcamp
English
-
[b]5. MISCELLANEOUS INFORMATION[/b] 1. This problem persisted from Battlenet to Steam, and started mid-season of the Drifter (Couldn't launch Gambit, Dreaming City and Tangled Shore Patrols and Strikes) , intensifying to its full effect in Season of Opulence (Everything in the game except for Tower and Crucible). 2. The game runs perfectly fine until I try to launch any open world activity that involves traversing through public areas. 3. [u][b]Any and all raids still work fine, as far as I'm aware.[b/][/u] 4. Certain locations and strikes are still playable, and have not ever triggered Problem type A (Still susceptible to problem type B). These locations and strikes are: - Titan - Mars - Mercury (any location that is not tied to season pass) - Io strikes - Earth Strikes - Warden of Nothing Strike, Tangled Shore 5. Certain locations immediately trigger either problem type A or B upon or within 3-5 minutes of launch. These locations are: - Tangled Shore - The Dreaming City - The Moon - Gambit Activities
-
Edited by Crisidelm: 4/11/2020 8:30:01 AMWhat can I say? You're lucky D2 even worked before and sometimes works now, given the specs of your laptop it shouldn't run... at all. The problem mainly being your video card, the integrated Intel 550 is below the minimum requirement to actually play D2. And the fact you're running on a Mac with Bootcamp doesn't help either.
-
Question: If I were to get an external GPU like the Razer Core X would that solve my problem?
-
Good question, whose answer I'd like to know as well. In theory, yes when paired with a fairly decent video card, but does it work correctly with Destiny 2? I don't know...
