UPDATE:
After the DLC 'official' release time - all issues magically disappeared.
Folks - that is a Bungie - Development-Testing-Process-Controls problem. I've been in this business for 20 years and this should never have happened.
By the numbers:
1. Xbox 360 (Home) - had NO issues. Worked perfectly throughout because I didn't purchase the Expansion Pack until this afternoon for the 360.
2. Xbox One (Home) - purchased Expansion pack. WASP error as described. NOTHING resolved.
3. Xbox One (Office) - did NOT download the Expansion pack. NO issues encountered.
4. PS3 - (Home) - purchased expansion pack. WASP error as described. NOTHING resolved.
All of these consoles are on the same network and router. The only consoles which experienced the issues were those with the Expansion Pack. So for Bungies primary resolution tips for power cycling the router, consoles and/or uninstall/reinstall,,,, well that's just BS. It is clear the problem was with the Expansion Pack alone.
I've loved Halo and Bungie for years, but this is sad and pathetic. Between all the story, content and game issues,,,,,and now obvious poor development practices and processes. Very disappointed with them thus far.
English
-
Edited by RedMachine72: 12/9/2014 10:45:31 PMCan't be the expansion pack alone, my son does not have the expansion nor the expansion pass and his keeps getting the error and I switched it to wired and did everything else they suggest and still no go. Mine, I have the pass and it downloaded the patches just fine. It still has to be something on their end if one console can get it just fine and the other cannot. My son has a 360 slim and I have the 360 Elite.
-
It may not be unique to the Expansion Pack, but it is certainly worse this time around for the updates surrounding the pack. And you're right, it is on their end.