Evan Heinrich

@Janyse

Sorry for the delayed reply. I was able to launch Minecraft through the Oculus Library w/ the official app and that is what I used when I tested it.

Can confirm Kane's temporary fix. Moving the DX11 DLL files he mentioned into a temporary file allowed the game to render RTX properly and not be a blackscreen.

This issue occurred for me after I updated my GPU drivers to 466.27

System specs:
RTX 2070 Super
Ryzen 5 3600
16 GB 3200MHz CL16 

When I tested Minecraft for myself, I didn't run it long enough to determine if there was a memory leak, but after reading some other comments, I might test again and monitor memory usage.

Also since an Xbox controller seems to be working for you, I do believe that the issue with knuckles is related to how Steam handles/adapts the controllers for Minecraft. Sorry I can't offer much more insight but at least for now an Xbox controller will work, assuming they fix that memory leak.

*EDIT*

My minecraft version is v1.16.221
Windows 10 Version 20H2 build number 19042.685
Oculus app version 28.0.0.222.469

I did not observe a memory leak or any increased memory usage while leaving me headset running and Minecraft VR streaming over Air Link.

Just out of curiosity Logan, does it work for you with a generic controller, like an Xbox controller? If so, that would lead me to believe it's an issue with how SteamVR and Minecraft UWP communicate in regards to the knuckles. The regular Oculus controllers worked fine for me so I don't know if it's because they're knuckles or if the game is having issues with outside-in tracking

The most recent update has fixed the issue for me at least. I decided to re-try using the Bedrock edition of Minecraft for VR since oculus launched Air Link, and after reinstalling the Oculus PC software and the Oculus store Minecraft launcher thing, the game launched properly. One thing I did notice was that the Oculus store Minecraft launcher closed itself shortly after opening, but then Minecraft UWP loaded and worked flawlessly.

I have a 64GB model of the Quest 2 headset, and as mentioned I was using Air Link.

PC Specs:

Ryzen 5 3600

16GB DDR4 3400 MHz RAM

RTX 2070 Super GPU

I don't have the windows 10 version on hand, but if enough people are curious, I can edit this comment with the version numbers for the Quest 2 system update version, Oculus PC app version, windows 10 version and stuff.

@Gerod

Minecraft VR was first developed for Windows Mixed Reality, so it should still be supported, but seeing your previous posts, you probably just have to find the default Windows MR runtime.

C:\WINDOWS\system32\MixedRealityRuntime.json should the the location

@Gerod
If you already know what the registry is, this should be easy to explain. Basically, there are a few different ways to handle VR applications, and Minecraft recently added support for the "OpenXR" runtime. Some people's registries haven't updated or are pointing to the wrong area for their specific headset. Some people were saying theirs were pointing to a Windows Mixed Reality runtime when they didn't have that kind of headset. So what you basically do is tell your system where the correct runtime is for VR; and for the case of Oculus, their runtime came with their game store program. I would assume it's a similar fix for SteamVR. Again, this is an assumption, but the Oculus store version of "Minecraft" seemed to be some sort of adapter between Minecraft's previous runtime and the runtime Oculus uses, which is my guess as to why it is broken now but some people can get it to run without the Oculus store version installed.

I tried a clean install of Windows 10 and all the other software, and it did not help. Still the same issue as people above.

I am using a Oculus Quest 2 VR headset over Oculus Link to play PC games.

Windows 10 version 20H2 / build 19042.685

CPU: Ryzen 5 3600

GPU: RTX 2070 Super

RAM: 16GB 3400MHz

Steps for recreation of the issue:

1. Reinstall windows after formatting drive

2. Install appropriate drivers for computer hardware

3. Download and install the Oculus software/store to use the Oculus Link

4. Install Minecraft Bedrock edition from the Microsoft store

5. Download the Minecraft launcher from the Oculus store

6. Connect Oculus Quest 2 over USB type C and enable Oculus Link

7. Go to my game library and attempt to launch Minecraft using the app downloaded from the Oculus store

The app then displays a VR view of "Checking for updates..." then after a few seconds, the app seemingly crashes or I get returned to the Oculus Link home. When I look on my PC, however, the game is started in 2D mode.

I then tried the OpenXR registry fix people above have mentioned, and it did somewhat work. I uninstalled the Minecraft launcher from the Oculus store AND the bedrock edition from the minecraft store. I applied the registry edit to point to the Oculus OpenXR json file, and then reinstalled first the windows store version of minecraft followed by the oculus store launcher. When I then went to launch the game from Oculus link, it stayed a bit longer on the "checking for updates" screen before turning completely black and then loading me into Minecraft in VR. I did not have to launch the game using the OpenXR shortcut people have mentioned earlier, and simply changing the registry value for OpenXR allowed the game to load when launching from the Oculus Link home.

It also might be worthwhile to mention that I had not installed Steam or SteamVR at all when I clean installed windows 10, just the oculus store and minecraft bedrock from the windows store.

While I was able to get into the game after applying the registry fix, there were a few issues I was having. Looking around normally with the headset in VR was smooth, but as soon as I had to use the thumbsticks to move around or look around the world I was testing with, the game started stuttering really bad.

HMD: Oculus Quest 2 (EDIT: using a link cable, not wireless virtual desktop)

System: RTX 2070 Super / Ryzen 5 3600 / 16GB RAM / Windows 10 2020H2 19042.685

Doing the registry edit to the oculus openXR library worked for me, but I only tested launching using the minecraft://mode/?OpenXR=true shortcut.

It seems I am having the same issue as some other people where the game is at a fixed 60fps or something.

I uninstalled the oculus store version of minecraft and now am only using the windows 10 edition with that aforementioned shortcut.

While yes it does work, like Richard Johnson said it isn't polished at all, and worked a LOT better before the shift to openXR. Hopefully mojang or whoever handles the openXR implementation more or less fixes it sometime soon.