Evan Gamble
Assigned
Reported
Comments
Could someone fix the description? It just refers to boats, when in fact it seems to be only a minecart issue at this point.
@KingSupernova
I did try to bring it to Dinnerbone's attention via twitter. Don't know if that worked. Then I emailed Sethbling and asked him about it. He replied and said they're definitely aware of the bug. So that's encouraging!
@MatthewPlumb I agree that this longstanding bug is the most glaring issue in Minecraft because it's so noticeable. I, too, wonder if Jeb and Dinnerbone are even aware of this issue for the PC version of MC. If they aren't, is there any way to bring it to their attention?
Excellent description, @jonathan2520, although I might have toned down the comment "you don't know what you're doing" slightly, for diplomacy's sake.
I hope the devs read this and address this frustrating, longstanding issue.
Isaac King had changed the description to the one written by Vincent Lee, which is here: http://pastebin.com/tYU9havV. That change was lost.
@jonathan2520, now that you're the reporter (thanks CubeTheThird) could you change the description, either to Vincent Lee's, or write your own?
What happened to all the comments on this bug that were posted on Jan. 29, and the change to the description, and the switch to jonathan2520 as reporter of the issue?
There is still something causing severe tick lag on my world in the 1.8 pre-releases. (That world didn't have any tick lag in the 1.7 releases.) I can make the tick lag disappear temporarily by changing my render distance, but then if I activate one of my redstone devices with a clock, it starts getting slower and slower and eventually nearly stops. Then everything has tick lag, even if I turn off the redstone circuit that triggered the tick lag, until I change the render distance again, and the tick lag disappears again.
In my regular world (not superflat) there are areas where the tick length suddenly increases from around 30 ms to 250 or 300 ms, which dramatically slows down minecarts, etc. This didn't happen in the 1.7 versions, only in the 1.8 snapshots. I'm not sure in which snapshot it started happening. Changing doMobSpawning to false does fix the problem, but only for a while. Something then automatically changes doMobSpawning back to true.
I've noticed that once I encounter an area of my world that makes the tick length very long, that traveling back to areas nearby where the tick length was short does not fix the problem, meaning the tick length stays long. Maybe this is because the offending chunks are still loaded. If I go far enough away from the offending areas, the tick length drops back down to normal.
The increase in tick length never seems to be gradual. It always jumps suddenly from normal length to really long in the offending areas. Also, it doesn't seem to be related to fps or to the speed of the computer. Running the same world on a Macbook Air and a fast iMac has about the same really long tick length, despite the fps being about four times higher on the iMac.
Maybe we could add the label "minecart" to this bug report, in addition to "boat" and "horse". Perhaps that would help get this issue noticed by Mojang. I've long wanted to extend my minecart system to include jumping from an overworld track to a track in the nether or the end, but this bug prevents that.