{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/25/2022 7:37:01 PM
7
The Ritual - Portal Bugged
Running through my Warlock after just coming back to Destiny 2. The warlock is my third play through but The Ritual campaign mission has worked fine every other time.
I get to the second round of breaking the webs. The first portal to the right is lit up green. I can not enter it. The other two work fine except for this one. I have restarted my console, left the mission and tried to just jump off the edge and restart that portion. None has worked.
Can I please get some help with this one?
-
2 отв.Try sliding into the portal! That worked for me.
-
I just ran into this bug 😒
-
1 ответsame issue here. first playthrough. same portal, same phase. also tried all the stuff. PC.
-
Same issue is happening with me, mine was warlock (first playthrough) it’s the last webs and it’s always the portal to the right and the other two are working. I hope this bug gets fixed soon
-
Same issue, same portal as described above. 100% reproducible.
-
2 отв.I'm having the same issue - 3rd character running through campaign (hunter) and not able to finish due to the last portal issue you mentioned above. Glad it's not just me. Frustrated that it's happening though! I just want to be done with this campaign already. I wish Bungie was more supportive of Alts so you wouldn't have to run through the same content on 3 different characters... give us a skip option please! Also, please hurry and fix this so I can start the pinnacle grind (another system that needs a lot of reworks!)
-
yep, same is happening to me. im playing as a hunter (first playthrough) and a few days ago i got to the ritual mission, and this has been happening to me as well for the whole time, ive tried leaving the mission and going back in, exiting and re-entering destiny 2, dying while there and some other stuff and nothing has worked so hopefully this is/gets fixed
