# Model and Segment rendering issues with 4.10 (and 4.11)

**URL:** <https://discourse.slicer.org/t/model-and-segment-rendering-issues-with-4-10-and-4-11/4685>\
**Category:** Support\
**Tags:** segmentation, slicerrt\
**Created:** [November 8, 2018, 5:15pm UTC](https://discourse.slicer.org/t/model-and-segment-rendering-issues-with-4-10-and-4-11/4685 "2018-11-08T17:15:01Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![cpinter](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/cpinter/32/7995_2.png) [@cpinter](https://discourse.slicer.org/u/cpinter)\
**Post date:** [November 13, 2018, 2:40pm UTC](https://discourse.slicer.org/t/model-and-segment-rendering-issues-with-4-10-and-4-11/4685/5 "2018-11-13T14:40:41Z")

</div>

Volume rendering changed quite a bit internally after 4.8.1. There have been discussions about this, they will probably help. Such as this:

> [@How to set volume rendering preset using Python](https://discourse.slicer.org/t/how-to-set-volume-rendering-preset-using-python/3063/2):
>
> Hi Oliver, There have been some improvements since 4.8.1 that makes it easier for us to do this. So if you use the latest nightly, then this is what you can do: Easier setup of volume rendering (no need to create the display node and update it from the logic): volRenLogic = slicer.modules.volumerendering.logic() displayNode = volRenLogic.CreateDefaultVolumeRenderingNodes(volumeNode) This is not very clean, because it uses widgets from the volume rendering module, but you can apply a shift li…

---

_[View the full topic](https://discourse.slicer.org/t/model-and-segment-rendering-issues-with-4-10-and-4-11/4685)._