Hi Lord Yesua,
We've made important updates to our help page here: http://www.bungie.net/en/Help/Article/11931
Not seeing others is one of the symptoms described, so give the article a read and you may be able to reconfigure your home network using suggestions there.
English
-
Dear Bungie peeps, The other day it was just my matchmaking that was broken (http://www.bungie.net/en/Forum/Post/74840423/0/0/1). Today, I can’t even sign into the game. Upon pressing A to launch the game, I receive the MARIONBERRY error. I have checked my NAT settings and they are optimal for on-line connectivity. I have been able to play Destiny on-line without any problems before the past few days. I am very disappointed to be receiving these errors all of a sudden. Something should be done to resolve the serious connectivity errors as soon as possible. I've paid good money for a game I can’t play. Other past problems include Zebra, Boar, Mongoose and Viper errors (if that helps at all). I still get the BOAR error upon signing in to the game. Destiny is epic and addictive. Not being able to play is a great shame. Lord Yesua (Xbox One)
-
The thing is, I haven't had any problems with matchmaking on Destiny before now with my current settings. My brother plays Destiny on the same console in the same house and has [i]no problems[/i] with matchmaking. The Strike games launch with only me playing. The crucible maps don't launch, instead I get a blue box on screen saying 'Mongoose error'. It is a shame, because I really love the game. Anyway, [i]thanks[/i] for getting back to me. I'll message you after I've looked into my NAT settings if there are still problems.