# Stitching artifact with volume rendering large volumes (Feb 17 2021 nightly)

**URL:** <https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering-large-volumes-feb-17-2021-nightly/16390>\
**Category:** Development\
**Created:** [March 5, 2021, 3:40pm UTC](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering-large-volumes-feb-17-2021-nightly/16390 "2021-03-05T15:40:11Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![lassoan](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/lassoan/32/13_2.png) [@lassoan](https://discourse.slicer.org/u/lassoan)\
**Post date:** [March 6, 2021, 3:29am UTC](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering-large-volumes-feb-17-2021-nightly/16390/16 "2021-03-06T03:29:27Z")

</div>

One more thing to try. You can partition the volume (upload to GPU in smaller blocks) using `SetPartition` method. For example, you can try this script (or change partitions to 4,4,4 or 1,1,2, …) and see it if makes any difference:

```python
threeDViewWidget = slicer.app.layoutManager().threeDWidget(0)
vrDisplayableManager = threeDViewWidget.threeDView().displayableManagerByClassName('vtkMRMLVolumeRenderingDisplayableManager')
vrMapper = vrDisplayableManager.GetVolumeMapper(getNode('CTChest'))
vrMapper.SetPartitions(2,2,2)

```

Overall, I don’t see much difference when using partitions, but `SetPartition(4,4,4)` seems to decrease TDR occurrence a bit for me (that otherwise would quite frequently occur with the “Adaptive” quality option).

---

_[View the full topic](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering-large-volumes-feb-17-2021-nightly/16390)._