# VR/AR and NVIDA IndeX
**URL:** https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245
**Category:** VR/AR
**Created:** [March 24, 2024, 1:38am UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245 "2024-03-24T01:38:45Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@aqfx](https://discourse.paraview.org/u/aqfx)
#### Post date: [March 24, 2024, 1:38am UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245/1 "2024-03-24T01:38:46Z")
Hi All, in a couple of weeks I’m scheduled to give a demo of ParaView running in VR- hopefully with a collaborator on board too.
Previously I’ve built a case study based on one of our forecasts of severe air pollution across Australia- [AQFx\_air\_pollution](https://youtu.be/UufXEeMakIA?si=BqBIIzF1gePWgdND) - and this looks really good in VR- at least when not animating.
We have the capability of running a large GPU server- and potentially using NVIDIA Index to speed up the volume rendering. However- when viewed in VR, there are challenges with output- the volume rendered outputs are spatially displaced, and show up as two separate stereo images. Can anyone please advise?
Currently using the Paraview setup as shown below. The headset is an OQ-3 linked to a Win-11 PC using Steam-Link. The GPU is an NVIDIA RTX 2070.
Thanks!
Martin
Client Information:
Version: 5.12.0
VTK Version: 9.3.20231030
Qt Version: 5.15.2
vtkIdType size: 64bits
Embedded Python: On
Python Library Path: C:\Users\marti\Downloads\ParaView-5.12.0-MPI-Windows-Python3.10-msvc2017-AMD64\bin\lib
Python Library Version: 3.10.11 (tags/v3.10.11:7d4cc5a, Apr 5 2023, 00:38:17) [MSC v.1929 64 bit (AMD64)]
Python Numpy Support: On
Python Numpy Path: C:\Users\marti\Downloads\ParaView-5.12.0-MPI-Windows-Python3.10-msvc2017-AMD64\bin\Lib\site-packages\numpy
Python Numpy Version: 1.25.2
Python Matplotlib Support: On
Python Matplotlib Path: C:\Users\marti\Downloads\ParaView-5.12.0-MPI-Windows-Python3.10-msvc2017-AMD64\bin\Lib\site-packages\matplotlib
Python Matplotlib Version: 3.7.2
Python Testing: Off
MPI Enabled: On
ParaView Build ID: superbuild 2891f7bc1038636e1e1abd941be85832dfd65d01 (!1178)
Disable Registry: Off
Test Directory:
Data Directory:
SMP Backend: TBB
SMP Max Number of Threads: 12
OpenGL Vendor: NVIDIA Corporation
OpenGL Version: 3.2.0 NVIDIA 531.41
OpenGL Renderer: NVIDIA GeForce RTX 2070 SUPER/PCIe/SSE2
Accelerated filters overrides available: No
Connection Information:
Remote Connection: No
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 25, 2024, 11:13am UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245/2 "2024-03-25T11:13:19Z")
Hi @aqfx !
> [@aqfx](#):
>
> We have the capability of running a large GPU server- and potentially using NVIDIA Index to speed up the volume rendering. However- when viewed in VR, there are challenges with output- the volume rendered outputs are spatially displaced, and show up as two separate stereo images. Can anyone please advise?
Could you share a screenshot of the issue ?
FYI @LucasGandel @Lucas_Givord
Best,
---
### Author:  [@aqfx](https://discourse.paraview.org/u/aqfx)
#### Post date: [March 27, 2024, 1:36am UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245/3 "2024-03-27T01:36:18Z")
Hi Mathieu,
The IndeX version looks as [follows](https://1drv.ms/v/s!AoxrjlonHd_4l5JT7nrs0-97UDKK6Q?e=pmT8ah); and the Paraview default volume version is [here](https://1drv.ms/v/s!AoxrjlonHd_4l5JUrz6t8UaBbdjrfA?e=GrNFns).
Also- it’s possible that I’ve not set things up properly in the case study, so have also provided the[setup and data](https://1drv.ms/f/s!AoxrjlonHd_4l5JnPFeyWBnuecZYQw?e=1aaevB) just in case this is helpful.
Many thanks
Martin
---
### Author:  [@jmensmann](https://discourse.paraview.org/u/jmensmann)
#### Post date: [April 3, 2024, 4:11pm UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245/4 "2024-04-03T16:11:44Z")
Hi Martin,
The NVIDIA IndeX plugin hasn’t been tested with ParaView VR, so unfortunately your use-case is currently unsupported.
The IndeX volume getting displaced when you rotate the camera is probably caused by differences in camera transformation handling between VR and normal mode. Or are you rendering multiple volumes with IndeX at the same time? (that should actually not be possible in normal ParaView mode)
There is also currently no support for a stereo camera, that’s what I assume to be the reason for getting two separate (side-by-side?) images.
Cheers,
Jörg
---
### Author:  [@aqfx](https://discourse.paraview.org/u/aqfx)
#### Post date: [April 10, 2024, 12:54am UTC](https://discourse.paraview.org/t/vr-ar-and-nvida-index/14245/5 "2024-04-10T00:54:11Z")
Hi Jörg,
Thank-you for following up on our enquiry- much appreciated.
In our set-up we are currently rendering a single volume with IndeX.
Anyway- very happy to work within the current capabilities of Paraview VR/XR- and look forward to other updates as they become availabe.
Regards
Martin