@kenobit lower decks è un piccolo capolavoro. Tutto.

@hazelnot since there's some amount of staggering that happens naturally between the CPU and GPU, the end to end latency is usually going to be something in the ballpark of the frame interval * 2. so the CPU submits work within its 16.6 ms, and the gpu completes its work within its own 16.6, and the two will drift within some overlap to a normal total of up to 33.3 milliseconds of total latency when everything is on time

@guardaminfaccia mi aspettavo che proseguisse con un 80 enne che riusciva a leggere tranquillamente le scritte sul pacchetto, e poi si alzava e partiva di corsa su un sentiero in montagna

ma forse è perché incontro troppi 80 enni che mi superano sui sentieri di collina :D

@hazelnot when vsync is on, and a frame is presented early, the gpu driver blocks the thread that requested a present so that it doesn't run faster than the GPU (this is an oversimplification). when the all of the rendering work is finished on the GPU and it is late, the present stalls until the next vblank before flipping the back buffer. so if you're targeting 60 fps on a 60 fps screen, the normal cadence is 16.6 ms, a hitch is + 16.6 * N where N is how many intervals late you are rounded up

@giornalismo
articolo21.org/2025/11/i-poste…
In occasione della Giornata internazionale per l’eliminazione della violenza contro le donne del 25 novembre, l’Unione Sportiva Lecce aderisce

@hazelnot modern computers still use vertical blank interrupts to indicate when it is safe to start scanning out a new frame. these come at a cadence like 60 hz, aka 16.6 milliseconds, and the game's cadence has to match that for everything to look and feel ok when stuff is in motion

@mms unfortunately, it's not.

@hazelnot these steps can be staggered in exciting ways, but let's ignore that. as far as the computer is concerned, the distance in time between frame step 1 and the end of step 4 is your latency. (your monitor will also add latency, but that's out of the game's control)