Darth_Trethon wrote...
Yeah but WHEN did they pick up on the issue? If they caught it right before submision for certification then it's a couple of days at best whereas if they found out about the issue yesterday....likely due to a failed certification then it will be weeks. If they delayed submission for certification then they may have not said anything earlier because they thought it may have been possible for it to still come out a bit earlier and make the 5th. And NO fixing a bug doesn't have to mean an entirely new build....all the work they did is still in place.
XBL DID update the RtO achievement yesterday and an italian site lists RtO as expected tomorrow(the 6th) so I am thinking that the certification did not fail and may have simply gone into certiffication even later than originally expected.
Unless the bug has nothing to do with the DLC content itself and instead has something to do with maybe how other things interact with the DLC, I'm pretty sure a new build is in order. The moment you alter anything, even it's a small variable, it's no longer the old build/version of the DLC and the new version has to be certified. At least that's what I've learned from my small amount of QA and programming experience out in the world. However, it's entirely possible that the issue has something to do with something else so we could see it sooner than later.
Hmmmm, well if you say XBL updated with the achievement yesterday, it's possible the issue wasn't found in certification but maybe they found it while testing future DLC or maybe even DA: Awakening for compatibility with the DLC. It's possible they pushed back the certification but it doesn't really seem likely based on when we got the release date.