Werner I
Comments
forget it, this will never get fixed. install vivecraft and enjoy the game if you still want to play it in vr.
No I had no luck with it. Reinstalling does nothing for me. It doesn't help that a few comments on that ticket have obviously nothing to do with the ongoing problem I and a few others are experiencing. When I have time I'll update the ticket with the newest information, game-, oculus- and driver versions.
Nothing is resolved here, please reopen and fix.
Is this a joke? Nothing is resolved, the same problem still exists over multiple Windows 10 versions and Minecraft versions over years now and you have the gall to close this bug as resolved? Incredible!
@Lloyd: I don't think that's the same problem described in that bug report, please open another one or look for the right one.
@Napoleon Bowie: The new Oculus version does have this feature and I tested it out asap; it still doesn't work so that theory is proven false (for me at least).
Not a good look mojang/Microsoft/Oculus.
@Jim Burtoft
That's not the same problem. I only have one video card in this machine and both, monitor and Rift are plugged into it.
The email from the recent update for the issue reminded me of this problem (btw vivecraft works really good, for all the people who are having problems: use vivecraft!) so I though: see for yourself:
Minecraft Windows 10 Edition 1.2.1
Oculus Launcher Version 1.1.5
Still the same problem (lol). Launching! -> Minecraft failed to launch, Press A.
Someone looked into the store password/Windows password mismatch problem? Will we get real Support now that it's out of beta? Or is it still in beta, whereas the version number suggests it's out? Should I try again with email to support or will they tell me that I should open a ticket in the bugtracker?
Updated the affected versions. What do I have to do that this will get the status confirmed?
Minecraft Win10 Edition 1.0.554.0
Oculus Launcher 1.0.5
Same problem.
Yes, still happening. The only difference is that it doesn't crash silently anymore instead you have to confirm that it doesn't work and press A to exit.
Oculus Home launcher version: 0.16.2 (Release Notes: "Minecraft Windows 10 Edition runs on Oculus Rift, and supports all the Windows 10 features you know and love" Yeah, about that...)
Minecraft Windows 10 Edition: 0.1602.2.0
Same problem.
Did anyone read the reddit post I linked above? Is the password mismatch the problem? Hello?
So, I stumbled over a reddit post:
https://www.reddit.com/r/oculus/comments/5cf8z2/minecraft_w10_is_moving_out_of_beta_getting_256/d9whiro/?st=ivfbb302&sh=f4b5bdb1
Quote: "i had an similar issue, for me it was my windows password being different than my windows store password."
Could this be true? I have a local windows account and I am logged in the windows store with my Microsoft account (obviously different passwords).
Eh, I gave up on it. Everything is in beta and that's really convenient for the devs.
If something doesn't work they can just say "Hey, it's beta! What did you expect?".
It doesn't matter that we bought the software and the hardware for real money, not beta money. Heck, Oculus Home is still in "beta" after many, many months.
Alpha, beta, release. Those terms doesn't matter anymore because their meaning has changed.
Nowadays, alpha and beta means "good to ship" with the bonus that you can say "not my problem" to your customers.
And as a double bonus you just don't support your customers. In September I asked for support over email. They don't support over email, I got a link for the bugtracker. Thanks!
The Oculus Home launcher updated to 0.16.0 and the store version to 0.1600.5.0. Problem persists. It's still crashing while launching. Can I do something? Sending log files?
Store version 0.1510.0.0; same problem.
Tried the latest Minecraft version on the Windows store, 0.159.0.0, same problem. No updates on the Oculus store for the launcher.
I've seen that post and looked for a vorbis.acm in my system32 (and searched also system wide) but I don't have that file on my system.
Updated the description.
is this a joke? this is a open and reopened bug that was never fixed despite some people polluting the bugreport with (maybe) similar problems that they claim to have fixed; the problem that I originally reported in 2016 never was fixed by mojang and I don't think I overstep my boundaries when I argue that mojang/Microsoft never seriously looked into that problem. since then, personally, I gave up on you a long time ago already; when I play VR minecraft I play the java version with the mod, but seeing this bug report gets updated every so often from someone with this problem who wants to see it fixed, not everyone has given up on you. Personally, I don't care anymore but now I'm curious if it ever gets fixed (I don't think so) and how long we can keep open this bugreport.