# Shift in Volume Render - Better than I can segment bones

**URL:** <https://discourse.slicer.org/t/shift-in-volume-render-better-than-i-can-segment-bones/2488>\
**Category:** Support\
**Tags:** segmentation\
**Created:** [April 1, 2018, 3:24pm UTC](https://discourse.slicer.org/t/shift-in-volume-render-better-than-i-can-segment-bones/2488 "2018-04-01T15:24:38Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pieper](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.slicer.org/pieper/32/8_2.png) [@pieper](https://discourse.slicer.org/u/pieper)\
**Post date:** [April 1, 2018, 5:46pm UTC](https://discourse.slicer.org/t/shift-in-volume-render-better-than-i-can-segment-bones/2488/2 "2018-04-01T17:46:24Z")

</div>

Hi -

This question comes up from time to time - have a look at this discussion for background on this:

> [@Save volume rendering as STL file](https://discourse.slicer.org/t/save-volume-rendering-as-stl-file/524/6):
>
> Semi-transparent volumetric cloud = your image data, so you already have it. No processing is performed on the data, it is visualized directly using [raycasting](https://en.wikipedia.org/wiki/Volume_rendering). Volume rendering visualization parameters are mostly defined by transfer functions (opacity, color, gradient), which are saved in the Slicer scene. STL file cannot store volumetric cloud, it only stores a surface mesh = hard boundary of your printed object. What confuses most people that volume rendering may give the illusion that ther…

---

_[View the full topic](https://discourse.slicer.org/t/shift-in-volume-render-better-than-i-can-segment-bones/2488)._