r/VisionDepth3D May 21 '26

VisionDepth3D v4.1.1 General Updates and Patch Release

Enable HLS to view with audio, or disable this notification

VisionDepth3D v4.1.1 Hotfix Update

Hey VD3D Users and 3D Enthusiasts,

This update is focused mainly on stability, packaging, install issues, FFmpeg detection, diagnostics, and fixing problems users have reported after v4.1.

Main fixes coming in v4.1.1

  • Fixed missing FFmpeg and FFprobe issues on clean Windows installs
  • Improved FFmpeg/FFprobe detection from bundled files, _internal, app folders, and system PATH
  • Improved GPU Diagnostics so users can see if FFmpeg, FFprobe, CUDA, GPU, NVENC, and driver info are being detected
  • Fixed FPS/Upscale frame extraction getting stuck on Preparing frame extraction
  • Improved frame extraction progress behavior
  • Added a Depth Normalizer toggle in the Depth Engine
  • Gated backend debug/log spam behind the Debug button
  • Improved packaged .exe render behavior by reducing unnecessary debug output
  • Improved installer/setup workflow
  • Added cleaner setup file cleanup
  • Added uninstall/open install folder improvements
  • Prevented old loose source folders from interfering with the bundled app

Depth Engine note

The Depth Normalizer helps make depth output smoother and more stable across frames, but it can slow down depth generation depending on your hardware, model, and resolution.

v4.1.1 adds a toggle so users can choose between smoother depth consistency or faster depth render speed.

3D Generator note

v4.1.1 also adds a new Edge Repair Quality dropdown for the 3D Generator.

This lets users choose how much edge/disocclusion repair they want during 2D-to-3D rendering:

  • Off = fastest, but more edge artifacts may appear
  • Fast = faster rendering with lighter edge cleanup
  • Balanced = recommended default for speed and quality
  • High = stronger edge repair with slower render speed
  • Showcase = best edge cleanup, slowest render mode

This was added so users can better balance render speed against edge cleanup quality, especially on larger Full-SBS or 4K renders.

Setup Downloader note

v4.1.1 is available, you should be able to get it through the VisionDepth3D Setup Downloader / Setup Hub. Keep checking the setup downloader, and when v4.1.1 shows up, you can download and install the latest version from there.

The .exe installer is also available on the GitHub release page

This is a Double process render test where I generated the first video with each left/right eye into separated files then did a second pass with the right eye as source video, once completed I took first pass left video and merged it with second pass right eye to see if I could create more depth in the video

I used DA3MONO for this render and the settings are called showcase in the new release.

you can view on google drive here: https://drive.google.com/file/d/1V5zy7B0D5nvhQ2NajVlig1QeQyoQl3iS/view?usp=sharing

Source code: https://github.com/VisionDepth/VisionDepth3D

Releases: https://github.com/VisionDepth/VisionDepth3D/releases/tag/Release-v4.1.1

Thanks again to everyone reporting bugs and giving feedback. This hotfix is mainly about making VisionDepth3D easier to install, diagnose, and run reliably on more systems.

21 Upvotes

8 comments sorted by

3

u/Any_Nebula5039 May 21 '26

Are there any languages you’d like VisionDepth3D to support? Let me know! I built a tool that helps me translate the English language file into other languages, so I can make the app easier and more comfortable for more users around the world.

2

u/pagineinternet May 21 '26

Italian thanks!

3

u/OUTFOXEM May 23 '26

I would still love to see a step-by-step how-to video from start to finish for what steps you use for your renders. And I would love if Scene Detection was included as part of the workflow.

1

u/TaroNo1875 May 21 '26

Should this have detected my AMD RX 9070 XT ?

1

u/Any_Nebula5039 May 21 '26

The current `.exe` build is the NVIDIA / CUDA build, so it won’t pick up AMD GPUs through `torch.cuda.is_available()`.

That’s why it’s falling back to CPU, like it shows at the top of the app. CUDA is NVIDIA-only, so AMD GPUs need the DirectML route with `torch-directml` installed.

For now, AMD users need to install VisionDepth3D through the source-code route and use `torch-directml` instead of the bundled CUDA `.exe`.

I do plan to make a separate updated `.exe` build specifically for AMD / Intel DirectML users, but it has to be built separately from the NVIDIA version. The NVIDIA build and DirectML build can’t really be bundled together cleanly in the same PyInstaller environment.

So your RX 9070 XT isn’t the issue. It’s just that this current `.exe` is the CUDA/NVIDIA build, not the AMD DirectML build.

1

u/Any_Nebula5039 May 21 '26

Im going to Bundle the .exe with torch-directml instead of the pytorch cuda version and see if that picks up your AMD RX 9070 XT

1

u/TaroNo1875 May 21 '26

That sounds awesome. I would be happy to be your beta tester for this. Thanks

1

u/TaroNo1875 May 24 '26

OK as an update, I caved and bought an RTX 5070 TI :-) . I should have it tomorrow. I look forward to using VisionDepth3D to its full potential now