@SuperWristBands said:
Man, how does that even happen? SSF4 uses GFWL (right?) so shouldn't Microsoft have that really long certification process so that this exact thing doesn't happen?
It sure does! I don't really get how this hasn't been tested, I guess Capcom test using an internal version with no GFWL ties, but Microsoft still have to approve patches (and take their sweet time doing so) so one has to ask what the fuck were they doing?
@SuperWristBands said:
Man, how does that even happen? SSF4 uses GFWL (right?) so shouldn't Microsoft have that really long certification process so that this exact thing doesn't happen?
@Sooty said:
Edit: It's fixed now, and this could have happened on any version. It's a result of lazy testing, nothing to do with the downsides of a platform.
It was fixed that fast? Are you sure it was widespread? I didn't even know Microsoft could react that fast.
Yep it's widespreadapparently it's just an issue with the GFWL side of things (the Xbox Live crap) so I think that's why a patch got put out so quickly, seems it was more of a Microsoft problem than Capcom, but really Capcom still should have tested a GFWL version of the game considering everybody else is forced to put up with it.
Log in to comment