# Does Nvidia IndeX plugin support vdb files?

**URL:** https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817
**Category:** ParaView Support
**Created:** [September 5, 2023, 9:00am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817 "2023-09-05T09:00:12Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![fashing](https://discourse.paraview.org/user_avatar/discourse.paraview.org/fashing/32/12357_2.png) [@fashing](https://discourse.paraview.org/u/fashing)
#### Post date: [September 5, 2023, 9:00am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/1 "2023-09-05T09:00:12Z")

</div>

Hi, I am new to ParaView and try to use ParaView 5.11.1 for volume rendering.  
I take the testcases from openvdb [official website](https://www.openvdb.org/download/).  
I can render the testcase (e.g. bunny\_cloud) successfully with volume representation and I can load IndeX plugin successfully (test with a .vtu file).  
However, I cannot render any .vdb files with IndeX option.  
Here’s the warning message I got when I try to switch the representation option to NVIDIA IndeX.

> [paraview] vtkDataObject.cxx:499 WARN| vtkImageData (0x24a21250): Attempted to ShallowCopy from null.

I thought IndeX plugin is used to support volume rendering, is there anything I miss?

BTW, while launching the paraview web, how can I load multiple plugins?  
The document says “–plugins [List of plugins]”, but it seems it only took the first argument after the flag.

Thank you for your time!

---

<div class="post-metadata">

### Author: ![ben.boeckel](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/b/ea5d25/32.png) [@ben.boeckel](https://discourse.paraview.org/u/ben.boeckel)
#### Post date: [September 5, 2023, 11:20am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/2 "2023-09-05T11:20:55Z")

</div>

For the IndeX problem itself: @cory.quammen @Sankhesh_Jhaveri

For the pvweb bit, @jourdain

---

<div class="post-metadata">

### Author: ![fashing](https://discourse.paraview.org/user_avatar/discourse.paraview.org/fashing/32/12357_2.png) [@fashing](https://discourse.paraview.org/u/fashing)
#### Post date: [September 11, 2023, 5:14am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/3 "2023-09-11T05:14:48Z")

</div>

Hi @cory.quammen, @Sankhesh_Jhaveri, @jourdain,  
Do you have any idea about my post?  
Thank you!

---

<div class="post-metadata">

### Author: ![Sankhesh\_Jhaveri](https://discourse.paraview.org/user_avatar/discourse.paraview.org/sankhesh_jhaveri/32/3374_2.png) [@Sankhesh\_Jhaveri](https://discourse.paraview.org/u/Sankhesh_Jhaveri)
#### Post date: [September 11, 2023, 2:45pm UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/4 "2023-09-11T14:45:41Z")

</div>

@fashing Do other image data work for you? Try creating a wavelet and render it using the IndeX plugin.  
If that works for you, there might be a bug with the OpenVDB reader integration in ParaView.

---

<div class="post-metadata">

### Author: ![fashing](https://discourse.paraview.org/user_avatar/discourse.paraview.org/fashing/32/12357_2.png) [@fashing](https://discourse.paraview.org/u/fashing)
#### Post date: [September 12, 2023, 1:43am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/5 "2023-09-12T01:43:01Z")

</div>

Yes, like I mentioned, a .vtu file can be rendered by the IndeX plugin on my side.

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 12, 2023, 7:19am UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/6 "2023-09-12T07:19:40Z")

</div>

a .vdb produce a partitioned dataset, this may be the cause of the problem.

---

<div class="post-metadata">

### Author: ![Sankhesh\_Jhaveri](https://discourse.paraview.org/user_avatar/discourse.paraview.org/sankhesh_jhaveri/32/3374_2.png) [@Sankhesh\_Jhaveri](https://discourse.paraview.org/u/Sankhesh_Jhaveri)
#### Post date: [September 12, 2023, 12:17pm UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/7 "2023-09-12T12:17:51Z")

</div>

Well, that will do it. So the plugin has to handle casting the partition datasets to image data.

Sankhesh

---

<div class="post-metadata">

### Author: ![steve\_r](https://discourse.paraview.org/user_avatar/discourse.paraview.org/steve_r/32/8305_2.png) [@steve\_r](https://discourse.paraview.org/u/steve_r)
#### Post date: [November 6, 2023, 3:08pm UTC](https://discourse.paraview.org/t/does-nvidia-index-plugin-support-vdb-files/12817/8 "2023-11-06T15:08:01Z")

</div>

Would be great if there was a way to extract the image data from the partition dataset inside ParaView, so not every plugin has to do that operation on its own.
