{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/23/2024 5:59:11 AM
10
Error codes CABBAGE and CURRANT - Empty activity instances
Hi,
Recently, I think since update 8.0.5, I have been sent to orbit much more frequently than usual, with error codes CURRANT or CABBAGE, most often.
This generally happens after loading into an activity with a friend, where I would get no enemies and no obstacles (for instance liminality, no ads and no dark-shootable-thingies blocking my way, I can walk right through) while my friend would see the enemies but wouldn't be able to shoot the blockage or progress through. I then get kicked to orbit with either code, only a few minutes in.
I also sometimes get sent back to orbit while trying to load into an activity or the tower, instead of landing I get error-coded.
Any help would be greatly appreciated,
Thanks
-
Similar kind of issues. Swedish player, and me and the buddies have constant issues. Can connect with each other IN ORBIT, but as soon as we try to play anything usually one or two of us are getting kicked. Most of the time the loading screen goes ahead but at the last minute, just before the activity starts we get a black screen and after a while one of us gets booted. It seems the we that have Telia as ISP has the most problems. I have have cleared cache and also tried using google DNS servers but same issue. Telia had big issues with their DNS servers earlier this week, and it seems to have started then. Coincidentally around tuesday and Destiny update? All other services work fine, streaming, downloading and so on. PSN party chat works all the time, only the destiny activities (or even going to the tower together) are problematic
-
I stand by this, ever since the update on Tuesday, can't load into any instance, error code: currant every time. I have gone through EVERY SINGLE troubleshooting method it's some bs. The issue is on bungie's side, please fix it bungie.
-
Same problem. I am not receiving any currant errors, but a lot of cabbage errors. Today was something new. After connecting to the raid I received rabbit error. I have never seen this one before. Ultimately I dont remember any of these errors, its started after tuesday patch
-
Same here, started happening after the patch.
-
The same problem.
-
Edited by Dooodley: 8/23/2024 5:56:07 PMI've tried two different routers now, I've reset them, checked everything AND I've tried connecting directly to the fiber socket in the wall (no modem or router at all). Everything els is working under all those circumstances, except for Destiny 2 - where I'm still getting currant, cabbage and random blackscreens. I've even tried loading in to instances that arent shared (maybe they are anyway, just that we dont see it) such as raids, GM's and higher level lost sectors and it's happening there too. Also, this was mentioned in a similar thread but it seems to affect a lot of people in the nordic countries (telia users and I would assume everyone on a smaller ISP that is utilizing telias infrastructure). So someone screwed up, either Bungie, through some regional settings, or the ISP. I just find it weird that the ISP should happen to change something at the exact same time as when the latest Destiny 2 patch was released - which is when the problems started.
-
Similar issues here. Constantly ending up with a black screen after zoning in to things and shortly after that I'll recieve a message regarding network issues. The only thing i can do during blackscreen is to hit ESC and go to change character - that'll take me back to orbit. Additionally I have cabbage and currant error codes spread out throughout the day. Never had any issues like that prior to Tuesday's patch. Nor have I changed anything on my end or have issues with my connection anywhere els.
-
Same thing happening here. I am using an Ethernet cable, my ISP did not change anything, it IS Bungie's fault 100%. I am from Lithuania if that helps. Every other game works like a charm, fix your stuff Bungie
-
6 RepliesHi! Thanks for reaching out. Our team is actively monitoring Currant errors for potential trends. Cabbage errors typically occur when your router settings are blocking communications to or from Destiny servers. You'll need to make sure your device is directly connected to your router through WiFi or wired. Could you please give the steps on [url=https://help.bungie.net/hc/en-us/articles/360048721992-Error-Code-CABBAGE]this page[/url] a try and let me know if that resolves it?
-
Do you have final shape?
