# Stitching artifact with volume rendering

**URL:** <https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering/20885>\
**Category:** Support\
**Created:** [December 2, 2021, 1:56pm UTC](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering/20885 "2021-12-02T13:56:29Z")\
**Posts on this page:** 1\
**Showing post:** 3

<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:** [December 2, 2021, 4:16pm UTC](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering/20885/3 "2021-12-02T16:16:01Z")

</div>

Stitching artifacts while rendering large volumes AMD GPUs can be solved by adjusting the number of partitions by copy-pasting a few lines of Python code as shown here:

> [@Stitching artifact with volume rendering large volumes (Feb 17 2021 nightly)](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering-large-volumes-feb-17-2021-nightly/16390/18):
>
> OKAY! (1,1,2) seems to work! THANKS A MILLION!!

I would recommend to go with NVidia if you need to render large volumes. Either AMD drivers are lower quality, or maybe NVidia drivers are just as bad but VTK is tested more with NVidia and so VTK contains more fixes or workarounds for NVidia bugs.

---

_[View the full topic](https://discourse.slicer.org/t/stitching-artifact-with-volume-rendering/20885)._