BlazeFaia
Assigned
Reported
Comments
@unknown Nope. This morning the store still said 0.14.0, but I had an update, and in game it said 0.14.1. As of now, the store should say 0.14.1 as well.
As of today, with 0.14.1, I was able to load into Minecraft successfully thrice. I suggest everyone having issues try again. Please report if it still doesn't work on your end. Assuming everyone else can connect. I'd request this bug stay open for at least 3 more days for extensive testing. I'll try opening the game in different environments (Ie different applications running, opening the game minimized, etc) and report back if I have any issues.
Ah. Sorry for the frustration. It's been a while since I've been able to play. I've been more active in /r/MCPE in my concerns however. I'll repeat what I said there if it's of any help.
"I can, with 99% certainty say it's an Nvidia Optimus Technology issue. And it's not the first game to not play nice with Optimus. A lot of "fixes" involved disabling the Nvidia graphics chip and using the Intel one or temporarily updating the drivers. But one thing I'm certain of is, despite it being related to Nvidia I don't think it's something that can be resolved with an Nvidia driver update as the issues return within a few days even without preforming another update.
I wish I could offer more information than that, but if you're not already looking into Optimus as a source of the problem I'd recommend doing so."
What? This is most certainly NOT resolved by any stretch of the imagination. Minecraft Win 10 Edition still crashes on startup. Am I just supposed to pretend like everything's fine and just never play this game again? That's just not right.
Don't relax just yet. Nvidia has updated multiple times and this issue has been "fixed" multiple times. Until a few days later when it happens again and you have to update your Nvidia drivers again. I don't want this bug to be marked as resolved only for it to pop up again a few days later because it's more than likely not something Nvidia can fix. I feel it has something to do with the most recent drivers available. Which is a problem when they update every other day.
I don't see Client> Setting gameDir to:<path>
I'm assuming that has something to do with Forge. But I need Forge. Any tips. =x
I said it worked with 1.6.2-1.5.1 XP What it wasn't working with was 1.4.7. Well. It WASN'T working. I tried a fresh vanilla 1.4.7 and it worked. Tried to install Forge and I got the same problem. So Forge is the problem here. Looks like this problem is indeed fixed.
But the title of this bug report doesn't specifically state 1.6.2. Just that new directories don't work. So even though it works for 1.6.2-1.5.1 anything lower doesn't work. That's still a bug that needs to be fixed.
Also whoops, meant to say 1.4.7. Not 1.4.5.
It's not fixed. In the image I just attached you can see I'm running my .jar with the custom directory but nothing is in there but the server.log file. I'm on launcher 1.1.1.
Ezekiel, that's not entirely true either. =P As long as there is a version on the launcher it'll work regardless of being local or being kept up to date with remote.
For instance. If I make a copy of 1.5.1 and rename it to something else, it's no longer "up to date with remote" but rather it's only "local". However. Because the launcher has a 1.5.1.jar on it it'll work. A 1.4.5.jar or lower won't work though.
Ezekiel, it does. I've tried it with 1.5.2 and 1.5.1. It will download and install to a new directory if it's a new version, but if you try to change the directory again it doesn't acknowledge said change. This becomes a problem with local only versions because they're never installed to begin with.
Edit: Nevermind. It works for any version that exists on the new launcher. Local or kept up to date on remote. So any 1.6, 1.5, or snapshot shown on the launcher will be able to change their game directory where they see fit. The version I need working is 1.4.5 which isn't listed.
Tl;dr: The problem isn't with pre-1.6 jars. It's with jars not on hosted on the dev launcher. (1.4 and under)
After some extensive testing I haven't had any issues running MC Win 10 anymore. So, at least for me, this bug is fixed.