Re: Your help requested for Definitive Guide to perfoverlay.drawfps 1 OSD

While you work for EA, I believe what you posted to be incorrect.

IIRC CPU is the polling of inputs and such (where you're looking/firing/movement/etc) and most of the various calculations required to feed the GPU data to render, SIM (simulation) is the CPU calculation of world/object physics/game logic/etc (where everything is located and what it's doing based on update packets from the server, with interpolation/extrapolation), GPU is the actual FPS and how long it takes the GPU to render each frame (this framerate can be higher than your refresh rate if vertical sync is set to 'off' or 'fast'), and mp/s is the megapixels per second.

Unlike previous engines these are asynchronous and the time taken for one of them doesn't impact how long another will take. This part is new and the specifics of how it works are largely unknown at this time, what is known is the GPU is allowed to render at higher frame rates than the CPU can achieve; but does this mean it simply renders duplicate frames when the CPU can't keep up? (...no one knows!). What this means is that your CPU (the first line) can * itself and take a long time to do anything making your inputs feel like they're not registering (or are delayed) despite your system maintaining a high and stable FPS (the third line) such that everything on screen still appears smooth (without any jolts or jittering).

Based on your values: your inputs are being polled and all the various new data is being generated by the CPU 79 times per second (taking 12.7ms each time), the CPU is updating and calculating the position/movement of everything in the world 45 times a second (22ms between updates, with each taking 9.7ms to calculate), and (utilizing everything previously calculated) a new frame is being rendered by your GPU every 4.2ms resulting in 238 frames per second (1000/4.2=238fps).