Hello, I was wondering is anyone else is experiencing an error code moose. I've notice it only happen in two places for me and seems to be a loading error. The first location it happens for me in is in the starting mission of the beta. Once you've fought your way through the battle and have to regroup with ikora to find the speaker. When I pass through the doors (which acts as a chunk loader loading in that part of the map) this is where it happens. When i pass through the doors and reach to where the shader kiosks are there are no enemies and no ikora. The whole map is open and after 30 seconds in this area it kicks me out with error code moose. Out of 8 times I have tried to do this mission, 7 of those have all ended with the situation above. The second place it happens and consistently happens is when doing the strike. Falling down the large pit to fight the boss of the strike. When i reach there and jump in, it kills me and creates my ghost at the top on the ledge with a 30 second timer. Once i respawn i get the joining allies count down. This bugs out as it tries to join me to the game but it isn't loaded for me. This happens about 5 times with me dying, spawning and join allies in that order. Once that has happened 5 times, it error codes me and kicks me out with Error code moose. I have had problems in the past with destiny 1 with error codes, getting disconnected from trials, strikes, crucible and raids with error code quail. I had fell out of love with the game. If this is how the full destiny 2 is going to play, I will be deeply regretful of pre-ordering and having my hopes crushed about the error codes being fixed. Thank you for reading this and any comments on solutions, previous experiences or any feedback will be helpful and I'll read them all. Thank you again. Ben Slade (BrownSlade)