MC-147857MC-137429 is resolved...how?
Same problem as https://bugs.mojang.com/browse/MC-137429.
It says resolved, but no resolution is provided. There is a link to a supposed duplicate, 20220, which seems to be a different issue as the user is able to actually start playing and try to jump. The, um, duplicate, has this sea of so-called duplicates:
What am I supposed to do with that? Check every single one for a possible answer?
I see a reference to updating java, ok done, same problem.
I see a reference to MC-138093, which is re-opened, not resolved.
I see a reference to http://hopper.minecraft.net/help/exit-code/code-1073741819/
"We are currently investigating the root cause of this issue"
That's not resolved. Some possible workarounds, some stabs in the dark that require users to re-install one thing after another in the hope they might solve something, is not a solution. Why do we have to guess and check to fix the bugs mojang has introduced? When this was beta I understood, but really now, have the honesty to at least keep the issue open. When I stopped playing this game it was working, now, without doing anything except watching it update, it's broken. Close the issue only when the updates you force on us have actually fixed it, or there is a clear understanding of some fundamental problem, marked on the issue....not a suggestion to spend an hour re-installing everything because, hey, maybe it'll work. Have some pride ffs.
Environment
Windows 10 64bit
Intel Core i5-3570k 3.4Ghz
16GB RAM
Nvidia gtx 1060 6gb
java version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Client VM (build 25.201-b09, mixed mode)
Created Issue:
MC-137429 is resolved...how?
Same problem as https://bugs.mojang.com/browse/MC-137429.
It says resolved, but no resolution is provided. There is a link to a supposed duplicate, 20220, which seems to be a different issue as the user is able to actually start playing and try to jump. The, um, duplicate, has this sea of so-called duplicates:
What am I supposed to do with that? Check every single one for a possible answer?
I see a reference to updating java, ok done, same problem.
I see a reference to
MC-138093, which is re-opened, not resolved.I see a reference to http://hopper.minecraft.net/help/exit-code/code-1073741819/
"We are currently investigating the root cause of this issue"
That's not resolved. Some possible workarounds, some stabs in the dark that require users to re-install one thing after another in the hope they might solve something, is not a solution. Why do we have to guess and check to fix the bugs mojang has introduced? When this was beta I understood, but really now, have the honesty to at least keep the issue open. When I stopped playing this game it was working, now, without doing anything except watching it update, it's broken. Close the issue only when the updates you force on us have actually fixed it, or there is a clear understanding of some fundamental problem, marked on the issue....not a suggestion to spend an hour re-installing everything because, hey, maybe it'll work. Have some pride ffs.
Environment
Windows 10 64bit
Intel Core i5-3570k 3.4Ghz
16GB RAM
Nvidia gtx 1060 6gbjava version "1.8.0_201"
Java(TM) SE Runtime Environment (build 1.8.0_201-b09)
Java HotSpot(TM) Client VM (build 25.201-b09, mixed mode)
Attachments2
MC-137429is a duplicate ofMC-20220. That has a resolution. You need to follow the trail with some of these issues.This is a technical support issue - not a bug. This page is not to be used for tech support.