How blueskydefender/depth3d works
Project type and purpose
• This is an open-source ReShade shader collection (post-process effects) rather than a traditional multi-tier web app or microservice suite.
• Its goal is to package a set of HLSL-style shader files (.fx/.fxh) plus supporting textures, so that users can drop them into ReShade’s “Shaders” folder in any DirectX 11+ game and get advanced depth-based 3D and related effects.
File structure
• Top-level folders:
– “Shaders”: primary .fx/.fxh files you’d ship to end users
– “Other Shaders”: extra or legacy shaders not part of the main suite
– “Textures”: lookup tables or other image assets the shaders reference
• Root files:
– README.md (project overview and how-to)
– _config.yml (GitHub Pages site config)
• No code directories like src/tests—this is purely assets and configuration.
Extract insights from the README
• Key filters: SuperDepth3D.fx (depth-map-based stereoscopic rendering) and Overwatch.fxh (an assistant to auto-tune depth parameters per game).
• No in-repo companion apps: the VR viewer is a separate download (deprecated).
Main components
a. User environment
– Game (DX11+ executable)
– ReShade injection layer (DLL hook)
b. Asset bundle (this repo when installed)
– Shaders folder → .fx/.fxh HLSL passes
– Other Shaders → auxiliary filters
– Textures → LUTs & supporting maps
c. GPU & pipeline
– Vertex/Pixel Shader stages invoked by ReShade
– Shader outputs: modified RGBA frames
d. Configuration & tuning
– ReShade.ini (user-editable settings, not in repo but implied)
– Depth-map calibration by Overwatch.fxh
Relationships and data flows
• Overwatch.fxh reads per-game presets (embedded or user-supplied) to adjust depth constants before SuperDepth3D runs.
Architectural patterns & design principles
• Plugin pattern: the shaders are dynamically discovered by ReShade at runtime.
• Separation of concerns:
– Core effects (.fx) vs. utility/includes (.fxh) vs. raw assets (Textures)
– Main vs. legacy/experimental (Shaders vs. Other Shaders)
• Declarative configuration: behavior is driven by shader code and ReShade’s INI, no procedural binaries in the repo.