I found another one

Comments

• Sibshops@feddit.cl ⁨2⁩ ⁨hours⁩ ago

  I don’t get this one. The refresh rate one makes sense. The monitor accepted a frame rate faster than it could draw.

  source

  • spicehoarder@lemmy.zip ⁨2⁩ ⁨hours⁩ ago

    Don’t ask a man his salary, a woman her weight, or a pentium how many cores

    Or something…

    source
  • ThatGuy46475@lemmy.world ⁨1⁩ ⁨hour⁩ ago

    It doesn’t have to make sense technologically it’s just a play on “how tall are you” “ how much do you weigh” (which also aren’t technical requirements for compatibility)

    source
  • YoSoySnekBoi@kbin.earth ⁨1⁩ ⁨hour⁩ ago

    My best guess is that it has something to do with most render pipelines using CPU frame scheduling. Since the GPU can only process shaders, the CPU has to do e.g. input logic, reading textures from disk, etc. So in most engines, the CPU gives the GPU basic directions for each frame, and then the GPU goes off to process them while the CPU prepares the next set of directions.

    If the CPU isn't fast enough, the GPU sits around waiting for instructions and it causes stuttering and FPS drops. If the GPU isn't fast enough, instructions from the CPU queue up and it causes input lag. To get around the input lag, most engines intentionally drop frames and decrease FPS (basically forcing the CPU to wait) in order to keep everything in sync.

    ---

    TL;DR The CPU runs the game logic and the GPU displays the result, so the GPU can only render frames as fast as the CPU can prepare them and vice-versa.

    source