Sinxar

I think this may be the same thing. I am not sure so I am including my crash log. I was just exploring new terrain and it crashed with this error.

[pastebin - ticking error|https://pastebin.com/Z4BnJnnE]

ed: it crashes within a few seconds when loading the world now, same error. i'll just wait for a new prerelease before trying to load it again

Thanks for your time.

This issue occurs in Minecraft version 1.8.1 as well. It is consistently reproducible in single player 1.8.1.

Attach two cows to two leads. Push them through the nether portal. Enter the nether portal. The leads duplicate on the ground on the other side.

Confirming it is easily able to be reproduced most of the time by going far enough away for the chunk to unload. Note that this for the lead actually breaking, not the invisible lead problem. I am unsure as to why the breaking problem is being closed as duplicates.

Been getting this since 1.6.1. I thought it was a SMP issue but it have been happening extremely often in my current SSP world as well (1.6.2).

I can assure you my PC is up to the task. My specs are posted above. In 1.4.7 I am getting 100+ FPS at all times. In 1.5 pre, its less than 20 FPS with smooth lighting. As stated, the new Optifine fixes the issue somehow. I have downloaded multiple copies of this snapshot over the past few days and noticed that each jar is slightly different in size, although it appears to be the same version. The latest download the problem is less, but still unplayable.

As an example, sometimes I can get up to 60 FPS if I derp around long enough. However it is not smooth. It appears as if the FPS is actually in the sub 20 range with constant stuttering and obvious to the human eye chugging causing eye strain, but the FPS meter doesn't pick this up. Two days ago I started a new world to test again. We all know it takes a bit for terrain to generate. Over 30 minutes later it is still at 0 - 5 FPS looking straight up at the sky from a hole in the ground.

According to GPU-Z my 8800GT is only being loaded to about 6% by Minecraft 1.5pre. With the new Optifine installed it increases the utilization to around 30%. 1.4.7 puts it at 30% max. 1.4.7 with optifine give me 41% max.

Evidence that the game isn't properly using my GPU.

I wish I could get 30 - 50. I can't seem to break 10 FPS anymore. Its usually less than 1 FPS. Anyway there is a new version of Optifine that was mentioned in that FPS fixer thread. It seems to fix the issue. It also seems to be using the new lighting update because the upside-down stair lighting glitch is not present. We will see how the official release goes tomorrow.

Attached my logs. Created a fresh install and upgraded to 1.5 pre. Created a new world to test the issue again. Strangely enough it is actually worse in the new world than my current 1.4.7 world.

From what I can gather, it has something to do with the way chunk updates are handled. So when I stand still for a while and the updates finish its silky smooth. Once you start moving around and it needs to be updated the stuttering and low FPS starts. It almost acts as if the GPU is not being used for the lighting, instead its running on the same core of the CPU that the loader is using.

I have no idea how this is handled in the game but that's my observation.

Im using an 8800GT 512MB. My CPU is an AMD 5600+ 64 X2 with 4GB RAM.

This issue is still present in 1.5 pre. Not sure why its showing up as "resolved" as its worse than the last snapshot. Am I seriously being forced to go from max settings (1.4.7) to minimum settings (1.5 pre) for it to be playable?

Sorry about that. I did in fact search first. There were no reported issues other than the official ones. It wasn't until after submitting the report, the other ones showed up. Perhaps its because I submitted this for the current snapshot while all the other reports are for old ones.