{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
9/1/2021 6:40:32 PM
20
-
Russian guy from steam fixed by dropping missing dll library in the folder with destiny2.exe Its hilrious You guys need to hire some PC devs
-
Edited by Terr: 9/2/2021 5:38:25 PM[b]NEVER ACCEPT DLLS FROM AN UNTRUSTED SOURCE[/b] It's exactly the same risk as if "some Russian guy on Steam" told you to download and run [i]totally_not_a_virus.exe[/i]. If you're going to experiment, grab a copy from Microsoft or a known-legit installation of another version of Windows.
-
Edited by Guardian: 9/1/2021 10:23:27 PMThat doesn't works. Dll will cause another errors
-
No, that way works (I tried it, but deleted it for fear of being banned)
-
Do indeed explain how he fixed it and what OS was he running.
-
Edited by Gkarbouzi: 9/1/2021 8:14:09 PMExplain how. We tried to put the missing dll onto the destiny 2 file and it didnt even work. We get another error that says 0xc000007b
-
error 0xc000007b is solvable, google it - common_dlls_for_games_file
-
Thank you but i already fixed it. I upgraded to windows 10
-
Worked for few people in the comments on that steam discussion Didnt worked for me tho, maybe he had installed like entire dll libary since the age of times i deleted all of that and reinstalled cause i thought i need an update He was running Win 7 x64
-
Was it an extra dll or a different that made it work? Could he suppose to give that information to see if its gonna work for the rest of us here?
-
They still haven't fixed the FPS drop for the Cinematics from at least 8 months ago. Think their fix will be to drop Windows 7 support. My other computer running Windows 10(laptop), has no issues running it currently. -V
-
Edited by Terr: 9/8/2021 5:21:10 PM[quote]I think their fix will be to drop Windows 7 support.[/quote] They already got enough bad press from "vaulting" the original D2 campaign, Curse of Osiris, Warmind, 5 raids, 7 strikes, 4 planets, and dozens of adventures and sidequests... If Bungie [u]also[/u] selectively blocked 5-10% of players from playing current content with negative-1 months of warning... that would be a lot more bad press and possibly some refund/legal problems. I expect if they decided to drop Win7 support today, they would change the specs on Witch Queen, claim: "5 months notice that your game will stop working is enough", and offer some refunds to preorders.
-
We don't know, we're still attempting to issue a fix in our builds.
-
Edited by 9Knoxus6: 9/1/2021 8:04:03 PMJust move the Battleye for us win 7 users until you can get back to your labs to your compatibility testing stuff. I am not a hacker. Check my crucible statistics, all my matches I have 1 or 2 kills.
-
They have literally said multiple times that it's not Battleye that's causing this
-
It's nice of you to respond to a user. Have you tried reverting back to a previous version of destiny2.exe? I'd very much like to know if you've actually run your attempts on actual Windows 7 machines, and not just using the 'methodology' within that blog that was posted by you.
-
Good luck trying
-
Have you tested even the update properly on Windows 7? Or you haven't?
