We have a problem where our Unity application (built, not in-editor) frequently hangs on startup, very early in the start-up process. Looking at the logs, it seems to hang indefinitely right after the first XR initialization log message came through. After enough system restarts and replugging the Pico 4 Enterprise link cable it usually starts magically working again, until it doesn’t.
Some information about our setup:
- Unity version 2022.3.4f1
- OpenXR Plugin version 1.8.2
- Using the Pico 4 Enterprise, which uses SteamVR for its OpenXR runtime
- SteamVR version 1.27.5
- Reproduced on a variety of systems with GPU’s ranging from 10 to 40 series NVIDIA, different generation Intel processors, and RAM up to 16GB (RAM usage does not seem to be a problem, looking at task manager)
- I attached a SteamVR System Report from one of the systems where the problem was reproduced.
Full Unity logs:
Mono path[0] = ‘C:/CleVR/SocialWorlds/CleVR.SocialWorlds.Unity_Data/Managed’
Mono config path = ‘C:/CleVR/SocialWorlds/MonoBleedingEdge/etc’
The command-line parameter ‘adapter’ has been removed. Please use ‘monitor’ instead.
Initialize engine version: 2022.3.4f1 (35713cd46cd7)
[Subsystems] Discovering subsystems at path C:/CleVR/SocialWorlds/CleVR.SocialWorlds.Unity_Data/UnitySubsystems
[Subsystems] No descriptors matched for examples in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json.
[Subsystems] 1 ‘inputs’ descriptors matched in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json
[Subsystems] 1 ‘displays’ descriptors matched in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json
[Subsystems] No descriptors matched for meshings in UnitySubsystems/UnityOpenXR/UnitySubsystemsManifest.json.
GfxDevice: creating device client; threaded=1; jobified=1
[XR] [9764] [15:12:44.456][Info ] Available Layers: (0)
Let me know what other pieces of information could be helpful, any help would be greatly appreciated.
9391070–1313774–SteamVR-2023-10-05-PM_04_36_46.txt (3.66 MB)