search

KitwareMedical / SlicerVirtualReality

A Slicer extension that enables user to interact with a Slicer scene using virtual reality.
Apache License 2.0
111 stars 56 forks source link

VR_Init FailedUnable to init VR runtime: Interface Not Found (105) #77

Closed chene77 closed 4 years ago

chene77 commented 4 years ago

hi,

In the last few nightly (Oct 02/05/07) the SlicerVirtualReality is unable to connect to the steamVR.

When clicking on "connect to hardware", I get "connection failed" in red. The debug/warning message says:

Switch to module: "VirtualReality" this->DisplayableManagerGroup 8 VR_Init FailedUnable to init VR runtime: Interface Not Found (105)

Failed to initialize OpenVR RenderWindow

the last line is a warning from QT. the second last line is an error message from VTK

The same hardware work just fine in the stale (4.10.2)

adamrankin commented 4 years ago

When the hardware worked for stable, was on the same boot? Aka, you didn't reboot between tries?

adamrankin commented 4 years ago

I just downloaded the latest nightly and installed SlicerVR and it worked first try with Samsung HMD.

chene77 commented 4 years ago

On the same boot, no reboot. Using HTC VIVE Pro

Sent from Mail for Windows 10

From: Adam Rankin Sent: October 9, 2019 10:31 AM To: KitwareMedical/SlicerVirtualReality Cc: Elvis Chen; Author Subject: Re: [KitwareMedical/SlicerVirtualReality] VR_Init FailedUnable toinit VR runtime: Interface Not Found (105) (#77)

When the hardware worked for stable, was on the same boot? Aka, you didn't reboot between tries? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

adamrankin commented 4 years ago

Do you have a reliable repro setup? If so, when you get back I can investigate.

On Thu, Oct 10, 2019 at 9:35 AM Elvis Chen notifications@github.com wrote:

On the same boot, no reboot. Using HTC VIVE Pro

Sent from Mail for Windows 10

From: Adam Rankin Sent: October 9, 2019 10:31 AM To: KitwareMedical/SlicerVirtualReality Cc: Elvis Chen; Author Subject: Re: [KitwareMedical/SlicerVirtualReality] VR_Init FailedUnable toinit VR runtime: Interface Not Found (105) (#77)

When the hardware worked for stable, was on the same boot? Aka, you didn't reboot between tries? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/KitwareMedical/SlicerVirtualReality/issues/77?email_source=notifications&email_token=AAYPZHVYCWKBJUWNTE4VL6TQN4VS5A5CNFSM4I6ZNNZKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEA4K3AI#issuecomment-540585345, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAYPZHRDYFTSL7MORS3NAVDQN4VS5ANCNFSM4I6ZNNZA .

lassoan commented 4 years ago

This is probably because you updated SteamVR and it is no more compatible with the OpenVR SDK that SlicerVirtualReality extension is built with.

@cpinter mentioned that he had to update OpenVR DLLs on his system manually. Probably he will push a fix soon.

cpinter commented 4 years ago

Indeed. Please hang on, I'll update OpenVR asap.

cpinter commented 4 years ago

I updated OpenVR and tested it successfully with a recent Slicer (28534). Please try it tomorrow with the nightly preview.

cpinter commented 4 years ago

Any news about this? It seems to work now, so I'm going to close the issue unless there are further comments.

lassoan commented 4 years ago

Unfortunately, it did not work for SlicerHeart group. Have you tested the factory-built extension?

cpinter commented 4 years ago

I only tested it with what I built. Have you?

lassoan commented 4 years ago

Hanna at CHOP tested it and wrote this:

I don't think this is working yet.

I downloaded the latest release of Slicer (10/17 version) and updated Steam. I downloaded the Slicer VR module successfully, but after trying to start VR I see a red "X" on the icon.

This is the error message in Slicer:

vtkObject (0000017192789190): This OpenGL implementation does not support the required texture size of 262144. Falling back to maximum allowed, 32768.This may cause an incorrect color table mapping.

this->DisplayableManagerGroup 8
VR_Init FailedUnable to init VR runtime: Interface Not Found (105)

Failed to initialize OpenVR RenderWindow
Warning: In d:\d\p\slicer-0-build\vtk\rendering\volumeopengl2\vtkOpenGLVolumeOpacityTable.h, line 191
vtkObject (0000017299AF1770): This OpenGL implementation does not support the required texture size of 262144. Falling back to maximum allowed, 32768.This may cause an incorrect color table mapping.

Is there anything else we are supposed to download/update for this?

Thank you.

cpinter commented 4 years ago

Not sure what this has to do with VR, it seems like a generic OpenGL error. Of course the fact that VR does not work and this error shows up just when trying to start it means that there is connection. I'll try it on Monday with a nightly install.

What is the data they want to visualize? Anything new or bigger than before, or just the usual?

lassoan commented 4 years ago

It is just the usual rendering, which worked before. Quite small volumes. We should test on more computers tomorrow, with the factory-built release.

cpinter commented 4 years ago

I tried the latest nightly that has SlicerVR (yesterday the Windows extension builds failed), and it works for me. I used an Acer WMR headset.

I noticed in the past that sometimes if Slicer started SteamVR, then it did not work and needed to restart Slicer (having an up and running SteamVR) to make it connect properly. Maybe they could try that.

cpinter commented 4 years ago

@lassoan says the issue at CHOP was a missing SteamVR update due to the hospital firewall, and now it works. @chene77 does not reply so I assume it works for him as well. I'm closing the issue.