OpenXR breaks get_rendering_device and create_local_rendering_device

[vrtood]

Tested versions

Reproducible in: Redot 26.2 beta 1, and above (this is the first one where the issue can be reproduced){v26.2.beta.1.official [5b6b4ff]}

Not reproducible in: 26.1.stable, and below

System information

liunx-CachyOS, Vulkan, NVIDIA GeForce RTX 3060 Lite Hash Rate , Intel(R) Core(TM) i7-10700F

Issue description

in forward+ and mobile renderer
.get_rendering_device() and .create_local_rendering_device()
gives null when OpenXR is enabled

Steps to reproduce

open a project in 26.2-beta.1 or above
enable OpenXR in Project Settings
make a script with:

extends Node

var rd: RenderingDevice

func _ready():
rd = RenderingServer.get_rendering_device()
prints("rd get_rendering_device is",rd)
rd = RenderingServer.create_local_rendering_device()
prints("rd create_local_rendering_device is",rd)

Minimal reproduction project (MRP)

OpenXR_bug.zip

[Arctis-Fireblight]

Hi vrtood,

Thanks for reporting this regression!
Would you potentially be willing to help bisect this to help locate the offending commit that caused the problem?
Normally I would perform this step myself, but I don't really have any VR hardware for testing.

If you are comfortable compiling from source, I would be more than happy to walk you through it.

[vrtood]

tl;dr{

488f299 is the first 'bad' commit
commit 488f299 (HEAD)
Author: Jon <14169426+JoltedJon@users.noreply.github.com>
Date:   Sun Mar 8 09:59:44 2026 -0400

   GH-674 Check if Vulkan is supported before attempting to Initialize (#1205)
    
    GH-674 Check if Vulkan is supported before attempting to Initialize
    
    GH-674 Add Vulk ifdef since macos/ios use functions while linux uses function pointers
    
   * GH-674 Add CodeRabbit Suggested Changes

drivers/vulkan/rendering_context_driver_vulkan.cpp | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---
drivers/vulkan/rendering_context_driver_vulkan.h   |  1 +
2 files changed, 62 insertions(+), 3 deletions(-)

}

———————————————

I'll be happy to help!
but I never compiled from source before
So I did a little searching
I had read https://docs.redotengine.org/contributing/development/compiling/compiling_for_linuxbsd
and installed the Requirements.
asked AI how to compile, and then got recommended git bisect and how to use it.
and then I got this 488f299

Hope this helps!

side notes:

Critical -- { in https://docs.redotengine.org/contributing/development/compiling/compiling_for_linuxbsd in Requirements
there is PulseAudio I installed that, and then the audio stopped working in my system.
If AI did not help me, I would have had to reinstall CachyOS
here is what I did to fix that (if anybody has the same problem )

systemctl --user enable --now pipewire pipewire-pulse wireplumber

systemctl --user restart pipewire pipewire-pulse wireplumber

sudo pacman -Syy plasma-pa

kquitapp6 plasmashell && kstart plasmashell &

sudo pacman -S lib32-pipewire lib32-libpulse lib32-alsa-plugins pipewire-alsa

then restart the pc } --
—————————————
On LinkedIn, the website links to the old banned Twitter account
In https://www.redotengine.org/community ReX is still there at the bottom

[Arctis-Fireblight]

Thanks for Bisecting that!
Looks like it is related to the Vulkan check, so that narrows it down. Should help us debug the issue.

We'll also look into getting the docs updated for use on pipewire only systems like CachyOS.

[JoltedJon]

Whoops didn't see this. I'll see if I can get this fixed soon:tm:
Thanks @GeneralProtectionFault for reminding me

[JoltedJon]

Hi @vrtood Can you give my PR a test when you get time? You can download the redot executable produced by the PR by going to the PR click "checks" at the top of the PR then scrolling down to artifacts at the bottom.

[vrtood]

Yup, I gave it a test, and everything works!