McFadge
Member
Not really because it doesn't just add the lines, but approximates the non-rendered lines from information gather during the rendering of the last frame. That's an additional step of computation and responsible for that method not being easily detectable by pixel counting.
If I have this right... There's another buffer that records the velocity of each rendered object, so that the missing information in the current frame can be filled by looking at the previous frame and gathering pixel information from there (with the offset provided by the object's movement) to estimate how the missing pixels should be coloured. Is this a basic understanding of what's happening?
If that's the case, would we expect the interlacing effect to be worse near the edges of the screen, where there's a greater chance that information needed to fill the pixels possibly wasn't rendered in the previous frame?