Hey,
As the topic states , I have been receiving This Error Code "marionberry" Since the first time i started to play the game Which was in BETA !!! Yesterday i purchased the full game from the xbox store, and to my surprise marionberry is till "ALIVE" and happening still, and not only me as the forum shows...
I followed the instructions Even Switched to Wired Connection to make sure it is the WiFi Connection giving trouble , ( tough even on Wireless connection i get A grade 0% Packet Loss) and any other demanding game as BF 3 and pro clubs FIFA 2014 on wireless. and never had a problem such as this one in Destiny.
And to my Surprise I'm still getting this Error.
Only way for me to Workaround this is to Sign out of my Xbox Live (Gold) Profile , and sign back right in , dont even need to restart the game/console (Xbox 360 btw ;) Till it happens again and it is pretty often , will kick me back to point u need to Press A ( Start) to continue and it will always fail signing in give me "marionberry" Error code, until i'll do the Above mentioned (sign out of my Xbox profile...and back in)
But it is getting annoying to a point i cant enjoy the game as intended [b], ( i understand its a Open Beta and those kind of Error could happen but the way it looks its not a problem on my end .[/b) Back ion BETA maybe , but now ? if its not going to be fixed in the next update, i will DEMAND a REFUND !!!
Just to be clear this is not a rant, its just how is it looking from my Side... Hopefully you can Help me sort it out.
if more information needed more than happy to give it in order to fix this ;)
P.s
Love the game :D
Sincerely,
GiborGadol
Edit: http://www.pingtest.net/result/106225486.png
-
I've been getting this "marionberry" code all morning. I wason and playing then kicked out and even off PSN. Rebooted everything and still getting this "code". Could this be their default code for "we have no idea what this is"? I really enjoy this game and would hate to have to return it or demand my money back. Hoping Bungie can get this patched up in the next update. :0(