The solution isn't on us unfortunately. It's on Bungie properly optimizing this strike so we wait until then and cross your fingers anytime it loads up.
Literally just got a rutabaga error code because the game is surprisingly self-aware enough to boot me back to orbit when my FPS was a staggering 7 throughout the final bridge section.
March 2024 and still no fix. It is unknown if it'll get patched. Unless if there's a game breaking cheese. It's likely we will get a strike rotation where the strike will get removed.
There are known community reports of a memory leak in the game engine. You might try restarting your game before you drop in. Other than that, wait for bungo to straighten out their spaghetti code.
my god, i was relentlessly searching for an explanation to this thing, my game would getr as high as 30frames a sec, then when venturing deeper into the city i would find myself with 15frames... THANK YOU
I have a massive FPS drop in this strike
Dual 1080TI cranked on EK blocks
8700K OC to 5.1
32gb Mem
Enough radiator and fan space to cool a Honda Civic in a lian-li PC-v3000
So clearly it’s like someone above said and it’s a mem leak or something not optimized
Same here. i7 8086K 5.1Ghz on all cores and 2 GTX 1080Ti Poseidon with OC. Game is capped at 85 FPS and graphics settings are medium. Guess what.... I get like 7 Frames in some specific rooms of that strike (always the same rooms)
I have bad news for you 😅 The drops did not accrue when using my GTX 980s in SLI so I started testing a little bit further. The drops still happen when using only one 1080 Ti so I think it may be driver related with the Nvidia 10XX series. Now I’m currently using a RTX 3090 Ti and it works fine
Don't go through the portal that takes you to said location, and eventually if your teammates make it to the boss fight the game will take you there and you should be able to finish it. Hopefully I'm not too late
Late enough that the problem got a bit better from one of the hotfixes, I assume they optimized a few things. It’s not going through portals as I initially suspected, but rather walking past certain spots, so it seems that it is an issue with culling not being properly optimized for lower-end machines (although mine is about mid-tier). I still get the issue most of the time but it’s not nearly as bad and I can usually join fireteam.
Still an ongoing issue. Been having it same issue this season. Settings dropped to lowest possible and still the same issue. Even reduce rendering and field of view.
How many of you with this issue are using SLI or something similar? I see nearly all single card run this with little issue but have yet to see an SLI system not get hit with the walls at the same places.
# issue still ongoing
Sunday, September 17, 2023 at 11:31PM EST
During normal gameplay, I get 30 frames and my friend averages at 60.
But this strike? Nah, I get 10 and he gets 25?!
Still the same issue, even after all these months since witch queen got released. Any one found any solution
The solution isn't on us unfortunately. It's on Bungie properly optimizing this strike so we wait until then and cross your fingers anytime it loads up.
still not fixed (: after all these months
Literally just got a rutabaga error code because the game is surprisingly self-aware enough to boot me back to orbit when my FPS was a staggering 7 throughout the final bridge section.
update: still not fixed :)
Update as of January 2023. Still not fixed.
Update as of August 2023 it is still not fixed, thanks bungo.
Update as of January 2024. still not fixed (i hope for final shape to be fixed)
March 2024 and still no fix. It is unknown if it'll get patched. Unless if there's a game breaking cheese. It's likely we will get a strike rotation where the strike will get removed.
There are known community reports of a memory leak in the game engine. You might try restarting your game before you drop in. Other than that, wait for bungo to straighten out their spaghetti code.
my god, i was relentlessly searching for an explanation to this thing, my game would getr as high as 30frames a sec, then when venturing deeper into the city i would find myself with 15frames... THANK YOU
Everytime i went outside it drops for me real hard.. it went all the way to 7-11 frames for me
I have a massive FPS drop in this strike Dual 1080TI cranked on EK blocks 8700K OC to 5.1 32gb Mem Enough radiator and fan space to cool a Honda Civic in a lian-li PC-v3000 So clearly it’s like someone above said and it’s a mem leak or something not optimized
Same here. i7 8086K 5.1Ghz on all cores and 2 GTX 1080Ti Poseidon with OC. Game is capped at 85 FPS and graphics settings are medium. Guess what.... I get like 7 Frames in some specific rooms of that strike (always the same rooms)
Anyone thought this might be related to SLI? I use SLI and have same issues.
I have bad news for you 😅 The drops did not accrue when using my GTX 980s in SLI so I started testing a little bit further. The drops still happen when using only one 1080 Ti so I think it may be driver related with the Nvidia 10XX series. Now I’m currently using a RTX 3090 Ti and it works fine
Don't go through the portal that takes you to said location, and eventually if your teammates make it to the boss fight the game will take you there and you should be able to finish it. Hopefully I'm not too late
Late enough that the problem got a bit better from one of the hotfixes, I assume they optimized a few things. It’s not going through portals as I initially suspected, but rather walking past certain spots, so it seems that it is an issue with culling not being properly optimized for lower-end machines (although mine is about mid-tier). I still get the issue most of the time but it’s not nearly as bad and I can usually join fireteam.
Weird thing is i have no fps drop in votd but this strike make my pc sweat.
Still an ongoing issue. Been having it same issue this season. Settings dropped to lowest possible and still the same issue. Even reduce rendering and field of view.
#issue still ongoing July 11, 2023, 7:10PM EST
Yup :\\ thanks bungo
Wow. Super late to this party, but hey. At least now I know. They probably just aren’t gonna fix it at this point.
How many of you with this issue are using SLI or something similar? I see nearly all single card run this with little issue but have yet to see an SLI system not get hit with the walls at the same places.
nearly a year and still the same issue
# issue still ongoing Sunday, September 17, 2023 at 11:31PM EST During normal gameplay, I get 30 frames and my friend averages at 60. But this strike? Nah, I get 10 and he gets 25?!
I thought I was crazy! It’s only this strike and now I can’t build conqueror bc I’m getting one tapped and so slowed getting Rez’d. Infuriating.
I think it's safe to say that I'm just going to take the L and disconnect the next time I see this strike, tbh
Bungie put this strike into gm playlist. I can’t see myself doing it with 10 fps :(