At 6 mn 30 I found clues of a native ~1080p resolution (the top right of the hologram).New Arkham Knight video running on PS4 is out. Visuals look great, but there is some nasty shader aliasing from time to time.
1080p?
At 6 mn 30 I found clues of a native ~1080p resolution (the top right of the hologram).New Arkham Knight video running on PS4 is out. Visuals look great, but there is some nasty shader aliasing from time to time.
1080p?
At 6 mn 30 I found clues of a native ~1080p resolution (the top right of the hologram).
Really? I first thought it is an ghosting artifact from temporal aa.Very crap motion 'blur' implementation.
Hopefully this is either from photo mode or a replay, but motion blur shouldn't be there in a game running at a high framerate.Taken from the PS4 version of Projects Cars. On paper it looks great: 1080p, 60fps (imagine forza 5 smoothness and clarity on PS4 with 40 cars), on paper only because it's 2015 so mandatory industry standards are fully there, deal with it:
Hopefully this is either from photo mode or a replay, but motion blur shouldn't be there in a game running at a high framerate.
It's just an old-school blend with previous frames. It's not motion blur at all (to few samples to simulate continuous sampling), but the radial quality shows exactly what's happening as the vector of motion is into the screen.So is this MB implementation intentional or maybe a bug?
That would have been my first thought...Really? I first thought it is an ghosting artifact from temporal aa.
It's full screen, every pixel. What kind of AA solution indiscriminately blends the previous frame?That would have been my first thought...
That's a possibility, although AFAIK 30 fps capture just capture every other frame. I don't recall any other examples of 30 fps captures of 60 fps material exhibiting 'double exposures'.perhaps it's simply an artifact from a capture device capturing at 30fps and blending frames together.