You know what, two things Funny_Chan.
1)Copy and pasting your identical reply in every thread you can find with RtO and PS3 in the title actually detracts from your credibility and that of Mr. Wachter. You also REposted his comment in the same thread he posted it.
2)If you read the thread from which that comment pertains, AND bother to do a little research yourself, you would find there is a huge discrepancy between what the different entities at Bioware are telling their customers.
posted by Eurypterid:
Abriel, you're really spinning this in the worst possible light you can. I'm not sure why you're choosing to do so though. Did they decide to work on the fix for the XBOX before the PS3? Yes, and it's explained why in the dev posts I linked. Does that mean they're treating PS3 owners as second class citizens or that PS3 owners are getting the shaft? I hardly think so.
But the reason it's taking so long for the PS3 version to come out isn't entirely BioWare's fault. In fact, if they shoulder any blame at all for that, it's minimal. The game has been sent to Sony for certification at least 11 days ago now. Could BioWare have decided to work on the PS3 version first, then send it for certification, then work on the other versions? Possibly, although from the way it was explained, that wouldn't have been the optimal way to go about it. Would that have meant they were treating XBOX and PC owners as second class citizens? Again, hardly. In any business there are decisions to make. Just because the particular decision might be more advantageous for one group over another doesn't mean the latter are being slighted.
So by Eurypterid's math that means the PS3 version was submitted to certification at around the time that RtO was releasing on PC/Xbox 360, but there is a catch with what Eurypterid said. On January 29, 2010 Mr. Wachter posted a reply sent to him by a Mr. Fernando which stated.
Victor Wachter:
The issue we saw on 360, which was introduced with the title update, also exists on the PS3 patch that was planned to go out with the Return to Ostagar DLC for PS3 – it is a console agnostic issue. However, the title update / patch itself (without the issue) is needed for both platforms in order to fix some main game items, as well as enable functionality for Return to Ostagar, and future functionality that benefits upcoming DLC. This meant we were unable to simply go ahead and release the PS3 version independent of pulling the 360 version, we now needed to re-open the PS3 version as well before that went public.
Once we were able to resolve the issue for 360 and delivered the second title update to MS for final certification then work began in earnest on the short hop to moving this across to PS3 and directing the test focus there. The nature of the issue was such that it required the same programmers and made more sense for that particular ‘nut’ to be cracked on the 360 first to really understand how to fix it once and for all, so this was not something we could do in parallel for both platforms.
Lastly, Sony's certification time simply takes longer than Microsoft's. It is also worth mentioning again that as we saw with the original RtO dates, even once in Cert until we actually pass an issue can still be found anytime either by ourselves or Sony/MS which would re-start the process all over again. In practical terms, what that means is that until we are virtually on the last days of certification it is not easy to provide an estimated release date – and we’re not there yet.
What we can do is update you once we get there with Sony certification, as we did with the 360 updates.
In essence what we are being told here is that the original-original decision was to program RtO first for Xbox 360 / PC (since they're nearly identical to program for) and PS3 second. Once the bug was found both DLC were pulled and sent back to the coding monkeys to fix some title screen code or some such. Now as the problem was code side all resources had to be pulled and focused entirely on the fix. This tells me there were two teams each working on their respective consoles, but 360/PC got more attention.
This is not because of some mysterious happenstance, but because Bioware made a business decision, one that others on these forums have made it a point to press, to focus on Xbox 360/PC first to "maximize" initial release day DLC sales in the quickest way possible. There was no consideration to reaching the broadest customer base possible; if it were the case work would have begun on PS3 first in order to ensure a simultaneous launch. However that would have postponed xbox and pc by several weeks most likely pushing it all into a February time window, this is before the bug fix fiasco. For Bioware this was not acceptable.
The way I read all this is that Bioware wanted money sooner rather than later. They threw the PS3 adopters under the bus and released the content on xbox/PC first.
Now I wanted the PS3 version initially, then switched over to PC when I heard it would release two weeks after xbox and PC got theirs. Upon hearing just before release that PS3 would launch same day I switched my pre-order back to PS3. Now here I am again in the same boat but already having committed to a product just to get shafted. The same shafting I wanted to avoid 8 months ago.
So perhaps its the fact we're all spoiled and got our game same day as everyone else because of a concerted effort on bioware AND sony's part to progress the game ahead two weeks faster than originally planned. Funny how that works out eh?
Perhaps Bioware should learn from this and focus on the longer developments first instead of the quick buck. Perhaps they wouldn't incur the wrath of 1/3 of their customer base.
Bioware is not squeeky clean here. They dropped the ball, made a bad decision, and now have a black eye as a result of it. Their first outting on the PS3 and they fail to make the grade in the first real test on their ability to bring equal content in equal time to an audience.
For the TLDR crowd:
*Bioware made a decision to put xbox/PC ahead of PS3 knowing PS3 certification process took longer.
*Bioware decided to pull PS3 coders to fix an issue present in the source code and not the console specific code, but still chose to apply the fix to xbox/PC first, and then go back to PS3.
*There is a communication issue as to just exactly when the PS3 version was sent to cert'. If it was 11 days prior to a Feb 9 posting that would put it at around Jan 29. However that would mean it took Microsoft only 5 days to certify a download.If Mr. Wachter is to be believed then the patch was applied the same week as the bug was found and then sent to Microsoft first then work began on the PS3 porting resulting in another weeks' delay.