# OpenVR problems with VTK 9.2

**URL:** https://discourse.vtk.org/t/openvr-problems-with-vtk-9-2/10992
**Category:** VR/AR
**Created:** [March 16, 2023, 2:44pm UTC](https://discourse.vtk.org/t/openvr-problems-with-vtk-9-2/10992 "2023-03-16T14:44:10Z")
**Posts on this page:** 1
**Showing post:** 19

<div class="post-metadata">

### Author: ![LucasGandel](https://discourse.vtk.org/user_avatar/discourse.vtk.org/lucasgandel/32/1831_2.png) [@LucasGandel](https://discourse.vtk.org/u/LucasGandel)
#### Post date: [March 30, 2023, 9:50am UTC](https://discourse.vtk.org/t/openvr-problems-with-vtk-9-2/10992/19 "2023-03-30T09:50:29Z")

</div>

> [@codeling](#):
>
> Do you have an idea how a more permanent fix of this might look like?

TBH I have no idea, the code was there in tests since the 1st commit that introduced OpenVR support in VTK (see [here](https://gitlab.kitware.com/vtk/vtk/-/blame/master/Rendering/OpenVR/Testing/Cxx/TestOpenVRInteractiveDragon.cxx#L61)).  
Maybe using `vtkCameraActor`/`vtkFrustumSource` could help to confirm that the camera frustum planes are computed correctly for the VR camera.

---

_[View the full topic](https://discourse.vtk.org/t/openvr-problems-with-vtk-9-2/10992)._