G

Update, the solution does make it better however teleporting back and forth especially on the map will still cause some issues

Im also having this issue aswell with a 33 by 33 map with more than 1000 individual maps. I think around a 300 map (17x17) limit is what the shaders can handle for survival. But i found out if you are in creative and you set your chunks with the map in it to be always loaded with the /tickingarea command it'll fix the issue.

Confirming that the API returns the JSON result incorrectly ordered, thus this is not a problem with the UI. Requesting from the API with the following (default) parameters:

pageSize=24&sortType=Recent&category=News&newsOnly=true

Returns articles with epoch timestamps 1721156915 (Tuesday, 16 July 2024 19:08:35), 1721133145 (Tuesday, 16 July 2024 12:32:25), 1721077945 (Monday, 15 July 2024 21:12:25) and so on.

Nope.  Almost 18 months. Still broken for WMR

Okay, I can live with it.
The reason why I left the Beta simply was to play with my friends who play on Switch because they can´t go into the Beta versions.
I hoped that I could join the world again in 1.17/1.18 (which worked), but I forgot, that Betas aren´t complete and some features can be deleted or changed.
I´ll try to fix the world corruption. 🙂

Yes, it had Caves&Cliffs Toggle enabled.

Please STOP saying that this is somehow fixed.  This is still a major issue and at the core the comments we are trying to get mojang to pay attention to is BEDROCK VR WILL NOT WORK IN WINDOWS MIXED REALITY! Cheers.

Can anyone confirm if 1.16.220 fixed our VR issues? I apparently cannot leave the beta (another problem) so I cannot test the release. Feedback?

I confirm beta 1.16.230.52 launched via windows MR clifhouse goes to black screen.  You can hear music of the main screen but no image.  Also, multiple reloads does not always play music. There is always a black screen now, no crash to launcher ...I guess we call that progress?

Anyone try the beta program?

Going on 4 months. 4 updates. And still Mojang refuses to even ACKNOWLEDGE that the issue exists.  I'm paying for a game and a realm I cannot use with a computer I purchased only 2 months before for the explicit purpose to continue to play Minecraft in VR after Mojang canceled my Gear VR option. MOJANG!!!

Anyone interested in joining a class action lawsuit for false advertising? Can everyone still unable to get VR to work after 1.16.210 and 4 months of complaining repost?  Need a recount of affected, their headset brand/model and platform (WMR, Oculus,  Steam)

Can anyone else confirm this is true. I haven't had a chance to download. But it's not mentioned in the release notes. 

☝This

I wish everyone would stop saying that it works by reg hacking the pointer to the "correct" runtime for Oculus.  BL: this is a hard-broke bug for Windows Mixed Reality.  I don't care about the rest (Steam/Oculus) because that's not what is broken.  Not my fault that Mojang keeps grouping us together.  Happy for every Facebook fan-boy out there who loves to use Rift but vanilla Minecraft worked fine in vanilla WMR until the 1.16.200 failed update.  This is the bug that has no fix.

Daniel, fine idea but CPU and GPU won't be the issues.  We already know these are two dissimilar issues. We know the issues started with .200 and the introduction of OpenXR. Different headsets = different runtimes (Oculus vs WMR). That's the difference. The problem is a slovenly Mojang.

I have a used Dell Optiplex 3060 slim (i5 with only on-board Intel UHD 630) which i got specifically to play minecraft VR.  I picked up a used Lenovo Explorer headset and I use Windows Mixed Reality.  My entire setup worked fine and cost less than just the Oculus headsets.It worked great until December and 1.16.200.

GPU: No external GPU (on board HUD 630)

Headset: No Oculus. Lenovo Explorer for WMR

CPU: Intel.

All, I spent all morning with Microsoft tech support. I was frustrated that even after latest windows Feb 2021 KBs vr still would not work since Mincraft 1.16.200 in Dec 2020. We used the latest windows iso to level-set the system. MC still crashed to MR portal on load.  So we downloaded a thing called "Driver Booster v8" and it updated several out of date drivers. Still didn't work. So we uninsalled openvr, the mr portal, dec tools, and minecraft. Restart pc. Unplug vr headset (Lenovo Explorer) usb/hdmi. Restart pc. We removed the xbox BT controler and all audio devices. Pluged the headset usb/hdmi back in. Reinstalled MR portal once headset was detected. Manually updated mixed reality device driver to whatever was already available to click. Repaired controler. Launched game. Still nothing. I'll keep you posted if anything ends up working. 

Muller/Mojang, I know this is hard but please try to understand that Oculus fixes DO NOT DO A THING for Windows Mixed Reality. As I've said, there are two problems here. One that seems to affect the Oculus runtime and is fixed (or might be? - gosh, if we had two different threads for two DIFFERENT PROBLEMS that might help clarify the situation) by changing OpenXRs registry so that the Oculus version of Minecraft can use OpenXR. There is another. The fact that Windows MR and NON-Oculus, Microsoft store Minecraft VR support DOES NOT WORK. At all.  Broken.  

Mojang, if you now understand the difference,  grab yourself a juicebox for a job well done and GO FIX IT!

It would be nice if they decided to FIX IT!  And no, it is VERY different.  Mojang needs to stop being lazy.  The bug reports are different in platform (Windows MR vs Oculus), timeline (1.16.200 ~DEC 2020 vs MUCH OLDER), VR interface (OpenXR vs whatever you used before), and in symptoms (immediate crash vs "searching for updates.").  You need to acknowledge that they are different and FIX IT!  How you ask?  It's called agile programming and hot fixes...it was invented, oh, a decade or so ago.