New automatic vdb sampling longer meshing #75551

New Issue

matthieu barbie · 2020-04-09T14:08:45+02:00

matthieu barbie commented

2020-04-09 14:08:45 +02:00

System Information
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75

Blender Version
Broken: version: 2.83 (sub 9), branch: new-object-types, commit date: 2020-03-16 21:50, hash: 024cb564df
Worked: Version before automating raymarching vdb system, old type raymarcher

Short description of error
Before the new raymarching automatic system, the vdb density parsing and the vdb meshing was really faster. The first rendering time took 4-8 sec and re-rendering after took for this pre-processing just 3-4 second. Now each time it's took for my scene 16-20 sec of pre-processing (auto mode). With custom settings for ray step lowers of few this time (1-2 sec) but the result is bader than before with old raymarcher. If use clipping, the result start to be like blocks / pixel art than the old raymarcher not done this but speedup rendering.

So great to have control by vdb objects (and have vdb objects) but the step size with same step size than the old raymarcher not produce the same result and is longuer to pre-process. Clipping do blocking effect quite rapidly. With default rendering vdb parameters, the result is good but when need to optimise, the optimisation method done directly blocking result. It's more a return than really a bug, performance / quality return.

Exact steps for others to reproduce the error
Just playing with clipping or ray step and render.

Debug_VDB.blend

**System Information** Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 445.75 **Blender Version** Broken: version: 2.83 (sub 9), branch: new-object-types, commit date: 2020-03-16 21:50, hash: `024cb564df` Worked: Version before automating raymarching vdb system, old type raymarcher **Short description of error** Before the new raymarching automatic system, the vdb density parsing and the vdb meshing was really faster. The first rendering time took 4-8 sec and re-rendering after took for this pre-processing just 3-4 second. Now each time it's took for my scene 16-20 sec of pre-processing (auto mode). With custom settings for ray step lowers of few this time (1-2 sec) but the result is bader than before with old raymarcher. If use clipping, the result start to be like blocks / pixel art than the old raymarcher not done this but speedup rendering. So great to have control by vdb objects (and have vdb objects) but the step size with same step size than the old raymarcher not produce the same result and is longuer to pre-process. Clipping do blocking effect quite rapidly. With default rendering vdb parameters, the result is good but when need to optimise, the optimisation method done directly blocking result. It's more a return than really a bug, performance / quality return. **Exact steps for others to reproduce the error** Just playing with clipping or ray step and render. [Debug_VDB.blend](https://archive.blender.org/developer/F8459623/Debug_VDB.blend)

matthieu barbie commented

2020-04-09 14:08:45 +02:00

Added subscriber: @matthieubarbie

Brecht Van Lommel commented

2020-04-10 15:12:54 +02:00

Changed status from 'Needs Triage' to: 'Needs Developer To Reproduce'

Germano Cavalcante commented

2020-04-10 15:16:09 +02:00

Added subscriber: @mano-wii

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

New automatic vdb sampling longer meshing #75551