Zorro8183

Yes it appears to work now finally with the latest version with one caveat... it appears that I'm in a permanent standing position with no way to change that in the menus. I'm disabled and need to be able to play the game in a seated position. Could you please add this option to the settings so that I can play the game sitting and still be able to get through my doorways. I didn't have a problem with this on previous version (before it broke again) but now because I'm sitting the game is kind of weird and can't get through even 2x2 doorways without crouching. Could you please fix this issue or add a settings option in accessibility menu to switch the game to seated play?

I just tested this issue with joining my WIFE'S world this time and still crashes when I try to place signs with the same error message as originally posted.

I forgot to mention that I'm using Oculus Quest 2 for my vr equipment with Air Link and my OS is Windows 10. 16GB RAM, I7 CPU (genuine Intel), Nvidia RTX 2060 GPU 

also I thought I was loosing my mind but now I know I'm not because when I Minecraft crashes I definitely hear audio from something somehow. Idk why or where it's coming from. it does NOT sound like Minecraft music

Are far as I can tell it's just realms and have since determined that there's something wrong with it's connectivity as we can connect just fine with an ethernet cable no problems I can tell. Pretty difficult ro use a wired ethernet connection on a cell phone though. I tried reporting my discovery and they said it was too technical for them. But anyway it's only with a wired ethernet connection that it works. No ethernet no connection which is what I'm trying to get fixed.

We've tried both wifi and mobile data but neither worked. It still gets "stuck" on joining realm. It won't let us download either when the message comes up "download and join/join"

I'm from Canada but yes I will join you because I did the same damn thing for the same reason only to find that as soon as I purchased the equipment the game did not work and still doesn't so yes I think this is bs and will definitely join you in the 'suit Gerod! they should have had this fixed months ago but all they're doing is giving us crappy so called "fixes" causes us to **** around with multi thousand dollar equipment that could possibly void the warranty if it self destructs as a result of the tampering!

MOJANG GET YOUR HEAD ON STRAIGHT AND GET THIS FIXED WITHOUT TRYING TO GET US TO VOID ANY WARRANTIES! THIS IS BS AND YOU KNOW IT! DO YOUR DAMN JOB THAT'S WHAT MOST OF US ARE PAYING FOR!

I also have RTX GPU but I see Microsoft didn't like the truth because my comment has been removed! the truth hurts doesn't it Microsoft?! I should've guessed that you would remove a comment that was just telling it like it is! 

anyway I have an Alienware m15 R2 (it WAS an R1 but now since the most recent update for some reason now it's R2 and Idk how) with RTX 2060 16GB RAM  i7 9th Gen Windows 10 x64 with latest drivers and I use an Oculus Quest 2 headset with Link cable

I have tried reinstalling everything but to no avail. I've grown tired of this BS and considering demanding a refund and moving onto the another game that DOES work! what a shame Microsoft but I'm not surprised you don't have the best track record for fixing things when they break! FIX THIS OR I WILL DEMAND A REFUND! no more half fixes or screwing around with the OS when it's not going to work especially with a computer in excess of $3k! just fix the issue how hard is that?! my dad had to pay to have my computer repaired because of your damn supposed "fixes"! it's NOT the os and I think the person that commented before me is right...now that I think of it, all these issues seem to have a pattern regarding RTX GPUs! some people have reported fixing the issue by either installing software or updating their drivers BUT they did NOT have RTX GPUs!

maybe if others start thinking the same way they might realize the loss of business and fix the damn issue!

I tried what you suggested but no change still crashes

can you guys PLEASE FIX THIS without making me wait another 5 years?! I have an Oculus Quest 2 that I got for my birthday after Christmas with Link cable and state of the art (it's a year old now) gaming computer that is VR capable. I have tried to uninstall and reinstall MC VR as well as doing same for Oculus suite but to no surprise no change...MC still says "checking for updates" then crashes back to Oculus home no matter what I try to do to fix it. this needs to be fixed I PAID for this and it doesn't work please fix this!

btw I use Windows 10 x64 with all the latest updates

I just looked up at the top of this issue and it says it affects v1.16.x. does this mean there is a newer version for MC VR? Oculus game screen (containing game details and play button) says 1.15 with no way to update. please confirm or verify - very confused!

I just realized I selected the wrong selection. It won't let me change it to Bedrock Codebase as it was a problem with BOTH regular Minecraft AND Realms!

I took a look at what you suggested and honestly, you know how long it would take me to do that? You know how big our base is or it's complexity and how many lights we use? It would take myself or one of my admins hours to do what you suggested! I thank you for the suggestion but it is just too impractical and WAY too time consuming! We need a more permanent fix.

These are digital stills I took of the screen when I tried to use the /forceload command. It does NOT work and now I'll upload the proof! Notice how I get an error message? Now that I've provided digital PROOF the damn does NOT work will you believe me now and fix it?!

I beg to differ! I typed the command in trying various configurations and methods but could NOT get the game to even recognize the command so how can you say it's there when clearly something is wrong with it and if I have to upload a screenshot of the blasted thing I will! This command is faulty unless you can prove otherwise like providing me the syntax that was used to actually produce the result the command is actually supposed to produce. I tried for 2 hours to get the command to work with no success! I will upload a screenshot tomorrow. Also you DID use version 1.13.2 right? That's the version I was using. I'm also using Chroma Hills.

Can you please provide instructions on how to upload my world so the dev's and/or mods can see the problem? If it it's neccessary I'm playing with the Halo Mashup. 

How long is it "fixed" for this time?

With my recent comment even that didn't even seem to get their attention. I am spending a LOT of money on subscriptions by these people for my family and they refuse to fix this. I am getting very upset about this and considering NOT renewing any of my family's subscriptions until this is resolved. I'm sorry to say they seem to be more interested in only computer or console to pay any attention to those that also use or play on mobile. They should worry about getting this issue resolved. 

Even though we've reported this issue and are complaining about this bug they do not seem to be too eager to fix this issue for mobile! I'm spending over $50 on Realms for my family and can't even use them on our mobile devices because of this blasted bug! What am I really paying for? I'm starting to get VERY frustrated and upset with this because I can't use what I am paying for! I might just cancel all my subscriptions - maybe then it will get their attention and will want to get this fixed expeditiously! I hope this gets their attention!

I'm experiencing this issue with my Samsung Galaxy Note 8 with Android 8.0. I can download my worlds from my Realms but cannot enter them once downloaded. This is very frustrating. You have fixed this for Xbox but not for Android please fix! I didn't pay for this not to be able to use it!

I just noticed that it has almost been a month since I was able to use/play Minecraft on my Note 8....    what's taking so long to fix this issue?

Is it going to be fixed soon?

The problem is...        I'm not using or playing on Xbox, I'm using my Note 8 which is Android (a product of Google) and the problem still exists. I didn't mention my device in the details of my description?