A post on the N4G forums has rumors swirling that PlayStation 3 cross-game voice chat was held back due to threats made by EA. We spoke to EA and Sony regarding this rumor.The post, written by N4G forum-goer Super_Secret who claims to be a Sony employee, explains that Cross-Game voice chat ran into a snag because certain games from "A rather large company" wouldn't support the feature.
He refers back to trouble including custom soundtracks to work in earlier PlayStation 3 firmware revisions. According to Super_Secret, PS3 titles have to be developed with custom soundtrack support, and one of this big company's more popular titles wouldn't support it.When they found out that a new firmware update was going to suddenly make one of their games look inferior to just about every other game released, they protested. A lot. They threatened everything, from legal action to dropping support for the PS3 all together.
The post goes on to suggest that a similar situation occurred with cross-game chat, causing our tips line to fill up with angry emails, one of which even referred to the situation as a "Potential WATERGATE of the videogame industry."While the poster doesn't mention EA by name, a coded message later in the thread makes the company he or she is implicating perfectly clear once translated (thanks streetmagix for the translation from Base64):" It's not Activision. It's not Ubisoft. It's not Capcom. It's not Insomniac. It's not Konami. It's not Take 2. It's not Midway. It's not Squaresoft. are wE All getting the picture yet?
One point I want to reiterate - there's a difference between the games that didn't work with in-game XMB and the games that DID work with in-game XMB but DIDN'T work well with custom soundtracks, so stop picking out the ones that simply didn't do in-game XMB. Also, it wasn't just ONE game that caused this, either. Although one title does come to mind and it wasn't even what you or I would call a "Big" game. I'll give you a hint: HPatOofP.
