# Image Culling in XRInterface
**URL:** https://discourse.paraview.org/t/image-culling-in-xrinterface/13823
**Category:** VR/AR
**Created:** [January 29, 2024, 10:38pm UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823 "2024-01-29T22:38:11Z")
**Posts on this page:** 8
**Page:** 1
### Author:  [@Sam00](https://discourse.paraview.org/u/Sam00)
#### Post date: [January 29, 2024, 10:38pm UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/1 "2024-01-29T22:38:11Z")
Hi,
I have been using Paraview’s VR capabilities to inspect 3D image data (uniform rectilinear grid). I’m amazed how well it works and how useful it is to view and navigate the data in VR.
A feature of Paraview 5.10.1 OpenVR plugin I found really useful was the way it culled (unsure if that’s the right term) the image when the camera collides with it. It almost worked as a dynamic crop, which was helpful since the built-in dynamic crop does not work for image data.
This behavior seemingly has changed in the newer versions of Paraview though, i.e. in the OpenXR plugin of version 5.12 for example. Here, the camera colliding with the image culls the image without rendering the inside of the image volume:
I can get this version of the plugin to crop the image in the way it used to by scaling the image to a certain size, at which point it is cropped properly (very far away from the camera though):
Is there a way of replicating the camera collision behavior I’m after in the OpenXR plugin? I really like the UI improvements that come with the updated versions of the plugin.
Thanks!
---
### Author:  [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [January 30, 2024, 8:01am UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/2 "2024-01-30T08:01:58Z")
Maybe @mwestphal@tgalland @LucasGandel can have some inputs ?
---
### Author:  [@LucasGandel](https://discourse.paraview.org/u/LucasGandel)
#### Post date: [January 30, 2024, 8:37am UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/3 "2024-01-30T08:37:53Z")
This is a regression in VTK, it was fixed in [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/10783](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10783).
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 30, 2024, 10:08am UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/4 "2024-01-30T10:08:32Z")
Than this means that you should be able to use the ParaView nightly to get this fix @Sam00 :
[https://www.paraview.org/download/?version=nightly](https://www.paraview.org/download/?version=nightly)
@Sankhesh_Jhaveri @Lucas_Givord : should this MR be backported to release and paraview/release ?
---
### Author:  [@Lucas\_Givord](https://discourse.paraview.org/u/Lucas_Givord)
#### Post date: [January 30, 2024, 10:16am UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/5 "2024-01-30T10:16:16Z")
we should backport this fix
---
### Author:  [@Sam00](https://discourse.paraview.org/u/Sam00)
#### Post date: [January 30, 2024, 12:37pm UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/6 "2024-01-30T12:37:39Z")
I just got the chance to try it out, works fine!
Thank you, @Lucas_Givord and @LucasGandel for the replies.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 30, 2024, 4:29pm UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/7 "2024-01-30T16:29:13Z")
I’m afraid it cannot be backported as is, it contains deprecation, which are not acceptable in backports.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [January 31, 2024, 9:01am UTC](https://discourse.paraview.org/t/image-culling-in-xrinterface/13823/8 "2024-01-31T09:01:40Z")
The actual fix can be backported: [https://gitlab.kitware.com/vtk/vtk/-/merge\_requests/10854](https://gitlab.kitware.com/vtk/vtk/-/merge_requests/10854)