[forrestthewoods]

The issue isn’t that 20ms is an unreasonable slice size. The issue is you can’t perform an arbitrary slice.

Imagine a game that runs at 50Hz/20ms frame. Unusual but let’s go with it because the exact value doesn’t matter. Ideally this update takes AT MOST 20ms. Otherwise we miss a frame. Which means most frames actually take maybe 15ms. And some may take only 5ms. If you drew this on a timeline there would be obvious sleeps waiting for the next frame to kick off.

If you take an arbitrary sequence of 20ms slices you’re not going to capture individual frames. You’re going to straddle frames. Which is really bad and means each pixel is measuring a totally different body of work.

Does that make sense?

[coherentpony]

Ah yes. Ok.

Yes, that makes perfect sense. Thanks.