{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
Modifié par Lord Magris :
11/17/2019 5:04:07 PM
3
Did this start happening for you just recently? Have you swapped out your router/modem or altered your settings in any way lately? And does this error happen every single time you load into the Tower or does it happen randomly?
There have been many reports about this and Cabbage errors happening with players since Cross-Save was introduced and it is a known issue.
English
-
It was every time. I tried for over an hour including restarts and changing characters. Then I just shut my Xbox down and waited a day. Now it works again.
-
I'm not too sure if this could've been your situation, but usually if a player gets the Lettuce error code in the middle of a session that has other players in it, if you try to rejoin or the game just puts you into the same session, you end up getting Lettuce again. It might be possible that the game kept trying to put you into the same lobby over and over, even for over an hour. That's usually how that error goes, but there have been some different cases before.
-
I'm also getting a lot of cabbage and lettuce errors. Not sure why. I use LFG for raids a lot and it is happening on a regular basis. We load into a raid and I get cabbage error and can't rejoin or I will get loaded into an empty instance and then get lettuce error not long after. This is starting to happen quite frequently. Once the instance is glitched it seems that the only remedy is to return the whole fireteam to orbit and hope you don't encounter the errors again. Problem is that in raids nobody wants to return to orbit to regroup because of raid.report and their stupid red dots.
