3D Depth Map Based Stereoscopic Shader

@ mr.spongworthy

Out of curiosity I've just tried Beyond (Steam Demo) and found that you have to enable (tick) the box with the most draw calls / vertices in the add-on tab of reshade to get 3D. You can confirm it's the right box by going through them while in Depth Map view mode in SuperDepth. However while the girls gameplay seems relatively fine, when playing as the spirit the depth map is restricted to 16:9 aspect ratio box within the 2:35:1 (cinematic) aspect ratio the game has, so you miss some processing at the extreme left and right of the image. I don't know if that can be improved, but you can get 3D in that game, albeit not always as good / complete as other games.

Hello, this shader is awesome!
I've been messing around with it a bit, and I wonder if there's a way to have it set to Side by Side but without the squashing? I'd be okay with just keeping the middle part of the screen and cutting off the sides just to get rid of the squash.
Thanks!

I think I figured it out by myself
If I change line 2313 and 2314 in SuperDepth3D.fx fromtoIt seems to work

Made a video highlighting some games this month.



Also a small Guide for Prodeus.

Thank you BlueSkyKnight for all your fantastic work!
The remaining people able to see the beauty behind the blessing of having two eyes are forever thankful to you. Please continue to exist. 😀

Hmmmm. So any ideas why it keeps crashing Cyberpunk 2077 v1.6? Things were OK for an hour or two, but after that I've been crashing all over the place with Superdepth enabled. Turn it off and all is fine, so as far as I can tell at this point it is definitely Superdepth doing it.

Yes, definitely SuperDepth 3D: It happens whenever I have the "Copy depth buffer before clearing operations" turned on. If I allow the artifacts to appear the game does not crash. If I prevent the artifacts from appearing Cyberpunk 1.6 will crash when Reshade/Superdepth tries to correct for the artifacts. Easy place to check this is V's apartment mirror, which causes artifacts whenever it is approached. With the fixes to prevent artifacts turned on it will crash for me every time.

It's a combo: SuperDepth3D + DLSS + v1.6 + Specific Depth Map settings in Reshade (those required to fix artifacts) = crash

Or maybe that's not the case. I'm now getting crashes even with DLSS off. Is there a reshade cache folder somewhere I can delete? SuperDepth VR still *seems* to be working, but SuperDepth3D has gone from working perfectly to crashing the game on load. I've restored Cyberpunk from a known good backup and uninstalled and reinstalled Reshade and SuperDepth3D, but no luck at all. It just went totally bonkers on me for no reason I can find. There's got to be some corrupt cache files somewhere (I've already blown away Nvidia's shader cache - also no luck.)

In case anyone else has this issue, it is not specific to SuperDepth; it is an incompatibility between Reshade 5.xx and Cyberpunk 1.6+.

Easiest solution seem to be downgrading to Reshade 4.9.1, which still functions fine.

This is fixed, update to latest. I played a 2 hour session of Cyberpunk 2077 with ReShade 5.5.1 without a crash (including changing graphics settings).

Thanks. I'll give it a go again!

First of all I want to thank You for the great shader and its improvements and refinements over the last years!
I just wanted to share my experiences with the Uncharted: Legacy of Thieves Collection as it didn't work "out of the box" with SuperDepth3D and I had to figure out some settings to make it work. Just in case someone wants to play this game in 3D, too Sorry if my hints are common knowledge - I'm quite new to SuperDepth3D and didn't read all the postings so far...
Using ReShade 5.5.1 and just enabling SuperDepth3D.fx caused the game to crash. When I enabled DisplayDepth.fx the depth map looked distorted. So I switched to the Add-ons tab and searched under Generic Depth for the lines with the same resolution as the rendering resolution in the game options (in my case 1280x720). There are several entries: one with several hundreds of draw calls. Don't select this line as it causes the game to crash with SuperDepth3D.fx. Instead choose one of the lines with only a few draw calls and check if the displayed depth map is correct (in DisplayDepth.fx use the option to show only the depth map). When You enable SuperDepth3D.fx the game runs fine now. Unfortunately I always had to select the suitable entry in Generic Depth manually after starting the game before enabling SuperDepth3D. I also have to quickly pause the game and disable SuperDepth3D before reloading a checkpoint (when the character failed, etc.) otherwise the game crashes. It's also necessary to disable SuperDepth3D before exiting the game to prevent a crash when starting the game the next time.
Is there a way to tell reshade to automatically choose the correct entry in Generic Depth? There were always different entries with different CRCs (?) when I started the game even in the same location. So I always have to find the correct entry manually. Using "Copy depth buffer" didn't seem to have an effect.

Another issue in the game with SuperDepth3D was the fact that the depth map didn't match correctly with the image shown on screen. DisplayDepth.fx made this quite obvious. The solution was to disable Barrel distortion and using the Screen zoom fix. To do this You have to edit the corresponding exe file as described here: www.reddit.com/r/FuckTAA/comments/ycka0s...ll_taa_dof_ca_fixes/
Now the depth map fits perfectly.

Before editing the exe file I tried to correct the depth map issue by editing the global preprocessor definitions as offered by DisplayDepth.fx. I added RESHADE_DEPTH_INPUT_X_PIXELOFFSET=-10 in DisplayDepth.fx. Unfortunately it had no effect on the depth map used in SuperDepth3D.fx. I tested RESHADE_DEPTH_INPUT_IS_UPSIDE_DOWN=1 with the same result. The preprocessor definitions only have an effect on the displayed depth map in DisplayDepth.fx but not on SuperDepth3D.fx. Is this correct?

After finishing The Lost Legacy I started to play Uncharted 4 and realized that u4.exe doesn't need to be changed (in contrary to tll.exe).

On  Uncharted 4 & TLL - TAA, DoF, CA fixes : FuckTAA (reddit.com)  now there is also a Screen zoom fix provided for u4.exe. In combination with Barrel distortion off this offers the best result for the fitting of depth map and image.

After several months of Reshade / Superdepth working with Cyberpunk it looks like the latest versions of both are not working properly together at this point. Like certain prior combos I now get a crash as soon as I get past the initial intro screen when Reshade is installed (5.6.0 reshade + 1.61 Cyberpunk).

Due to health reasons I’m limited to what displays I can use. Outside of fringe displays like HMD’s and AR glasses (which I’ve tried) there isn’t much available anyway. I’ve always dismissed anaglyph 3D due to my experiences with red/blue, the 3D effect is fine but everything else is bad.

Out of desperation, I decided to give Inficolor a try. Initial impressions were not good, but after acclimating to the drawbacks and limitations I’m seriously impressed. first thing to understand is this technology was designed to retain good color information at the expense of depth. Color and brightness issues can be mitigated in ReShade and effects like bloom and DoF can enhance perceived dimensionality. One glaring drawback is retinal rivalry, where you get opposing color information from each eye, creating a bright flickering like effect.

While researching anaglyph I came across this paper

www.researchgate.net/publication/3908713...aglyph_stereo_images

with a equation to reduce retinal rivalry and wonder if you’d consider incorporating it into SuperDepth. The main advantage to anaglyph is price and compatibly. If works with any screen and any budget.

This is probably outside the scope of this shader, but I really with there was a generic way to mod games for head tracking. I think head tracking plus Pulfrich glasses could potentially yield impressive simulated 3D while retaining excellent color and none of the artifacting associated with anaglyph.

Thanks for this amazing shader!

Edit: This newer paper claims their method is superior. Forgive the link shortener, it was got cut off in my IPad.

tinyurl.com/2p84kjyw

mr_spongeworthy wrote:

After several months of Reshade / Superdepth working with Cyberpunk it looks like the latest versions of both are not working properly together at this point. Like certain prior combos I now get a crash as soon as I get past the initial intro screen when Reshade is installed (5.6.0 reshade + 1.61 Cyberpunk).
 

This does indeed seem to be specific to SuperDepth3D and SuperDepthVR at this time; or at least and shaders that rely on depth map detection (maybe). As soon as the depth map is detected the game flatlines. Works fine with other Reshade shaders. Sure hope this is something you can fix!

crosire is working on this issue please be patient. Thank you.

Today I played with pretty much every permutation I could think of to get DLSS Frame Generation working reliably with SuperDepth3D in Cyberpunk. I played with a variety of Vsync modes (forced through NVIDIA CP), limiting FPS manually (through NVIDIA CP) and limiting FPS internally in Cyberpunk settings.

In some configurations it is very close to working, but I was unable to achieve 100% usability as there are occasional flickers and glitches. I found that the single best solution is limiting the FPS in-game to 50% of your display's refresh. Since DLSS Frame Gen disables vsync without manually capping the fps in some way you will immediately exceed your display's refresh (in my case I've been testing on an old 60hz Playstation 3D display with shutter glasses in above/below mode). With those settings, I can get Cyberpunk into a state where it appears to be generating every other frame reliably, and peaking at 60fps including generated frames. However, there are occasional glitches. I've tested to be sure I'm exceeding 30fps by reasonable amounts in all scenes with Frame Gen off. 4090 @2560x1440 DLAA & RT Path Tracing enabled I'm hitting 35-45 fps (but stuttering of course due to sub-refresh rate rendering). With Frame Gen on at 30 rendered frames + 30 generated frames things are a bit softer but the experience is generally smooth. If you guys can figure out how to resolve the remaining glitches, which look to be out-of-sync stereo frames (that's a guess), you'll have a solution that will allow stereoscopic rendering of modern titles at extremely high quality settings.

EDIT: It's possible the glitches might be occurring when SuperDepth is detecting something onscreen and attempting to auto-adjust certain depth settings. I've noticed that initiating a phone-call will reliably cause it to happen. Or possibly the GPU overhead for Frame Gen is much higher than I would have anticipated and the slight increase in GPU usage caused by the phone overlay is at the root of the problem. I'll have to try it in Witcher 3 Next Gen and Hogwarts Legacy also, as knowing Cyberpunk this could easily be "a cyberpunk thing."

Update on DLSS3 Frame Gen and Reshade/SuperDepth: I double-checked my GPU usage and I do see the glitches at far below peak GPU utilization. The clearest example is bringing up the Mantis Blades in CP2077, works fine without FrameGen, but flicker between two different depths (I think) with FrameGen on. Still haven't tested in other titles at this point, maybe I'll give Witcher3 NextGen a go soon, but at this time I can't say with certainty that this isn't Cyberpunk specific.

A bit more testing: In Witcher 3 next gen I was able to drive stereoscopy through Superdepth at 60hz/120fps with frame gen on, which I really thought would not work at all. Shockingly it mostly worked, with only the aforementioned depth glitching like I see in Cyberpunk. Entire screen will even sometimes flicker between two distinct frames. Also tried locking to 30/60 with similar results. Higher frame rates result in increased depth glitches, but do not seem to be directly related to GPU usage, but rather just increase as the frame rate increases. Not 100% sure on that of course, but that's what my testing suggests at this time.

Do any driving games work?