Jump to content

Destiny 2 Cabbage error, booted from games constantly


Recommended Posts

So just got done with playing a few hours of Destiny 2, just story missions and patrol.

 

I had the Destiny profile enabled, but just couldn't play the opening mission from the beta, I thought it was unusual that almost no enemies were appearing, then I got booted out with "cabbage error"(can't find any mention of this anywhere from Bungie) this happened 4 more times in 10 minutes.

 

I tried using the general gaming profile, it kept happening so I ended up completely disconnecting the Duma and just using the ISP hub on its own, no issues for 3 hours.

 

Obviously a new game brings new issues, just thought I'd share my experience, hopefully you guys can get to the bottom of what is causing this.

Link to comment
Share on other sites

i picked this up from reddit

 

Your description fits with the infamous MOOSE/SPINACH error from the Beta.

If that's the case, I have bad news for you, since there seems to be no solution in sight.

Check the Bungie forums. I'd send you a link, but Bungie.net seems to be under maintenance for me right now.

Sorry =(

Edit: Some further info/confirmation: is your router a Technicolor one? They seem to be the most affected. Also, a (poor, I know) solution is to configure a hotspot and use your mobile connection (or any other provider/network/router) to avoid the issue. Hope this helps.

Link to comment
Share on other sites

My ISP hub is a TP Link, so not Technicolor, it's in Bridge mode. I was able to play for half an hour just then using the Netduma with the general gaming profile but had to untick the box in Host Filtering near the top left under the console name that say "enabled".

 

I don't really think my problem has anything to do with my ISP hub.

Link to comment
Share on other sites

lets get this addressed!! many of us will be playing this game. need it to be playable with geo filter enabled because it is still a Peer2Peer game and can result in ruff connections if connecting to host with a ping that's more than 50ms..So in short the game will connect you to one of their servers for player movement and gun shooting so your shots will feel instantly fired, then the actual host of the game is another player in the lobby (p2p) . so its a hybrid system. post the id's to the servers you are connecting to (not the players hosts)

 

everyone report back with your experiences so we can get this fixed as soon as possible.

 

thanks

Link to comment
Share on other sites

Another cabbage, boot, this time again in the U.S.A looks like somewhere in Boston. ID: ac120cd7af4bd7dc

 

Again booted, this time looks like Connecticut. ID: 7d0d814caa1c363b

 

I'm going to expand my radius to include the whole world as it seems the issue is it will only connect me to a N.A host, btw this is PvE just the initial mission.

Link to comment
Share on other sites

  • Netduma Staff

Hi guys - every new game will unfortunately have errors unless we're lucky, since we need to test the Geo-filter ourselves and add the new servers to our cloud database. Until we get bigger as a company and maybe manage to score some early copies of the game to test before launch (which would be AWESOME!) we have to go through this annoying phase.

I'd ask everyone playing Destiny 2 to post ID's of servers that appear blocked on the map when (if) you get kicked from the game. That'd be a massive help and speed up the process. If it becomes really annoying feel free to disable the Geo-filter until we've released a cloud update or two.

 

Thanks for your patience guardians.

Link to comment
Share on other sites

  • Netduma Staff

Tried using the geo filter for the first time in a few days, got kicked with cabbage three times in 5 minutes, by two different U.S hosts in PvE.

 

ID: b50d1be6aa54363b

 

ID: df23ffcac07ea0a5

 

Thank you for providing these - it seems particularly bad in your case. There are lots of people using the Geo-filter with no issues, so I'm confident that once we get a few cloud updates this shouldn't happen.

Link to comment
Share on other sites

Well I'd imagine most of your customers reside in N. A, so they shouldn't have any problems.

 

It seems like Bungie has changed somewhat how they handle the host, not that I bought this product for PvE, but in the past doing a Nightfall with 2 fellow Australians would result in one of us being host or even an Australian server.

 

However in D2 the same situation results in us getting a N.A server, so a 250-275ms or so ping to host.

 

I did try it in PvP tonight with a 2000km filter but got kicked by an ID already listed, despite the entire lobby being in Australia the host was in the States.

 

I can live with it for now, and I did expect some issues with a new game, it's not easy for you guys to stay on top of.

 

Bungie certainly isn't making it easier insisting on using servers in a different hemisphere, I really don't understand the logic in that.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...