On the right side of the screen, near the actor's face, over the lamp:

On the right side of the screen, near the actor's face, under the lamp:

On the left side of the screen, the ventilation system:

On the left side of the screen, the first and second exhaust of the ventilation system:

On the top left side of the actor's head and the top and lower top right side of the actor's head:

This relates to artifacts similar to the image above, on the top left side, but this also shows the merging that happens sometimes beyond window blinds towards other objects. For example the window blind artifact slightly merges with the actor's silhouette of white clothing creating a different kind of artifact:

These screenshots are but a fraction of what is happening when the movies are playing because the artifacts come and go and appear in waves thus making them much more noticeable, especially on big screens. However, I did use "Large" Search radius in order to produce more artifacts so you can better study them. Using "Average" makes less artifacting but again on the same areas, while "Small" almost completely eliminates them (unnoticeable unless you are looking for them specifically).

Also, while testing, I noticed the following:

There are 3 specific scenes on 3 different movies I run tests and all showed the same result. For some reason:

A) When Motion vectors grid is set to 12 px. Average 2 - Search radius has to be set to small to eliminate window blind artifacts.

B) When Motion vectors grid is set to 24 px. Large 2 - Search radius can be set to either Average or even Large and I get absolutely no window blind artifacts

However, even 16 px. Average 0 gives almost the same amount of window blind artifacts as 12 px. Average 2. I believe this is abnormal, how can there be no improvement on 16 px. Average 0 on either average or large but I get no window blind artifacts on 24 px. Large 2 on both average and large?

Would it not be more normal if for example:
0 window blind artifacts for Average should be coupled with 24 px. Large 2 and
0 window blind artifacts for Large should be coupled with 28 px. Large 2 or below?

Is it the "analyse.main.search.distance" on "override"? Or should I look for something different?

I was thinking something in terms of a more complex search method to avoid the blind artifacts that exist on "Average" but not on "Small" for example. There is nothing that can be done to improve the "Average" search - even at the expense of a lot of CPU resources?

Does anybody know if there is a way to improve the search radius quality? For example have "Average" and "Large" better detect artifacts at the cost of performance?

Thank you in advance.