Welcome, Guest.
Username: Password: Remember me

TOPIC: D3D8 and depth buffer range problem (?)

D3D8 and depth buffer range problem (?) 1 year 11 months ago #1

  • lowenz
  • lowenz's Avatar
  • Offline
  • Posts: 158
  • Thank you received: 15
Max Payne: all-white!


Chrome:

and pressing ESC to change menu/exit (with animated scene):

In-game I can see the SSAO applied only to the weapon model!

Range (->HUD) problem?
Last Edit: 1 year 11 months ago by lowenz.
The administrator has disabled public write access.

D3D8 and depth buffer range problem (?) 1 year 11 months ago #2

  • lowenz
  • lowenz's Avatar
  • Offline
  • Posts: 158
  • Thank you received: 15
Up :p

Chrome's problem is clearly game-related, SSAO works perfectly in some scenes, and doesn't work well in others (look at the weapon):

(Perfect)


(Weapon Only SSAO)

But for Max Payne? Why it's all white?
Last Edit: 1 year 11 months ago by lowenz.
The administrator has disabled public write access.

D3D8 and depth buffer range problem (?) 1 year 11 months ago #3

  • crosire
  • crosire's Avatar
  • Offline
  • Posts: 2453
  • Thank you received: 1393
Depthbuffer in Chrome only contains the weapon model, probably because the game clears it before rendering the FPS hands/weapon. Not much can be done about that. =)
And as for Max Payne: ReShade appearently grabs the wrong one here ...
Cheers, crosire =)
The administrator has disabled public write access.

D3D8 and depth buffer range problem (?) 1 year 11 months ago #4

  • lowenz
  • lowenz's Avatar
  • Offline
  • Posts: 158
  • Thank you received: 15
Uhm.....UT 2004:

without weapon:


same place with weapon (spawn):


It's exactly the Chrome problem.....so it's not Chrome, it's ReShade, somehow :p
Last Edit: 1 year 11 months ago by lowenz.
The administrator has disabled public write access.

D3D8 and depth buffer range problem (?) 1 year 10 months ago #5

  • brussell
  • brussell's Avatar
  • Offline
  • Posts: 139
  • Thank you received: 113
Is this kind of problem "fixable" within reshade, or are we doomed to live with it forever...?
The administrator has disabled public write access.

D3D8 and depth buffer range problem (?) 1 year 10 months ago #6

  • crosire
  • crosire's Avatar
  • Offline
  • Posts: 2453
  • Thank you received: 1393
In some games the depthbuffer doesn't contain environement information, because the game clears the buffer before starting to render the FPS weapons. In that case one would need to prevent that clear, which is possible, but hard to detect on a generic level (might add a "#pragma" option for it in the future to allow game specific user configuration).
Some games render environment and weapon into different depthbuffers altogether and ReShade's algorithm chooses the one with the weapon. It still needs improvement to choose the one with the most useful data (there are games with more than 30 depthbuffers, so it's no easy task to figure out the best match, though it works quite well already).

So yeah, both these cases are fixable unless there's yet another reason I did not list =)
Cheers, crosire =)
The administrator has disabled public write access.
The following user(s) said Thank You: brussell