There appears to be order of magnitude (from approx.15 ms / frame to approx 150 ms / frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude (from 0000015:0000015 ms / frame to ~ 150 ms / frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude (from 0000015:0000015 ms/frame to ~ 150 ms/frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude (from 0000015:0000015 ms/frame to 0000118:0000150 ms/frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude (from 0000015:0000015 ms/frame to 0000118:0000150 ms/frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4

There appears to be order of magnitude (from 0000015:0000015 ms/frame to 0000118:0000150 ms/frame) degradation in slice scrolling performance when volume rendering is enabled (slice is not shown in 3d view).
See demo in this screencast: https://www.screencast.com/t/fJ9O9N2El
This was done on a mac with the latest nightly.

Problem is reproducible on Windows and using Qt5, too.

The problem was originally reported on the Slicer forum: https://discourse.slicer.org/t/major-slice-scrolling-performance-degradation-with-volume-rendering-on/938/4