# raytracing in vtk

**URL:** https://discourse.vtk.org/t/raytracing-in-vtk/2364
**Category:** Support
**Created:** [January 1, 2020, 9:16pm UTC](https://discourse.vtk.org/t/raytracing-in-vtk/2364 "2020-01-01T21:16:49Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![Dave\_DeMarle](https://discourse.vtk.org/user_avatar/discourse.vtk.org/dave_demarle/32/6_2.png) [@Dave\_DeMarle](https://discourse.vtk.org/u/Dave_DeMarle)
#### Post date: [January 3, 2020, 9:23pm UTC](https://discourse.vtk.org/t/raytracing-in-vtk/2364/5 "2020-01-03T21:23:53Z")

</div>

I am not aware of any current work to enable VolumeRendering in [VisRTX](https://github.com/NVIDIA/VisRTX) and thus OptiX within VTK. There are some leanings toward promoting IndeX from ParaView up to VTK, but I don’t know of any plans for tight OptiX/IndeX interoperability.

OSPRay’s path tracer in VTK also lacks volume rendering. That option will get volume rendering later this year when we bump to OSPRay 2.x and add [OpenVKL](https://www.openvkl.org/). OSPRay’s ray caster already has VolumeRendering, but could use minor tweaks to improve sampling in some situations.

---

_[View the full topic](https://discourse.vtk.org/t/raytracing-in-vtk/2364)._