# Volume Rendering when SetUseDepthPeeling(True) disappeared in Windows OS

**URL:** <https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278>\
**Category:** Development\
**Created:** [November 17, 2022, 9:54am UTC](https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278 "2022-11-17T09:54:33Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [November 17, 2022, 9:54am UTC](https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278/1 "2022-11-17T09:54:33Z")

</div>

Hello, everyone, recently I find a situation abount different volume rendering performance between Windows and Linux OS.

I would to realize volume rendering in the 3d view, sometimes I would display surface rendering and volume rendering at the same time. To confirm the depth information correctly, I would use the setting parameters, SetUseDepthPeeling(True).

But the difference occurs, If in Linux system, the volume rendering will be displayed as expected. But in Windows system, the volume rendering will not display, eventhough I move the mouse on the 3d View.

Then I switch to “View Controllers” module, unchecked “Use depth peeling” , then the volume rendering will displayed as expected. After that, even I checked the “Use depth peeling” again, the volume rendering will displayed all time.

So to my confusion, why in Windows system, when SetUseDepthPeeling(True), the volume rendering will not displayed as expected, but in Linux, all is right.

---

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [November 17, 2022, 12:11pm UTC](https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278/2 "2022-11-17T12:11:25Z")

</div>

here is the View Controllers module, and the Use depth peeling checkbox.  
 ![viewControllers](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/d/8/d8e77d88224bea7cfffe3d6bf04c8dd5e3ed1f80.png)

Any advice will be appreciated!  
And thanks to @lassoan @muratmaga @pieper @cpinter in advance, expect to your  
professional answer and advices.

---

<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:** [November 17, 2022, 8:18pm UTC](https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278/3 "2022-11-17T20:18:49Z")

</div>

I remember encountering this issue (you need to disable and re-enable depth peeling for volume rendering to work). If you can reproduce it with the latest Slicer Preview Release then please submit a bug report to [https://issues.slicer.org](https://issues.slicer.org). Thank you!

---

<div class="post-metadata">

**Author:** ![StephenLeePeng](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/stephenleepeng/32/11892_2.png) [@StephenLeePeng](https://discourse.slicer.org/u/StephenLeePeng)\
**Post date:** [November 18, 2022, 2:30am UTC](https://discourse.slicer.org/t/volume-rendering-when-setusedepthpeeling-true-disappeared-in-windows-os/26278/4 "2022-11-18T02:30:52Z")

</div>

Thanks, now I used Slicer version is Slicer-4.13.0-2022-01-16-linux-amd64, and windows version is built by source codes one years ago.

I want to know the problem is occured by different GPU version, such as in Linux, I use Nvidia 1080 GPU, bu t in Windows, I use intel UHD Graphics driver, or any other reason.  
 ![inter-graphics](https://us1.discourse-cdn.com/flex002/uploads/slicer/original/3X/4/5/459092263f37cce80cf3f55e655258dc0dda140a.png)

And I will use the latest Slicer Preview Release as you recommend and try to reproduce this bug.