Welcome, Guest.
Username: Password: Remember me

TOPIC: DoF issue with Arkham Knight

DoF issue with Arkham Knight 1 year 2 months ago #1

I'm working on a preset for Arkham Knight. I have one major problem. I can get DoF looking fantastic with Batman, and fantastic in the Batmobile, but never both. The camera changes and I'm not sure if's throwing the depth off or what, but if I have Batman's DoF perfect and I get into the Batmobile, EVERYTHING blurs. So thus I have to change all the settings to accomodate that.

My ? is, is there any workaround for this? Maybe a way to switch DoF settings when switching to batmobile or even when pressing L1 to get in the car?
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #2

  • crosire
  • crosire's Avatar
  • Offline
  • Posts: 2452
  • Thank you received: 1392
I'm guessing ReShade is unable to find the correct depth buffer when you are in the batmobile. Check the depth output. It should be a black/white representation of the scene.
Cheers, crosire =)
Last Edit: 1 year 2 months ago by crosire.
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #3

Thanks for the response.

You were correct. All white screen when in batmobile, perfectly find outside of it. Any ideas on how to get reshade to find correct depth buffer?
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #4

  • crosire
  • crosire's Avatar
  • Offline
  • Posts: 2452
  • Thank you received: 1392
There is nothing you can do then unfortunately.
Cheers, crosire =)
Last Edit: 1 year 2 months ago by crosire.
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #5

Update, So I enabled SMAA. Depth buffer works on batmobile...some of the time. As I drive it will do good and then go all white. What would cause that?
Last Edit: 1 year 2 months ago by jminternelia.
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #6

Well for the time being I found a fix - disabling manual focus. This way when the depth buffer decides its not going to cooperate DoF doesnt overtake the screen. Still keen to know what causes the depth buffer to go empty at random while in batmobile tho..
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #7

  • crosire
  • crosire's Avatar
  • Offline
  • Posts: 2452
  • Thank you received: 1392
That's how ReShade works. There are lots of ways games can store depth information and that can change with every frame. So ReShade scans all possible candidates every 30 frames or so and tries to find the best match with the statistics it collected. This gives back the correct depth buffer most of the time, but on some occasions the algorithm fails and you get the wrong one back. This seems to be the case when you drive in the batmobile.
Cheers, crosire =)
The administrator has disabled public write access.

DoF issue with Arkham Knight 1 year 2 months ago #8

  • piltrafus
  • piltrafus's Avatar
  • Offline
  • Posts: 73
  • Thank you received: 15
crosire wrote:
...There are lots of ways games can store depth information and that can change with every frame. So ReShade scans all possible candidates every 30 frames or so and tries to find the best match with the statistics it collected[...]on some occasions the algorithm fails and you get the wrong one back...

Would be possible at all to have a switch for reshade to stop scanning for changes in the way the depth buffer is stored? so if it finds the depth buffer at some point maybe we can press a key so it stops looking for changes? would that solve the problem?

Another possible way to deal with this would be to set an option for "auto" or "manual" depth buffer scan. Auto would be as it is now ( described by crosire above). For manual an specific mode for depth buffer scanning should be manually set in reshade.fx.

I'm aware it may not make any sense. Just throwing a suggestion.
The administrator has disabled public write access.