{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Edited by Caminon:
11/23/2020 7:23:36 PM
2
I am having terrible framerate problems in cutscenes. The game runs about the same as it ever did on my machine when in, say, Crucible or the Tower, but once a cutscene starts the framerate falls all the way to 2 FPS, rendering it unwatchable. Interestingly, however, these problems plague all cutscenes except the third one that plays on the first mission of Beyond Light (the one where you and Ghost are looking over the cliffside before the mission starts.) For some reason, that one, and only that one, runs fine.
Reddit suggested disabling nVidia reflex in the cvars file, which made no difference.
DxDiag:
[url]https://pastebin.com/4fFfX4eM[/url]
I am using:
i7 6700K
ASUS Z170 Premium
32GB G.Skill Tridentz @ 3200 MHz
GALAX GTX 1080 HOF running driver version 457.30 (though I was having the same problem on 441.87, one that I believe Reddit also suggested rolling back to.)
Destiny 2 is stored on my Seagate Firecuda (SSHD.)
Windows 7 64-bit <- This seems to be the common thread among most of us who have this problem, though there are also some people on Windows 10 who report having the problem.
English
-
yap win7 is definitely a problem... everyone who uses win7 had every pre-rendered cinematic stuttering as hell as well!
-
Edited by Paras: 11/24/2020 10:28:24 PMWin7 here as well and I think the problem is because of the only at Win10 running [b]DirectX12[/b]. I've talked to another guy who faced same problems in another game and the problem there was the switch from DirectX11 to DirectX12 so he thinks its the same issue here. And it makes sense! It's kind of another tyranny of Microsoft to punish people not whilled to use Win10 if you ask me ... because actually DirectX12 could work for Win7 but it does not. Also you're not able to install it manually. Insted you need to use an installer what checks your system for Win10. If not you can't install it even if your hardware actually supports it. I really don't get why Bungie or developer in general would use that at all. It's not much of an improvement to DirectX11 as much as I've found out... could be for an extreme performance-eating application but Destiny 2 actually isn't one. Also this does not work for any hardware - in fact there are some reports of critical problems using it not only for people not using Win10 but also for people with Win10 but unsupported Hardware... but also people with side-problems because of DirectX12. I wont use Win10 due to it's terrible usability, the many problems it had, has and will have (because of broken updates etc.), it's ugly pseudo-modern Design and other reasons and I wont even if Bungie refuses to fix the problem! In that case I would get rid of Destiny 2 before! I really hope they'll fix it and Im in fact quite curious if it really is because of DirectX12... of course we could be wrong and its caused by something else. Im not an expert.
