Alby_da_Wolf said:
SvennoJ said:
Alby_da_Wolf said:
Yes, artifacts are quite common with interpolation, particularly in motion and when using computationally lightweight interpolation methods, like linear ones. As I already wrode many pages before, most probably they had to use interpolation, and a simple one too, because the multiplayer version uses the cloud only as hub to route data packets between users, while it uses the players' consoles themselves as computational nodes.
|
I guess the simple interpolation comes into play when the temporal blending is not possible, when for example rotating. Another example of stationary vs spinning.
(images)
(Pressing take screenshot randomly until I had an image facing the same way, while I'm spinning left on the spot) Not a full screen effect either as the gun stays sharp, selective linear interpolation.
The stationary picture can only be sharp if they use temporal blending. These are the 2 extremes of the algorithm they use. While strafing and walking you get a combination of the two techniques with varying results.
Anyway the stationary blended 1080p pictures still don't come close to singleplayer
(image)
|
Yes, temporal blending is a good choice when it's possible, for stationary and very slow apparent motion, as besides giving better results it's even more lightweight than interpolation.
|
Yup, the interesting part happens where the code decides how to mix the 2 techniques

I wish I could get better screenshots, facebook upload really sucks for fine detail, source is a 161kb jpg :/
Yet you can see the vertical lines from where the cables were 1 frame ago. Somehow the game knows that it has to solidify the relatively fast moving cables in this shot. Maybe it always does the interpolation first then blends the previous frame onto it, to add detail, based on a simple ruleset (that obviously fails in this shot)
When you're a sniper you get full 1920x1080 visuals, run and gun style is a mixed bag. Smart in a way, anyone who takes screenshots or takes in the scenery usually stands still, while it wouldn't be visible on compressed you tube videos anyway.