I would doubt they missed it. As former QA, it is an unfortunate reality that bugs are assigned fix priority and addressed as such. Frequently, non-crash bugs will be set aside, left in and fixed with future patches. Frustrating as it is, the crunch to make release on time will necessitate this behavior. I do find it surprising, however, that there are many many QA issues in this game that have still not been addressed or acknowledged this late post-release. I find it further surprising that there is time/resources to make a dead cryparch, audio for him, time to test his implementation, but no time/resources for fixing issues like the original post points out. It would be lovely if Bungie would simply make a sticky post that listed known bugs simply to allay our concerns and give us hope (even if false) that they are calling some of these issues bugs and have a plan (hopefully) to address/fix them. My biggest surprise of all with this game is not the lack of content, not the black holes in the story, nor the alleged insane budget, but is the truly piss-poor job Bungie is doing with their communications dept. Their inability to communicate with us effectively is so incredibly sub-par. There is absolutely no way to get in-game issue support if you encounter an issue that halts your ability to progress. You're expected to make a post on the Help forum and then pray someone responds — and based on my observations it is highly unlikely they will.

[quote]It would be lovely if Bungie would simply make a sticky post that listed known bugs simply to allay our concerns and give us hope (even if false) that they are calling some of these issues bugs and have a plan (hopefully) to address/fix them.[/quote] I'd wager good money that the list of known bugs is frighteningly long... no way they'd put it in print ;)

We didn't miss it though, we discovered it, did we not?

[quote]We didn't miss it though, we discovered it, did we not?[/quote] ??? Well I can only speak for myself but I'm not part of their testing department. My point was that it should never have been released with THIS bug. I work for a software company and bugs are to be expected.... you simply can't predict or test for everything.... but this one is one that never should have been missed and it speaks volumes about the abysmal quality of their testing department. I had the same issue today with the Archive mission on Venus....