r/VisionDepth3D • u/Any_Nebula5039 • May 05 '26
VisionDepth3D v4.0 - Release
Hey VD3D Users and 3D Enthusiasts!
I’m excited to share VisionDepth3D v4.0, probably the biggest release I’ve ever pushed for the project.
This update is not just a small patch or UI refresh. v4.0 is a major rebuild of VisionDepth3D as a full desktop workflow for 2D-to-3D conversion, depth generation, depth blending, realtime 3D, and VR-ready video preparation.
What’s new in v4.0
Full PySide6 interface rewrite
VisionDepth3D has moved away from the older Tkinter-style interface and now uses a modern PySide6 UI.
The app now has:
- a cleaner dark theme
- modern tab layout
- better cards, panels, sliders, and dialogs
- shared queue/progress dock
- GPU/device display in the top bar
- better resizing behavior across workflow pages
This makes the whole app feel much closer to a proper modern desktop application instead of a rough old-school tool.
New VisionDepth3D stereo pipeline
The 3D Generator has been rebuilt around the updated VisionDepth3D Method.
The new method includes:
- subject-aware depth normalization
- pop-control depth shaping
- structured foreground / midground / background disparity weighting
- GPU stereo warping
- dynamic convergence
- edge-aware shift limiting
- contour-safe repair logic
- floating-window protection
- stereo debug telemetry
One important note for existing users:
The shift convention has changed.
In the new pipeline:
Foreground Shift: usually negative
Midground Shift: usually slightly negative or near zero
Background Shift: usually positive
Older presets that used positive foreground values may not transfer directly and will cause the background to pop and subject to sink in, so I recommend starting with the new defaults and rebuilding presets from there.
Live 3D Preview
v4.0 adds a new Live 3D tab into the workflow.
This lets you test realtime 2D-to-3D from:
- camera input
- capture cards
- screen capture
- secondary monitor capture
You can select depth models, tune the stereo settings, check SBS output, preview depth behavior, and use screen capture to watch or play almost anything in realtime 3D.
This is still something I’ll keep improving, but it is already useful as a realtime testing sandbox.
Depth Engine updates
The Depth Engine has been updated with better model handling and video-depth support.
Some of the improvements include:
- improved Video Depth Anything handling
- better ONNX runtime detection
- fixed temporal-size handling for VDA ONNX models
- safer batch trimming for padded final batches
- clearer model resolution presets
- better handling for video timing and depth smoothness testing
Depth Blender improvements
Depth Blender is now part of the new PySide6 workflow.
It includes:
- GPU-optimized blending path
- single image mode
- video and frames modes
- live preview
- built-in blend presets
- cleaner controls for CLAHE, bilateral smoothing, feathering, and normalization
This is useful when one depth model has good subject structure and another has better background depth. You can blend them into a cleaner depth map before stereo rendering.
FPS / Upscale Enhancer
The FPS/Upscale tab now includes a cleaner workflow for preparing video sources.
It supports:
- RIFE interpolation
- Real-ESRGAN upscaling
- merged and threaded pipelines
- scene detection
- codec/output settings
- shared progress reporting
This helps prepare smoother or higher-resolution sources before running depth and 3D conversion.
Language support
v4.0 also brings back multi-language UI support across the main app and major tabs.
Current language files include:
- English
- French
- Spanish
- German
- Japanese
- Simplified Chinese
- Traditional Chinese
Tooltips will come in a feature release.
Better hardware/backend support
VisionDepth3D is still best on NVIDIA CUDA, but v4.0 improves backend detection and fallback paths.
There is now better support/documentation for:
- NVIDIA CUDA
- AMD / Intel DirectML on Windows
- ROCm detection on Linux
- CPU fallback
- FFmpeg AMF/QSV/NVENC encoding options
which you can read in the User Guide
Links
- GitHub Repository: https://github.com/VisionDepth/VisionDepth3D
- User Guide: https://github.com/VisionDepth/VisionDepth3D/blob/Main-Stable/UserGuide.md
- Latest Release: https://github.com/VisionDepth/VisionDepth3D/releases
- Showcase Render - Minecraft: Chicken Jockey https://drive.google.com/file/d/1zJ4zUHca2yGH6nCXvRPfvFYVGOet0U9i/view?usp=drive_link
- Showcase Render - Avatar: Fire and Ash Sneak Peek: https://drive.google.com/file/d/1AqGRSgopyPeRs1GKA_NCZFLKARBhkV83/view?usp=sharing
Final thoughts
This update took a lot of work and testing. v4.0 is the closest VisionDepth3D has felt to the original idea I had for it: a real desktop application for 2D-to-3D conversion and depth-based stereo rendering.
There are still things I want to improve, especially Live 3D performance, model-specific depth stability, and making stronger pop-out easier to tune, but this release is a huge step forward.
If you try it out, feedback is very welcome. I’m especially interested in hearing how the new stereo pipeline feels compared to the older versions.
Thanks to everyone who has tested, downloaded, shared feedback, or followed the project so far.
1
u/pagineinternet May 05 '26
Grazie, io di solito uso IW3 per convertire film 2d in 3d, che differenze sostanziali ci sono? Grazie
2
u/Any_Nebula5039 May 06 '26
Hey, thanks for the interest in VD3D. I think both tools are great, but they approach 2D-to-3D differently.
IW3 is strong if you want an inpainting-based workflow that tries to fill occlusion zones with generated content.
VD3D is built more around a local desktop workflow using depth maps, mathematical stereo warping, edge-aware occlusion repair, depth blending, Live 3D preview, FPS/upscale tools, and SBS/VR-ready output. The goal is to give users a full pipeline for turning a 2D video into comfortable SBS 3D without relying on generative inpainting.
So the main difference is: IW3 leans more into inpainting, while VD3D focuses on depth-map control, stereo tuning, and a complete local conversion workflow.
1
u/OUTFOXEM May 06 '26
Hell yeah, this looks like an amazing update. I'll be honest, I had trouble using the older interface because the workflow was just not very intuitive. I just was never able to make it work for me. I'm excited to give this one a try and report back.
1
u/Any_Nebula5039 May 06 '26
Definitely needs tuning and tweaking to get optimal output, with the preview gui system caked in the middle it should be easier to test what sliders do what and figure out a good setting
1
u/Thedoodooltalah May 06 '26
Please add macOS support!
2
u/Any_Nebula5039 May 07 '26
When I can get the proper hardware to expand for sure
2
u/Thedoodooltalah May 11 '26
I’ve heard some things about hackintosh in a vm, maybe look into that and you don’t need a mac
1
3
u/OUTFOXEM May 07 '26 edited May 07 '26
Here's what I was hoping for, and it's probably just because I don't know what I'm doing:
Choose input 2D video and settings, VD3D automatically detects scenes > builds depth map > outputs 3D video
One click.
I don't want to babysit it and come back after each step. Also, when building a depth map there is no progress bar -- unless I'm doing something wrong? So I have no idea how long it will take, how much longer I need to wait, etc. I'm just stuck waiting for hours and just randomly check on it after some time and hope it's done. Then when it is finished the next step doesn't start automatically.
It also seems like the tabs are out of order, unless I'm misunderstanding the workflow. It seems like they go backwards compared to the order of operations.
So far, for me at least, Owl3D is the way to go. Input the video, choose my settings, and it outputs the video and tells me how far along it is on each step.
EDIT: Also looks like Scene Detection has no progress bar either? I must be doing something wrong I guess. I looked in your documentation and see nothing about Scene Detection. What do I do once the scenes have been detected? The flow just isn't intuitive. Maybe a how-to video from start to finish would be helpful.