The fix in D11095 fixed visual FOV issue but the problem is not addressed fully (turns out the FOV is expanded to cover the shifting range rather than to precisely cut at the image border, leading to longer calculation time as more strokes and triangles are potentially included).

During me coding overscan function I found this is still a problem and now it's fixed. Later I'll provide an overscan patch so it allows user to control the margin in which line art is calculated.