Rectangle artifact in RoboCop

[achtchaern]

In RoboCop - Rogue City (and probably lots of other games), there is an artifact in the shape of one (or two) 3D projected rectangles. Some observations:

• The rectangles are visible primarily due to a mismatch in brightness between the inner and the outer area.
• In the screenshot, there are two rectangles visible, the left one is clearly very noticable whereas to see the right one, you have to pixel-peep (take a look at the second shot)
• The larger the motion vectors, the further the rectangles are moving towards the screen center. In the example screenshot, you can see that on the left side, the line is much further towards the screen center than on the right side, because the pixel's movement speed is much higher on the left.
• The brightness mismatch also seems to scale with the pixel speed, which is why it almost looks like a vignette effect by gradually getting darker towards the left screen edge
• Changing graphics settings does not change anything
• The issue persists without HUD (it was disabled when capturing the screenshot)
• The 3D projected rectangles are also visible in CP2077 (see here)
• Tested with 0.70 and 0.80

[doktorsleepelss]

These rectangles are also visible on official FSR3 implementations. Only really noticeable if you hyper focus on it while moving fast or with large/fast camera swings.

So chances are only AMD themselves can fix it in future versions.

[achtchaern]

Sure, on your shots, it's hardly noticeable because there is no brightness mismatch. But in the described case of RoboCop, one can't oversee it. I wouldn't have reported it if it was this mild as in Avatar or Immortals.

[doktorsleepelss]

Okay, I think you're right it is an actual vignette post effect. In cyberpunk, using this mod gets rid of it, and the border is no longer as visible anymore. https://www.nexusmods.com/cyberpunk2077/mods/11196?tab=description

EDIT: video https://www.youtube.com/watch?v=MasJAt3BzN0

I think the parameter to get rid of it in in UE5 r.Tonemapper.Quality 0 or r.Tonemapper.Quality 1. I'll check if it works in a minute.

[doktorsleepelss]

Okay, I can confirm r.Tonemapper.Quality 1 does fix it. But it does kind make the entire picture look a bit brighter.

[achtchaern]

2 days ago, I tried exactly this command via Engine.ini and it didn't help. But I found out the reason thanks to you; the game overrides this cvar during runtime (r.tonemapper.quality = 5). So you have to enter it via the ingame console, which obviously is a bit annoying.

Is there a way to make this setting persistent?

[Nooblet16]

That's simply either the UI layer being pulled to the side or the vignetting layer, you usually see it in games where there is UI garbling after frame gen. But since Robocop doesn't have UI garbling, I'd imagine it's the vignetting layer that's being garbled with frame gen and pulled.

Unfortunately in UE5 you can't disable vignetting without also disabling tone mapping, so your colours and exposures would end up looking all wrong if you change the tone mapper.

Oddly enough, I didn't notice it when I tried it in Robocop, but then again I was frequently crashing in that game so I got rid of frame gen after a while.

[achtchaern]

The lack of the original tonemapping can be easily compensated for with a bit of ReShade. But whenever I want to play RoboCop, I 'have to' add the US keybaord layout (because with my country's keyboard layout, the console key is a dead key and therefore not working), open the ingame console (enabled via mod from Gamers Nexus), and enter the command 'r.tonemapper.quality = 1'