During Beyond Light cutscenes i've been getting major framedrops, and I usually end up getting error code rutabaga if I don't skip it. I haven't ever had this problem before, and I think it may have to do with cpu usage. Are there any know fixes?
-
1 ReplyI posted this in [url=https://www.bungie.net/en/Forums/Post/257517468?sort=0&page=0]another thread[/url] where everyone's replying to BNGHelp7 with their dxdiag system info... ---- It seems to be more a DirectX issue than a Win 7 issue. It's highly likely that the cutscenes are using something that requires DirectX 12 Ultimate. Which is not on Win7 or Win8.1 but was free with Win10 May 2020 updates. All of the pastebins that I looked at showed DirectX 11. Microsoft initially had no intention of adding DirectX 12 to Win 7 to push ppl to upgrade to Win 10. But after some time, they provided this link: https://devblogs.microsoft.com/directx/porting-directx-12-games-to-windows-7/ Unfortunately, the latest binaries from that page are from Nov 2019 (which might still miss changes in DirectX 12 Ultimate). Perhaps that's why some Win 10 users are also seeing the cutscene stutter--because they don't have the May 2020 update. It would be good to see their dxdiag if they would post it here. What surprises me is that Bungie's test or beta team didn't encounter this during their testing of Beyond Light. They don't have one machine or beta tester that has Win 7 or Win 8.1 or a pre Win10 May 2020 OS? At the very least, they should remove Win 7 and Win 8.1 from the Recommended System Requirements if they're not going to test on those platforms. I don't know how easy this will be to fix... ----------------- So for folks looking for a quick solution, I'm not sure it's going to be that easy.
-
Exact same problem. I have Windows 7 as well. GTX970 updated to the newest drivers and everything. I really hope they fix this cause I am not gonna play the game until i can do the Beyond Light story. Would be nice of them to acknowledge that its a known issue.
-
It is most likely now an error occurring with windows 7. I have tested making a profile for destiny 2 on my nvidia control panel, adaptive (half rate) vsync settings, game settings, no vsync, lower graphical settings, using a program for boosting game performance by pre-allocating memory for the game (worried that it was a cpu problem). I am running an older system but it has run destiny 2 until today at higher settings where it matters and never had frame rate issues. I am one of the few people who actually can't update to windows 10 so I was wondering if there would be a possible solution that lets me avoid not being able to play the game.
-
10 RepliesHello. Could you paste your DxDiag here? You can find this by doing the following: [quote]• Press (Windows Key + R) to bring up the Run dialog box, enter this command “dxdiag” without quotation marks. • Click on “Save all information”. • Copy the text and use a text dump website (i.e. [url=http://pastebin.com]PasteBin.com[/url]) to paste the information. • Create a link and post it here.[/quote]
-
21 RepliesCan confirm that my friend running windows 7 faces the same issue, however both myself and another friend are on Windows 10 where it works fine. This issue is seemingly limited to windows 7 users. As such, windows 7 is no longer supported by Microsoft and my suggestion is to upgrade to perform an in-place upgrade to Windows 10.
-
Edited by IceStorm: 11/11/2020 10:39:46 PMI'm on Windows 10 and am having stuttering in cutscenes as well. It's nowhere near as bad as others report in this thread, but I'm on a system that can easily handle 30FPS in-engine (9900k, 32GB RAM, 2TB NVMe SSD, RTX 2080 Ti at 1080p60) and I'm experiencing both stuttering in the video and audio hiccups, with the framerate dipping to 24 according to the in-game FPS counter and the Steam FPS counter. DxDiag details: https://pastebin.com/2356nQzk I have tried forcing both Fast and Adaptive (half-refresh) in the nVidia control panel for Destiny2.exe specifically. In-game, I have vertical sync disabled and a framerate cap of 120FPS set.
-
Similar issues here. I've played the final boss mission 4-5 times now, and the cutscene freezes and crashes my PC with error code broccoli.
-
Edited by (GA) GrandAdmiral: 11/11/2020 2:06:04 AMYeah, same here. No fixes as far as anyone knows. It does not, however, appear to be an issue with windows 7 only as we've been assuming.
-
Same issue here, Win 7 user
-
Yeah, it seem like the problem is limited to us Windows 7 users. I have the same problem. Bungie, please fix this and soon!
-
Same thing. I'm dissapointed
-
Having the same exact problem, tried updating drivers, resetting my PC, changing in-game settings. Nothing seems to work. It's only the pre-rendered cutscenes too.
-
Also posted here: https://www.bungie.net/en/Forums/Post/257510503?sort=0&page=0 With youtube video here: https://www.youtube.com/watch?v=LMTGUJmITqg I'm seeing it too with an i5-3470 w Nvidia GTX 1650. I am running Windows 7 x64. Are all the folks seeing this also running with Win 7?
-
Same. Win7 Cutscenes completely unwatchable or Rutabaga'd.
-
I have the same problem. Also using Windows 7 64bit version, gtx970. The rest of the game runs as smooth as it used to do before the new expansion.
-
1 ReplyI have this problem too :'(
-
Also happening to me. Running on Windows 7 x64.
-
Edited by Katana Grey: 11/11/2020 12:09:10 AMsame problem(((( Win7 x64, Nvidia 1660. drops from 200 to 1 or 3 fps, then error code - gitar.
-
Same story. Meaning can’t see the story. Cutscenes are unwatchable. Can we address this please, Bungie? Win7 GTX1080
-
Same problem here, game runs perfectly fine and smooth EXCEPT in cutscenes, to the point where it boots me for Rutabaga-reasons (low framerates), telling me to adjust my graphic card's settings. Win7 64bit / GTX1080 Would also love to know about a fix.
-
same here w7 and 2fps on cutscenes
-
Multiple forum posts, and no answer at all by bungie. I don't think they have any intention of fixing this... I think I won't be able to play destiny for some time... As I don't want to upgrade to win 10 right now, and the campaign is unplayable. Money wasted...
-
Got the same problem and end up with the same code. Running the game on Windows 7 x64 like everyone in this post.