By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Machiavellian on 30 June 2013
Edit Thread
ChrolloLucilfer said:
Reduced

Developing Common features is a good possiblity. But only If the PS4 Camera sell well enough to bother using that feature. If the Camera goes on to sell only a couple a million, I can't see many Third Party jumping at the chance to use it's features.

It's about efficiency.  If I spend X amount of time building a feature for the Xbox One or Xbox 360, I want utilize that as much as possible.  If Sony builds in the same capabilities for voice recognition as the Xbox One, or the developer creates something that works passibly, then they'll do it.  If a game for the Xbox One builds in a face mapping feature, then in all likelihood the developer would include that in the PS4 version.  Just because I create the hooks, doesn't mean I force that feature upon you.  I can do an IF statement to check and see if you have the necessary hardware to support a feature.

If the PS4 Camera has a good attach rate with the PS4, then yes it would be worthwhile for Third Party creating Kinect based features on X1. As there would be potential audience for those types feature to be ported over for PS4 Camera use. But If the PS4 Camera sales are poor, why would a Third Party Developer spend their own time and money on developing features which only X1 audience is going to use to any large degree? It would be a waste resources which could be saved or spent on other aspects of the game developement instead.

Gamers still have this notion that developers time and resources are bottomless.  Developers who think like this are the ones who are hurting from one game to the next because they spend to much time on things that does not produce sales.  For a developer they have to budget their time efficiently and pretty much cost each feature or they can lose money.  As stated, Unless the sales of the PS3 match a certain install base, then creating features for it starts to be a liability.  

 

Lets take the voice recognition that Kinect has.  People have wondered why developers have supported this features within their games for Kinect but not the headset or even Sonys Eye.  The reason is that MS has a complete API that makes it easy for developers to integrate voice for Kinect while the headset and Sony Eye does not.  This will be the same this gen unless Sony provide an API for their PSeye because most developers will not want to create their own voice recognition code just to add that feature to a game.