VR_Init gets stuck with Pico 4 headset

[DouglasCBO]

I have developed my own openvr application that works fine with HTC Vive and Quest 2 headsets. However, I recently have acquired a Pico 4 headset and the app gets stuck on the initialization.

Debugging the application I have found the VR_Init function is waiting forever for a conecction with the vrserver.

Logs:

vrclient type=VRApplication_Scene
Fri Jan 27 2023 17:50:57.735 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\htc\resources\settings\default.vrsettings
Fri Jan 27 2023 17:50:57.735 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\lighthouse\resources\settings\default.vrsettings
Fri Jan 27 2023 17:50:57.735 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\drivers\null\resources\settings\default.vrsettings

Fri Jan 27 2023 17:50:57.736 - [Settings] Load Default Json Settings from C:\Program Files\Streaming Assistant\driver\resources\settings\default.vrsettings

Fri Jan 27 2023 17:50:57.736 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\iVRy\resources\settings\default.vrsettings
Fri Jan 27 2023 17:50:57.736 - [Settings] Load Default Json Settings from C:\Program Files (x86)\Steam\steamapps\common\SteamVR\resources\settings\default.vrsettings
Fri Jan 27 2023 17:50:57.737 - [Settings] Load Json Settings from C:\Program Files (x86)\Steam\config\steamvr.vrsettings
Fri Jan 27 2023 17:50:58.747 - WaitNamedPipe SteamVR_Namespace failed because The semaphore timeout has expired.
 (121)
Fri Jan 27 2023 17:50:58.747 - Starting vrserver process: C:\Program Files (x86)\Steam\steamapps\common\SteamVR\bin\win64\vrserver.exe
"cadvr_opengl_d.exe" (Win32): Carregado "C:\Windows\System32\apphelp.dll". 
Fri Jan 27 2023 17:50:59.756 - WaitNamedPipe SteamVR_Namespace failed because The semaphore timeout has expired.
 (121)

Fri Jan 27 2023 17:50:59.756 - CSharedResourceNamespaceClient::Init(): failed connect
Fri Jan 27 2023 17:50:59.756 - CSharedResourceNamespaceClient::Init(): still waiting for vrserver to reply with namespace data
Fri Jan 27 2023 17:51:00.857 - WaitNamedPipe SteamVR_Namespace failed because The semaphore timeout has expired.
 (121)

These last three entries keep repeting forever.

Someone knows if there is a way (some configuration, a driver etc) to make this to work?

[SorenMuller]

Hi, Got the same error here.. Did you find any solution to it.. ??

[DouglasCBO]

Hi,

I have not found a solution yet. I'm still waiting for an answer here.

Let me know if you fix this, please.

[esi-jwr]

Hey everyone,

I see this exact behaviour in cases where an "Administrator" account is used (the actual account, does not happen on just any account added to the Administrators group. Even with no configuration in SteamVR active (no hmd connected), and irregardless of hardware - it basically sits there, waiting for the timeout on WaitNamedPipe, blocking the vrclient.

I can also reproduce the same behavior on a Windows Server install, and it does affect other account types there. Investigating I do see a couple very similar posts strewn across the internet (including NVIDIA's own forums on CloudXR) but no actual reason/solution.

It appears to be something the client is doing, as simple(r) vrclients like steamtours or the tutorial just work regularly.

Best regards, Jan