By using this site, you agree to our Privacy Policy and our Terms of Use. Close
Adinnieken on 07 October 2013
Edit Thread
ethomaz said:

Hello guys... I did a litte vacation this weekend... so I will try to resume what I read.

HIGHLIGHTS OR KEY POINTS

  • 15 co-porcessors listed: eight inside the audio block, four move engines, one video encode, one video decode and one video compositor/resizer... SO NOTHING TO HELP GRAPHICS, NO DGPU, NO SPECIAL SAUCE.

I disagree.  By offloading the video encode, decode, and resizing to a separate processor, you free the GPU and CPU up.  Likewise with the move engines and audio block (CPU).

They're what Microsoft calls "Free" resources.  Meaning, developers don't have to program for them specifically, the API is built so that when certain functions are called they automatically take advantage of the features.  Behind the scenes, the API is doing the work so that the developer doesn't have to write custom code to use it.

  • Co-processors are mostly reserved to Kinect and SystemOS.

 No they aren't.  There is a processor within the audio block used by Kinect.  The system will take advantage of some of the processors for various functions, but games will also take advantage of those processors as well.  The Move engines, as an example are part of the GPU and thus are utilized during graphical rendering.

  • Each game is shipped with a OS... so the virtual machine for Games only run the OS together with the game.

Um...no they didn't say that.

  • They confirme the CPU is weak and the biggest problem for fps drops.
    		•

    No, they didn't say that.  They said the CPU is a bottleneck for frames per second in any given system.  Even for the PS4 that's true.