# Volume rendering invalid texture dimensions

**URL:** https://discourse.vtk.org/t/volume-rendering-invalid-texture-dimensions/3917
**Category:** Support
**Created:** [August 5, 2020, 2:00pm UTC](https://discourse.vtk.org/t/volume-rendering-invalid-texture-dimensions/3917 "2020-08-05T14:00:55Z")
**Posts on this page:** 1
**Showing post:** 8

<div class="post-metadata">

### Author: ![sankhesh](https://discourse.vtk.org/user_avatar/discourse.vtk.org/sankhesh/32/73_2.png) [@sankhesh](https://discourse.vtk.org/u/sankhesh)
#### Post date: [August 7, 2020, 4:22pm UTC](https://discourse.vtk.org/t/volume-rendering-invalid-texture-dimensions/3917/8 "2020-08-07T16:22:22Z")

</div>

> [@mykolav](#):
>
> whole volume with vtkOpenGLGPUVolumeRayCastMapper and SetPartitions(2, 2, 2) : ~3fps  
> partitioned volume with vtkMultiBlockVolumeMapper 2x2x2 : ~70fps

`SetPartitions` should be analogous to the MultiBlockVolumeMapper approach as all it does it splits up the volume into the request number of textures and streams each texture to the GPU. The only additional step that paritioning with GPU volume mapper does over multiblock volume mapper is sorting the blocks before rendering. Having said that, I don’t think the SetPartitions logic is stress-tested enough. I am sure there are areas of improvement there.

---

_[View the full topic](https://discourse.vtk.org/t/volume-rendering-invalid-texture-dimensions/3917)._