# nvindex error when axes enabled
**URL:** https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805
**Category:** ParaView Support
**Created:** [March 12, 2020, 11:37pm UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805 "2020-03-12T23:37:33Z")
**Posts on this page:** 13
**Page:** 1
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [March 12, 2020, 11:37pm UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/1 "2020-03-12T23:37:34Z")
volume rendering a structured grid using representation “nvidia index” i get:
```
vtkOutputWindow.cxx:76 ERRI nvindex: 1.0 PVPLN main error: Trying to set unsupported z-buffer precision 0. Please verify the status of the X-server when the precision is reported as 0.
```
when the “data axes grid” or “axes grid” box is checked. performance then drops massively (fps drops from \>200 to \<10) relative to no-axes.
when representation is “volume” i don’t have this error message but the performance still drops (a lot but not as much) with axes on.
my nvidia card is a 2060s…i get “vtkOutputWindow.cxx:86 … datasets in double format are not natively supported…will convert with corresponding overhead…” if i save my data in double format. that goes away when i save as single. this is fine and as expected. but this axes thing cuts performance way more than even that on-the-fly conversion does.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 13, 2020, 2:27am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/2 "2020-03-13T02:27:20Z")
StructuredGrid can’t be represented with the NVidia Index representation.
I assume that you are converting to ImageData or UnstructuredGrid ?
I can’t reproduce with either of them. (ArchLinux, ParaView 5.8.0, 1050 Ti, 440.59)
Please state :
Version of ParaView ? Where from ?
OS ?
GPU driver ?
Please share your dataset if you can.
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [March 13, 2020, 2:37am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/3 "2020-03-13T02:37:30Z")
Resample to image data, yes. Sorry didnt realize that mattered (new to paraview).
Ubuntu 18.04 ,5.8.0, 2060s, 440.59
I’ll see if I can get a dataset that is shareable…
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 13, 2020, 2:44am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/4 "2020-03-13T02:44:06Z")
Did you download ParaView from : [https://www.paraview.org/download/](https://www.paraview.org/download/) ?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 13, 2020, 2:46am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/5 "2020-03-13T02:46:16Z")
I tried with this image dataset. I do have the double warning, but the FPS is quite high, even with the Axes.
[index.vti](https://discourse.paraview.org/uploads/short-url/9i4IwLZ9THnvXLgTPHbZkmfT7kT.vti) (541.8 KB)
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [March 13, 2020, 4:10am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/6 "2020-03-13T04:10:05Z")
my paraview is from there yes.
and ok ill try this data set later today and come back.
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [March 13, 2020, 6:21am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/7 "2020-03-13T06:21:32Z")
the only difference is the clicked axes box. that fps drop is pretty consistent if i rotate the model etc.
what other settings would you like to see?
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 13, 2020, 6:38am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/8 "2020-03-13T06:38:06Z")
My bad, I reproduce and the FPS drop is quite visible !
This is a known issue, see here :
[https://gitlab.kitware.com/paraview/paraview/issues/17487](https://gitlab.kitware.com/paraview/paraview/issues/17487)
We hope to fix it for 5.9.0.
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [March 13, 2020, 7:40am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/9 "2020-03-13T07:40:33Z")
Ok fair enough and thanks Will look out for it.
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [January 19, 2021, 8:33am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/10 "2021-01-19T08:33:41Z")
so i’ve just retried this on 5.9rc2 and rc4…it crashes both with and without the nv plugin activated before i even get to toggling the axes setting.
---
### Author:  [@jonreiter](https://discourse.paraview.org/u/jonreiter)
#### Post date: [January 26, 2021, 1:38am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/11 "2021-01-26T01:38:38Z")
runs in 5.9 but axes issue still present.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 26, 2021, 9:09am UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/12 "2021-01-26T09:09:31Z")
Well, the issue has not been closed so it is expected. It is now targeting 5.10.
---
### Author:  [@liangwang0734](https://discourse.paraview.org/u/liangwang0734)
#### Post date: [February 5, 2021, 4:16pm UTC](https://discourse.paraview.org/t/nvindex-error-when-axes-enabled/3805/13 "2021-02-05T16:16:06Z")
One possible side effect is that the screenshot shows a small number of white (transparent?) pixels, in both volume and nvindex representations.