destiny marionberry

[mike]

ok i have no idea what an actual marionberry is if indeed it exists ?.

but looking at the geo-filter from here in the uk if the geo is set as i normally have it (756km) when i try to log on theres always a padlock symbol over what im guessing is a server farm/hub in oklahoma , now unless i expand the geo to cover this i cant log on , but when i do and i log on i can then set the geo back to 756km and theres little or no problems.

 

just wondering if other uk players have noticed the padlock in the same area ?.

 

and yes i know its another bungle cock up they did an update and some ppl reported the marionberry error and then went back to a previous build and now everyone is getting errors.

 

just curious to see if other ppl have noticed the same as me ?.

[XIJMAW]

I have exact same problem, I have bleeding edge cloud ticked and all the rest.

[mike]

just set your geo to 756km note where the padlock shows up in the usa (hopefully its the same one that i see) then expand the geo to cover that padlock , log in select your class and then set your geo back to what ever you have your geo set at , mine is 756km atm.

 

like i say in my post above im uk based and bunghole is usa based.

[Netduma Fraser]

Please see this thread regarding the issue: http://forum.netduma.com/topic/17880-cant-connect-to-games-nat-errors-etc-workaround-fixes/

 

You will want the test cloud starting with 21, you may then have to use the workaround as well but you shouldn't get the marionberry error.