[SOLVED] DoF InfiniteFocus & Curves Problems

It seems like there are a few problems with DoF after the 2.0 update. One is broken completely but the second is easily fixable by switching some values. (I am using AdvancedDoF on a log depth game)

InfiniteFocus: This setting seems to be broken and does not effect the distance that the DoF cuts off. I am trying to use this setting in a log depth game and I have had no success with getting the DoF to end near the camera. (ReShade 1.1 worked fine)

FarBlurCurve & NearBlurCruve: These 2 settings seemed to have switched places and near curve now effects the far curve and vice versa. To fix this as the user I just switched the values and it seems to work just fine.

Bump. I am only bumping this thread because I know many people use the infinite focus feature and it makes DoF unplayable when implementing it into a preset

You probably just forgot to enable "RESHADE_DEPTH_INPUT_IS_REVERSED", which games like GTA V need in addition to "RESHADE_DEPTH_INPUT_IS_LOGARITHMIC".

crosire wrote: You probably just forgot to enable "RESHADE_DEPTH_INPUT_IS_REVERSED", which games like GTA V need in addition to "RESHADE_DEPTH_INPUT_IS_LOGARITHMIC".

Why did the depth buffer work fine in 1.1? It should be the same (I can't test reversed right now, since I'm on vacation)

Elimina wrote:

crosire wrote: You probably just forgot to enable "RESHADE_DEPTH_INPUT_IS_REVERSED", which games like GTA V need in addition to "RESHADE_DEPTH_INPUT_IS_LOGARITHMIC".

Why did the depth buffer work fine in 1.1? It should be the same (I can't test reversed right now, since I'm on vacation)

See: github.com/crosire/reshade-shaders/issues/23

OtisInf wrote:

Elimina wrote:

crosire wrote: You probably just forgot to enable "RESHADE_DEPTH_INPUT_IS_REVERSED", which games like GTA V need in addition to "RESHADE_DEPTH_INPUT_IS_LOGARITHMIC".

Why did the depth buffer work fine in 1.1? It should be the same (I can't test reversed right now, since I'm on vacation)

See: github.com/crosire/reshade-shaders/issues/23

Ah so that's how it is, this helped fix The Division and Far Cry Primal, however I have tested them with these options before but then I toggled them while the game was running, for this to work correctly it seems the game must be started with the proper depth detection settings already configured or it'll just display a pure black or pure white depth image if you attempt to change it at runtime.
(Set reverse to 1 and set logarithmic to 1 - good to know for other games in the future too and I assume this also goes for the other ones IE Dying Light, Witcher 3, GTA V, Just Cause 3 etc.)