VR Mode in Blender gives Error Message #78844

New Issue

Audrie · 2020-07-12T04:11:08+02:00

Audrie commented

2020-07-12 04:11:08 +02:00

System Information
Operating system: Windows 10
Graphics card: AMD RX 560X

Blender Version
Broken: (example: 2.80, edbf15d3c0, master, 2018-11-28, as found on the splash screen) Blender 2.83.1 VR capability gives following error message: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. "Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.
Worked: (newest version of Blender that worked as expected)

Short description of error
Using Oculus Quest and Oculus Link to activate VR mode in Blender

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: Windows 10 Graphics card: AMD RX 560X **Blender Version** Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) Blender 2.83.1 VR capability gives following error message: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. "Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line. Worked: (newest version of Blender that worked as expected) **Short description of error** Using Oculus Quest and Oculus Link to activate VR mode in Blender **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).

Audrie commented

2020-07-12 04:11:08 +02:00

Added subscriber: @audrie-2

blender-admin commented

2020-07-12 04:11:08 +02:00

#95153 was marked as duplicate of this issue

Alaska commented

2020-07-12 04:48:47 +02:00

Added subscriber: @Alaska

Alaska commented

2020-07-12 04:48:47 +02:00

Are you able to try these things?

Update your graphics drivers. https://www.amd.com/en/support
Test Blender 2.83.2. https://www.blender.org/download/
Test Blender 2.90.0. https://builder.blender.org/download/

Are you able to try these things? 1. Update your graphics drivers. https://www.amd.com/en/support 2. Test Blender 2.83.2. https://www.blender.org/download/ 3. Test Blender 2.90.0. https://builder.blender.org/download/

Audrie commented

2020-07-14 23:58:02 +02:00

I have upgraded laptop to CPU: Ryzen 7; GPU: RTX2060; RAM: 16GB. I still get the same error message with the Blender 2.9 (alpha) version.

Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however.
Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.

I have upgraded laptop to CPU: Ryzen 7; GPU: RTX2060; RAM: 16GB. I still get the same error message with the Blender 2.9 (alpha) version. Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.

Audrie commented

2020-07-15 02:54:26 +02:00

blender_debug_output.txt

blender_system_info.txt

[blender_debug_output.txt](https://archive.blender.org/developer/F8694915/blender_debug_output.txt) [blender_system_info.txt](https://archive.blender.org/developer/F8694916/blender_system_info.txt)

Audrie commented

2020-07-22 05:44:58 +02:00

Hi I am still having issues getting the VR in Blender to work properly. I have followed the instructions on the Blender website and watched numerous YouTube videos. I keep getting a yellow page with an exclamation mark and then the following error message:

Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however.

Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.

Please advise why I get this message and how I can remedy the situation. Nobody seems to know why this happens. If there is possibly a step or a process I missed, please let me know.

Thanks,

Audrie

Hi I am still having issues getting the VR in Blender to work properly. I have followed the instructions on the Blender website and watched numerous YouTube videos. I keep getting a yellow page with an exclamation mark and then the following error message: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line. Please advise why I get this message and how I can remedy the situation. Nobody seems to know why this happens. If there is possibly a step or a process I missed, please let me know. Thanks, Audrie

Tina_Christine commented

2020-07-23 16:37:58 +02:00

Added subscriber: @Tina_Christine

Tina_Christine commented

2020-07-23 16:37:58 +02:00

Did you solve it?I ues oculus too.

Julian Eisel commented

2020-08-14 14:36:33 +02:00

Added subscriber: @JulianEisel

Julian Eisel commented

2020-08-14 14:36:33 +02:00

Did you try running Blender with the --debug-xr option? The output of that might be very helpful for debugging, just to know where it fails.

Did you try running Blender with the `--debug-xr` option? The output of that might be very helpful for debugging, just to know where it fails.

Julian Eisel commented

2020-09-03 12:21:36 +02:00

Changed status from 'Needs Triage' to: 'Archived'

Julian Eisel closed this issue

2020-09-03 12:21:36 +02:00

Julian Eisel self-assigned this 2020-09-03 12:21:36 +02:00

Julian Eisel commented

2020-09-03 12:21:36 +02:00

It's important that we see the output of --debug-xr.
The mentioned message is shown if xrCreateSession() fails, so the error happens in the OpenXR loader or in the OpenXR runtime (Oculus I assume) side. So we need to see which exact error xrCreateSession() reports which we can only see with --debug-xr.

The policy of our tracker is to close reports that are waiting on the reporter to give more info after a week. So I will close this for now. We can reopen it as soon as the information is there.

It's important that we see the output of `--debug-xr`. The mentioned message is shown if `xrCreateSession()` fails, so the error happens in the OpenXR loader or in the OpenXR runtime (Oculus I assume) side. So we need to see which exact error `xrCreateSession()` reports which we can only see with `--debug-xr`. The policy of our tracker is to close reports that are waiting on the reporter to give more info after a week. So I will close this for now. We can reopen it as soon as the information is there.

David Hsu commented

2022-01-22 18:23:46 +01:00

Added subscriber: @davidtriune

David Hsu commented

2022-01-22 18:23:46 +01:00

Hi, really would like this feature working, Here is the error I get. Same error as above, but with debug enabled

Available OpenXR API-layers/extensions:
Extension: XR_KHR_D3D11_enable
Extension: XR_KHR_D3D12_enable
Extension: XR_KHR_opengl_enable
Extension: XR_KHR_vulkan_enable
Extension: XR_KHR_vulkan_enable2
Extension: XR_KHR_composition_layer_depth
Extension: XR_KHR_win32_convert_performance_counter_time
Extension: XR_KHR_convert_timespec_time
Extension: XR_KHR_composition_layer_cube
Extension: XR_KHR_composition_layer_cylinder
Extension: XR_KHR_composition_layer_equirect
Extension: XR_KHR_visibility_mask
Extension: XR_KHR_composition_layer_color_scale_bias
Extension: XR_EXT_win32_appcontainer_compatible
Extension: XR_OCULUS_recenter_event
Extension: XR_FB_color_space
Extension: XR_OCULUS_ovrsession_handle
Extension: XR_OCULUS_perf_stats
Extension: XR_OCULUS_audio_device_guid
Extension: XR_EXT_debug_utils
Enabling OpenXR Extension: XR_KHR_opengl_enable
Enabling OpenXR Extension: XR_KHR_D3D11_enable
Enabling OpenXR Extension: XR_EXT_debug_utils
Connected to OpenXR runtime: Oculus (Version 1.69.0)
OpenXR Debug Message:
Completed loader terminator
OpenXR Debug Message:
Completed loader trampoline
Error: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however.
Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.
OpenXR error value: -38
OpenXR Debug Message:
Entering loader trampoline
OpenXR Debug Message:
Entering loader terminator

Hi, really would like this feature working, Here is the error I get. Same error as above, but with debug enabled Available OpenXR API-layers/extensions: Extension: XR_KHR_D3D11_enable Extension: XR_KHR_D3D12_enable Extension: XR_KHR_opengl_enable Extension: XR_KHR_vulkan_enable Extension: XR_KHR_vulkan_enable2 Extension: XR_KHR_composition_layer_depth Extension: XR_KHR_win32_convert_performance_counter_time Extension: XR_KHR_convert_timespec_time Extension: XR_KHR_composition_layer_cube Extension: XR_KHR_composition_layer_cylinder Extension: XR_KHR_composition_layer_equirect Extension: XR_KHR_visibility_mask Extension: XR_KHR_composition_layer_color_scale_bias Extension: XR_EXT_win32_appcontainer_compatible Extension: XR_OCULUS_recenter_event Extension: XR_FB_color_space Extension: XR_OCULUS_ovrsession_handle Extension: XR_OCULUS_perf_stats Extension: XR_OCULUS_audio_device_guid Extension: XR_EXT_debug_utils Enabling OpenXR Extension: XR_KHR_opengl_enable Enabling OpenXR Extension: XR_KHR_D3D11_enable Enabling OpenXR Extension: XR_EXT_debug_utils Connected to OpenXR runtime: Oculus (Version 1.69.0) OpenXR Debug Message: Completed loader terminator OpenXR Debug Message: Completed loader trampoline Error: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line. OpenXR error value: -38 OpenXR Debug Message: Entering loader trampoline OpenXR Debug Message: Entering loader terminator

Peter Kim commented

2022-01-24 10:08:36 +01:00

Added subscriber: @muxed-reality

Peter Kim commented

2022-01-24 10:08:36 +01:00

Changed status from 'Archived' to: 'Needs User Info'

Peter Kim reopened this issue

2022-01-24 10:08:36 +01:00

Peter Kim commented

2022-01-24 10:08:36 +01:00

@davidtriune Hi, are you using Oculus Quest/Quest 2 + Link?
If so, what software version is it running?
https://support.oculus.com/articles/getting-started/getting-started-with-quest-2/update-software-quest/

@davidtriune Hi, are you using Oculus Quest/Quest 2 + Link? If so, what software version is it running? https://support.oculus.com/articles/getting-started/getting-started-with-quest-2/update-software-quest/

Peter Kim commented

2022-01-24 10:09:03 +01:00

Added subscriber: @Dimitar

David Hsu commented

2022-01-24 10:51:50 +01:00

I'm using CV1 (not sure if model is too old)
App version 37.0.0.79.109 , not sure how to check the firmware version, but i updated everything
actually just bought the quest 2, going to try it on there once it arrives

I'm using CV1 (not sure if model is too old) App version 37.0.0.79.109 , not sure how to check the firmware version, but i updated everything actually just bought the quest 2, going to try it on there once it arrives

Patrick commented

2022-01-24 22:04:37 +01:00

Added subscriber: @pwcb

Patrick commented

2022-01-24 22:04:37 +01:00

I'm getting the exact same debug message (error 38) in Blender 3.0 using both a CV1 and Quest 2. Quest 2 has the same results via Air Link and regular Link, on Oculus versions 1.67 and 1.69 after enabling "Public Test Channel". The Quest 2 itself has no updates available, software version 21985310426300000.

Operating System
- Windows 10 Home 64-bit
CPU
- AMD Ryzen 9 3900X
RAM
- 32.0GB
Motherboard
- ASUSTeK COMPUTER INC. TUF GAMING X570-PLUS (AM4)
Graphics
- 4095MB NVIDIA GeForce RTX 3060 (PNY)
- 2047MB NVIDIA GeForce RTX 2060 (EVGA)

I'm getting the exact same debug message (error 38) in Blender 3.0 using both a CV1 and Quest 2. Quest 2 has the same results via Air Link and regular Link, on Oculus versions 1.67 and 1.69 after enabling "Public Test Channel". The Quest 2 itself has no updates available, software version 21985310426300000. Operating System - Windows 10 Home 64-bit CPU - AMD Ryzen 9 3900X RAM - 32.0GB Motherboard - ASUSTeK COMPUTER INC. TUF GAMING X570-PLUS (AM4) Graphics - 4095MB NVIDIA GeForce RTX 3060 (PNY) - 2047MB NVIDIA GeForce RTX 2060 (EVGA)

David Hsu commented

2022-01-25 23:05:59 +01:00

Found it, oculus version 1.69.0, firmware version 709/b1ae4f61ae for my CV1,
also just got my quest 2 and got the same error on it. software version 339081052
Tried on 2 GPUS: GTX 1080TI and RTX 2070
CPU: Intel Core i5-8600k
graphics driver 511.23

Found it, oculus version 1.69.0, firmware version 709/b1ae4f61ae for my CV1, also just got my quest 2 and got the same error on it. software version 339081052 Tried on 2 GPUS: GTX 1080TI and RTX 2070 CPU: Intel Core i5-8600k graphics driver 511.23

David Hsu commented

2022-01-30 06:19:13 +01:00

i dont know what happened, but it works all of a sudden. maybe it was the oculus update?
i'm super happy :)
blender xr works too. are you the same guys working on that? wouldve loved to sculpt in it, but its very buggy and crashes often (2 axes are inverted for grab tool). I suggest enabling mouse/keyboard and normal UI and use them as you would on a desktop.
Hope this gets improved!

i dont know what happened, but it works all of a sudden. maybe it was the oculus update? i'm super happy :) blender xr works too. are you the same guys working on that? wouldve loved to sculpt in it, but its very buggy and crashes often (2 axes are inverted for grab tool). I suggest enabling mouse/keyboard and normal UI and use them as you would on a desktop. Hope this gets improved!

Dimitar P. commented

2022-01-30 11:10:10 +01:00

Sadly, I cannot report the same success. Oculus Quest 2 has been updated to 37.0.147, and the Software is Oculus on the desktop v 37.0.0.79.109 but I still get the same error with Blender 3.0.1:

System Information
Operating system: Windows-10-10.0.19044-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09

Blender Version
Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: dc2d180181

Console output when trying to start VR session via Blender_oculus.cmd with --factory-startup and --debug-xr:

Available OpenXR API-layers/extensions:
Extension: XR_KHR_D3D11_enable
Extension: XR_KHR_D3D12_enable
Extension: XR_KHR_opengl_enable
Extension: XR_KHR_vulkan_enable
Extension: XR_KHR_vulkan_enable2
Extension: XR_KHR_composition_layer_depth
Extension: XR_KHR_win32_convert_performance_counter_time
Extension: XR_KHR_convert_timespec_time
Extension: XR_KHR_composition_layer_cube
Extension: XR_KHR_composition_layer_cylinder
Extension: XR_KHR_composition_layer_equirect
Extension: XR_KHR_visibility_mask
Extension: XR_KHR_composition_layer_color_scale_bias
Extension: XR_EXT_win32_appcontainer_compatible
Extension: XR_OCULUS_recenter_event
Extension: XR_FB_color_space
Extension: XR_OCULUS_ovrsession_handle
Extension: XR_OCULUS_perf_stats
Extension: XR_OCULUS_audio_device_guid
Extension: XR_EXT_debug_utils
Enabling OpenXR Extension: XR_KHR_opengl_enable
Enabling OpenXR Extension: XR_KHR_D3D11_enable
Enabling OpenXR Extension: XR_EXT_debug_utils
Connected to OpenXR runtime: Oculus (Version 1.69.0)
OpenXR Debug Message:
Completed loader terminator
OpenXR Debug Message:
Completed loader trampoline
Error:  Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however.
Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line.
        OpenXR error value: -38
OpenXR Debug Message:
Entering loader trampoline
OpenXR Debug Message:
Entering loader terminator

Sadly, I cannot report the same success. Oculus Quest 2 has been updated to 37.0.147, and the Software is Oculus on the desktop v 37.0.0.79.109 but I still get the same error with Blender 3.0.1: **System Information** Operating system: Windows-10-10.0.19044-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 2080 SUPER/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.09 **Blender Version** Broken: version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `dc2d180181` Console output when trying to start VR session via Blender_oculus.cmd with `--factory-startup` and `--debug-xr`: ``` Available OpenXR API-layers/extensions: Extension: XR_KHR_D3D11_enable Extension: XR_KHR_D3D12_enable Extension: XR_KHR_opengl_enable Extension: XR_KHR_vulkan_enable Extension: XR_KHR_vulkan_enable2 Extension: XR_KHR_composition_layer_depth Extension: XR_KHR_win32_convert_performance_counter_time Extension: XR_KHR_convert_timespec_time Extension: XR_KHR_composition_layer_cube Extension: XR_KHR_composition_layer_cylinder Extension: XR_KHR_composition_layer_equirect Extension: XR_KHR_visibility_mask Extension: XR_KHR_composition_layer_color_scale_bias Extension: XR_EXT_win32_appcontainer_compatible Extension: XR_OCULUS_recenter_event Extension: XR_FB_color_space Extension: XR_OCULUS_ovrsession_handle Extension: XR_OCULUS_perf_stats Extension: XR_OCULUS_audio_device_guid Extension: XR_EXT_debug_utils Enabling OpenXR Extension: XR_KHR_opengl_enable Enabling OpenXR Extension: XR_KHR_D3D11_enable Enabling OpenXR Extension: XR_EXT_debug_utils Connected to OpenXR runtime: Oculus (Version 1.69.0) OpenXR Debug Message: Completed loader terminator OpenXR Debug Message: Completed loader trampoline Error: Failed to create VR session. The OpenXR runtime may have additional requirements for the graphics driver that are not met. Other causes are possible too however. Tip: The --debug-xr command line option for Blender might allow the runtime to output detailed error information to the command line. OpenXR error value: -38 OpenXR Debug Message: Entering loader trampoline OpenXR Debug Message: Entering loader terminator ```

David Hsu commented

2022-01-31 01:27:38 +01:00

I haven't done anything except install the new oculus firmware that came out a few days ago.
i even tried it on my laptop, and it works on there. it doesn't even have the latest geforce drivers.
be sure to run from "blender_oculus.cmd". running blender 3.0.0.
version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557, type: release

I haven't done anything except install the new oculus firmware that came out a few days ago. i even tried it on my laptop, and it works on there. it doesn't even have the latest geforce drivers. be sure to run from "blender_oculus.cmd". running blender 3.0.0. version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca3055776, type: release

Peter Kim commented

2022-02-01 08:12:24 +01:00

Re-tested with the latest Quest 2 and Oculus app updates but still can't reproduce the error unfortunately.

System Information
Operating system: Windows-10-10.0.19043-SP0 64 Bits
Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23
Oculus PC app version: 37.0.0.79.109
Oculus Quest 2 version: 37.0.0.147.109
Oculus OpenXR runtime version: 1.69

Blender Version
version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: f1cca30557
version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: dc2d180181
version: 3.2.0 Alpha, branch: master, commit date: 2022-01-31 23:10, hash: 95005bbe02

@Dimitar @pwcb As another option, have you tried using SteamVR?
https://docs.blender.org/manual/en/latest/getting_started/configuration/hardware.html#steamvr

Re-tested with the latest Quest 2 and Oculus app updates but still can't reproduce the error unfortunately. System Information Operating system: Windows-10-10.0.19043-SP0 64 Bits Graphics card: NVIDIA GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 511.23 Oculus PC app version: 37.0.0.79.109 Oculus Quest 2 version: 37.0.0.147.109 Oculus OpenXR runtime version: 1.69 Blender Version version: 3.0.0, branch: master, commit date: 2021-12-02 18:35, hash: `f1cca30557` version: 3.0.1, branch: master, commit date: 2022-01-25 17:19, hash: `dc2d180181` version: 3.2.0 Alpha, branch: master, commit date: 2022-01-31 23:10, hash: `95005bbe02` @Dimitar @pwcb As another option, have you tried using SteamVR? https://docs.blender.org/manual/en/latest/getting_started/configuration/hardware.html#steamvr

Patrick commented

2022-02-02 09:22:25 +01:00

Ok, so I got it to actually start after setting up SteamVR and making it the OpenXR runtime, but it's only showing pink on the headset. Maybe the same issue here , but maybe not because I'm using a Nvidia GPU. Debugger spits out "Error: Framebuffer for shared DirectX-OpenGL resource incomplete 36054" nonstop while running the VR session, but I did notice everything is tracking correctly with the hmd/controllers in the normal viewport.

That's all in 3.0.1, running in 3.0.2 gives the same result in the debugger but does manage to display the "next up" title card on the SteamVR home screen at a low framerate instead of a pink screen.

I hope some of this is useful, the results seem so random from person to person

Ok, so I got it to actually start after setting up SteamVR and making it the OpenXR runtime, but it's only showing pink on the headset. Maybe the same issue [here ](https://developer.blender.org/T76082), but maybe not because I'm using a Nvidia GPU. Debugger spits out "Error: Framebuffer for shared DirectX-OpenGL resource incomplete 36054" nonstop while running the VR session, but I did notice everything is tracking correctly with the hmd/controllers in the normal viewport. That's all in 3.0.1, running in 3.0.2 gives the same result in the debugger but does manage to display the "next up" title card on the SteamVR home screen at a low framerate instead of a pink screen. I hope some of this is useful, the results seem so random from person to person

David Hsu commented

2022-02-13 02:55:31 +01:00

i think i found out how i fixed mine. I assume oculus only runs on the gpu that your monitor is connected to. my primary monitor was connected to my GTX 1080 ti, and it showed the error. When I switched monitor to my GTX 2080, it worked. So it seems like the plugin is only compatible with certain graphics cards. If you have multiple gpus, try connecting your monitor to each one, restart pc, and try again. good luck.

Peter Kim commented

2022-02-17 09:16:01 +01:00

@pwcb Thanks for the information. The pink screen issue should be fixed now with dd6fd06c15 and the fix will be included in the upcoming Blender 3.1 release.
If you would like to try it out before then, you can download the next 3.1 beta or 3.2 alpha daily build:
https://builder.blender.org/download/daily/

@pwcb Thanks for the information. The pink screen issue should be fixed now with dd6fd06c15 and the fix will be included in the upcoming Blender 3.1 release. If you would like to try it out before then, you can download the next 3.1 beta or 3.2 alpha daily build: https://builder.blender.org/download/daily/

Pratik Borhade changed title from ~~VR Mode in Blender 2.83.1 Gives Error Message~~ to VR Mode in Blender gives Error Message

2022-06-08 12:22:17 +02:00

Philipp Oeser commented

2023-04-05 09:45:07 +02:00

Is this considered resolved now?