[vtkusers] Restrictions of vtkVolumeTextureMapper3D

[Francois Bertel]

Hello,

It is first limited by your graphics card capabilities. Look for the
value returned by the GL_MAX_3D_TEXTURE_SIZE request.

For example, on my nVidia Quadro FX 3600M on Linux:
$ glxinfo -l | grep GL_MAX_3D_TEXTURE_SIZE
returns
GL_MAX_3D_TEXTURE_SIZE = 2048

It means it can fit up to a 2048x2048x2048 uniform grid, if there is
enough VRAM. (it depends on the number of tuples, on the number of
components per tuple and on the size of a component in bytes)
It means it cannot fit a 2049x1x1 uniform grid, even if there is enough VRAM.

To discover the value on other platforms, see the VTK FAQ (glview
third-party tool on Windows, OpenGL Driver Monitor on Mac):
http://www.vtk.org/Wiki/VTK_FAQ#How_do_I_check_which_OpenGL_versions_or_extensions_are_supported_by_my_graphic_card_or_OpenGL_implementation.3F

On Wed, Nov 11, 2009 at 11:10 AM, Michael Kloster
<vtkusers at michael-kloster.de> wrote:
> Hello everybody!
>
> Does anybody know what the restrictions of the vtkVolumeTextureMapper3D
> regarding to the extends of image/voxel data are?
>
> Bye,
> Michael
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the VTK FAQ at:
> http://www.vtk.org/Wiki/VTK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.vtk.org/mailman/listinfo/vtkusers
>



-- 
François Bertel, PhD  | Kitware Inc. Suite 204
1 (518) 371 3971 x113 | 28 Corporate Drive
                      | Clifton Park NY 12065, USA