[vtkusers] vtkVolumeTextureMapper3D behaves differently between v5.1 and v6.2

Weiguang guan guanw at rhpcs.mcmaster.ca
Mon Sep 14 09:55:39 EDT 2015

Hi David,

I'll try vtkImageResize. Thanks.


On 11/09/2015 1:48 PM, David Gobbi wrote:
> Hi Weiguang,
> You can do the image resizing as a preliminary step with 
> vtkImageResize, which does efficient band-limited sinc interpolation 
> and can do a good job of shrinking the image without introducing 
> aliasing artifacts.
> Hopefully someone else will answer your question about 
> vtkVolumeTextureMapper3D (I haven't used it in a while).
>  - David
> On Fri, Sep 11, 2015 at 11:22 AM, Weiguang guan 
> <guanw at rhpcs.mcmaster.ca <mailto:guanw at rhpcs.mcmaster.ca>> wrote:
>     Hello VTK users,
>     We develop a viz system using vtkVolumeTextureMapper3D for volume
>     rendering. Recently, we've moved up from v5.1 to v6.2. After that,
>     we notice our viz system has a significant slow-down in rendering
>     speed (compared on the same computer) when volume size is large,
>     say LxWxH ~= 512^^3 . It can always render small volumes at
>     interactive rate.
>     I know that vtkVolumeTextureMapper3D needs to resample large
>     volume to fit in 128*256*256 (BTW, our data is regular volume data
>     with a single component). But this down-sampling process is not
>     new in 6.2. Are there other changes that cause the performance
>     issue? Does anyone experience the same issue? Thanks.
>     Best,
>     Weiguang

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20150914/f888f9b8/attachment.html>

More information about the vtkusers mailing list