Forum Discussion
LogHMD: Error: Failed to load a depth texture frame description for the left eye.
My packaged Unreal build for the Quest 3 will not start and stays at the Unreal Editor splash screen. I dumped the log and saw the title of this post dozens and dozens of times in said log file:
[2024.08.03-01.35.34:788][399]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:790][399]LogShaderLibrary: Warning: Spent 4.39 ms in a blocking wait for shader preload, NumRefs: 2, FramePreloadStarted: 2686, CurrentFrame: 2686
[2024.08.03-01.35.34:803][400]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:846][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:846][401]LogSVRLoadScreen: Display: BlockTick delta: 0.11 seconds. Current elapsed load screen time: 4.35
[2024.08.03-01.35.34:858][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:864][401]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:881][404]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
[2024.08.03-01.35.34:881][404]LogHMD: Error: Failed to load a depth texture frame description for the left eye.
...and on and on. The error seems to be linked to a custom node that uses the return ResolvedView.StereoPassIndex; command in order to adjust an effect per-eye. When I remove the node, the game starts properly. Everything runs fine in PIE, no troubles at all.
I've never run into this error before on other projects, yet this particular one is plagued by it. What could the problem be?
1 Reply
Replies have been turned off for this discussion
My app runs fine, but the log is filled with those depth texture frame description errors, both in the editor when running VR PIE and in packaged builds for Quest 3.
I don't think this error is related to your app not launching.
This error might be related to some option in project settings.
